Cloud/Walrus/SC init script confusing

[Colin Watson]

The eucalyptus-{cloud,walrus,sc} init scripts are very confusing. They all operate on more or less the one daemon process, copying different .jar files into place as appropriate. Starting each of the components involves repeatedly restarting the Java front-end.

It would be a lot simpler and more robust, and certainly more efficient at boot, to have a single init script that starts all the locally-installed components at once.

[Thierry Carrez (ttx)]

We could have a single eucalyptus-java-ws init script (shipped in eucalyptus-java-common) and have eucalyptus-{cloud,walrus,sc} install a file in /etc/eucalyptus/ws.d. That init script would start eucalyptus-cloud once, enabling all installed ws in one pass, then wait the thing to really come up (timeouting after one minute), and try to register services if needed.

Postinst would just restart eucalyptus-java-ws, solving bug 430841 in the process.

[Dustin Kirkland  (kirkland)]

Marking wishlist. I agree wholeheartedly this needs to be fixed, though.

:-Dustin

[Thierry Carrez (ttx)]

Rather than using a file in /etc/eucalyptus/ws.d it is possible to start all installed services by looking at installed jar files.

Remark: the current design (multiple initscripts) was there to enable the possibility to stop just one service without affecting all the installed services. Basically it would stop all services then restart without the one you stopped. That doesn't invalidate the single-initscript-for-all-eucalyptus-ws approach, its just that we need to provide a "/etc/init.d/eucalyptus-java-ws stop walrus" that would allow that.

[Thierry Carrez (ttx)]

Fixed by the upstartification of the scripts, as of 1.6~bzr854-0ubuntu10