WebUI scheduling question

I'd like some clarification on the scheduling functions.

For them to work, obviously the FlexRAID Host Service has to be running in the background.

What I'm not sure about is: does the Tomcat thing have to run as well? Or, once set in the WebUI, the Host Service will "know" what to do and when?

Yes, both of them have to be running.

The scheduling function is part of the Web UI Client.
I left this sort of functionality out of the host application to keep it lean and clean.

I could probably add the option to export your Web configuration to a configuration that could be run by the DOS/Shell client.
This way, one could script and schedule the DOS/Shell client through the OS as a lighter weight option.

Since you only have to have a single Web UI Client regardless of the number of hosts, I moved my Web UI Client to a VMware virtual appliance.
I leave that virtual appliance running 24/7 and do not worry much about it.

I am still looking for developers that will write simpler and/or more interesting clients.

This message was edited 1 time. Last update was at 11/01/2009 16:08:33

Brahim wrote:Yes, both of them have to be running.

The scheduling function is part of the Web UI Client.
I left this sort of functionality out of the host application to keep it lean and clean.

I could probably add the option to export your Web configuration to a configuration that could be run by the DOS/Shell client.
This way, one could script and schedule the DOS/Shell client through the OS as a lighter weight option.

Since you only have to have a single Web UI Client regardless of the number of hosts, I moved my Web UI Client to a VMware virtual appliance.
I leave that virtual appliance running 24/7 and do not worry much about it.

I am still looking for developers that will write simpler and/or more interesting clients.

I would leave the management interfaces separate from the services as well. A tomcat service is a very light footprint and can be called as a service if desired. I would want my service management interface left running to give me email notices on my regularly scheduled activities (ie. re-sync errors based on re-syncing every hour). This also allows for you to place your service management interface on another system (as stated ie: VMWare). Remember, VMWare will inherently have a much larger overhead than just running your Tomcat based interface (Mine only takes 87k memory and >2% process cycles).