[Pacemaker] Upstart resources

[Andrew Beekhof]

On Mon, Feb 27, 2012 at 10:27 PM, Florian Haas <florian at hastexo.com> wrote:
> On 02/27/12 11:37, Andrew Beekhof wrote:
>> On Sun, Feb 26, 2012 at 8:54 AM, Ante Karamatic <ivoks at ubuntu.com> wrote:
>>> On 23.02.2012 23:52, Andrew Beekhof wrote:
>>>
>>>> On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic <ivoks at ubuntu.com> wrote:
>>>>> Well... Upstart actually does notice if the job failed and respawns it -
>>>>> depending on job's configuration.
>>>>
>>>> Actually this is /really/ bad as it subverts our recovery policies.
>>>> Restarting on the local machine is not the only option.
>>>
>>> It's an option. If you add 'respawn' to upstart job, it will respawn on
>>> failure.
>>
>> I know, but whatever the admin specifies should over-rule the package
>> maintainer's defaults.
>> From what you're saying, this is not possible with Upstart.  Which is bad.
>
> Alas, to the best of my knowledge the only way to change a specific
> job's respawn policy is by modifying its job definition. Likewise,
> that's the only way to enable or disable starting on system boot. So
> there is a way to overrule the package maintainer's default -- hacking
> the job definition.

This was the path the systemd guys tried to send us down too.
I was able to bring them around in the end.

>
> All of which isn't exactly pretty. What you could say in the Upstart
> folks' defense is that the job definitions themselves are at least
> always defined as config files in the .deb packages, so they won't get
> clobbered on upgrades.
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org