Description of problem:
In RHCS3, service state was persisted across quorum transitions because it wrote
the states to stable storage. In RHCS4, we have no such luxury. The service
states are distributed, and are zapped when quorum is lost.
So, I added an "autostart" (default=1) to services at some point along the way.
This allows services to automatically start when quorum is achieved and/or when
When autostart is explicitly set to 0, the service will not automatically start
when the cluster is ready... instead, the administrator will have to enable it.
As a UI thing, I would think this is a check box which defaults to "checked".
check box has been added.