On 3/19/2010 9:42 AM, Marcin Owsiany wrote:
On Thu, Mar 18, 2010 at 10:58:52AM +0100, David Schmitt wrote:
On 3/17/2010 8:41 PM, Luke Kanies wrote:
If you have two services, where one service specifies that it being in a
'running' state requires that the other service must also be in a
'running' state, when you got to restart the required service then the
requiring service can automatically be brought down first.
+1
There might be exceptions, though. Consider an application that requires
a database to be up for startup, but once it's running, is able to
survive a database restart, degrading gracefully (serving from cache or
whatever). You would not want to degrade ungracefully by shutting it
down with the DB.
Indeed. But this is a question of modelling, not of the required
mechnics. Such an application would need to have running, degraded and
stopped states defined. This could even be used to start a lighttpd
serving a static "we're offline" site instead of a normally running
application container.
Regards, David
--
dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at
Klosterneuburg UID: ATU64260999
FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
