- Original Message -
> From: "Andreas Ntaflos"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, February 29, 2012 1:38:08 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> On 27/02/12 13:09, Ante Karamatić wrote:
>
On 27/02/12 13:09, Ante Karamatić wrote:
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> 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
On Wed, Feb 29, 2012 at 6:38 PM, Florian Haas wrote:
> On Wed, Feb 29, 2012 at 8:21 AM, Andrew Beekhof wrote:
>> 2012/2/27 Ante Karamatić :
>>> On 27.02.2012 12:27, Florian Haas wrote:
>>>
Alas, to the best of my knowledge the only way to change a specific
job's respawn policy is by mod
On Wed, Feb 29, 2012 at 8:21 AM, Andrew Beekhof wrote:
> 2012/2/27 Ante Karamatić :
>> On 27.02.2012 12:27, Florian Haas wrote:
>>
>>> 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
2012/2/27 Ante Karamatić :
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> 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
2012/2/27 Ante Karamatić :
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> 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
On 27.02.2012 12:27, Florian Haas wrote:
> 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 mainta
On Mon, Feb 27, 2012 at 11:07 PM, Ante Karamatic wrote:
> On 27.02.2012 11:37, Andrew Beekhof wrote:
>
>> I know, but whatever the admin specifies should over-rule the package
>> maintainer's defaults.
>
> I agree and that's how upstart works.
>
>> From what you're saying, this is not possible wit
On 27.02.2012 11:37, Andrew Beekhof wrote:
> I know, but whatever the admin specifies should over-rule the package
> maintainer's defaults.
I agree and that's how upstart works.
> From what you're saying, this is not possible with Upstart. Which is bad.
I said it's an option, not that it's not
On Mon, Feb 27, 2012 at 10:27 PM, Florian Haas wrote:
> On 02/27/12 11:37, Andrew Beekhof wrote:
>> On Sun, Feb 26, 2012 at 8:54 AM, Ante Karamatic wrote:
>>> On 23.02.2012 23:52, Andrew Beekhof wrote:
>>>
On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic wrote:
> Well... Upstart actually
On 02/27/12 11:37, Andrew Beekhof wrote:
> On Sun, Feb 26, 2012 at 8:54 AM, Ante Karamatic wrote:
>> On 23.02.2012 23:52, Andrew Beekhof wrote:
>>
>>> On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic wrote:
Well... Upstart actually does notice if the job failed and respawns it -
dependin
On Sun, Feb 26, 2012 at 8:54 AM, Ante Karamatic wrote:
> On 23.02.2012 23:52, Andrew Beekhof wrote:
>
>> On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic wrote:
>>> Well... Upstart actually does notice if the job failed and respawns it -
>>> depending on job's configuration.
>>
>> Actually this is
On 23.02.2012 23:52, Andrew Beekhof wrote:
> On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic 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.
> Restartin
On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic wrote:
> On 23.02.2012 07:57, Vladislav Bogdanov wrote:
>
>> Thanks for clarification, that wasn't clear at the moment I looked at
>> it. If I knew that, I wouldn't write that RA. One remark, my RA has
>> possibility to check service aliveness on mon
On Thu, Feb 23, 2012 at 6:31 PM, Ante Karamatic wrote:
> On 23.02.2012 00:10, Andrew Beekhof wrote:
>
>> Do you still have LSB scripts on a machine thats using upstart?
>
> Yes, some LSB scripts can't be easily converted to upstart jobs. Or,
> let's rephrase that - can't be converted to upstart jo
23.02.2012 10:43, Ante Karamatic wrote:
> On 23.02.2012 07:57, Vladislav Bogdanov wrote:
>
>> Thanks for clarification, that wasn't clear at the moment I looked at
>> it. If I knew that, I wouldn't write that RA. One remark, my RA has
>> possibility to check service aliveness on monitor operation
On 23.02.2012 07:57, Vladislav Bogdanov wrote:
> Thanks for clarification, that wasn't clear at the moment I looked at
> it. If I knew that, I wouldn't write that RA. One remark, my RA has
> possibility to check service aliveness on monitor operation and repair
> that service if it hangs.
Well...
On 23.02.2012 00:10, Andrew Beekhof wrote:
> Do you still have LSB scripts on a machine thats using upstart?
Yes, some LSB scripts can't be easily converted to upstart jobs. Or,
let's rephrase that - can't be converted to upstart jobs without losing
some of the functionality.
> On fedora they pu
22.02.2012 22:44, Ante Karamatic wrote:
> On 22.02.2012 19:45, Vladislav Bogdanov wrote:
>
>> I looked at that RAexec very early, just after it was commited, and I
>> understand that it requires running dbus daemon to operate. I prefer to
>> simplify operation chains, so that is really not an opti
On Thu, Feb 23, 2012 at 5:01 AM, Ante Karamatic wrote:
> On 21.02.2012 17:56, Jake Smith wrote:
>
>> Np thanks for adding - I was asking because the exit codes on the
>> upstart jobs I'm using didn't align (I believe) with the LSB spec and
>> I wasn't sure if they were supposed to. Haven't really
- Original Message -
> From: "Ante Karamatic"
> To: pacemaker@oss.clusterlabs.org
> Sent: Wednesday, February 22, 2012 1:26:56 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> On 21.02.2012 16:30, Florian Haas wrote:
>
> > [1] "Why
On 22.02.2012 19:45, Vladislav Bogdanov wrote:
> I looked at that RAexec very early, just after it was commited, and I
> understand that it requires running dbus daemon to operate. I prefer to
> simplify operation chains, so that is really not an option for me to
> rely on one more service to do s
- Original Message -
> From: "Ante Karamatic"
> To: pacemaker@oss.clusterlabs.org
> Sent: Wednesday, February 22, 2012 1:01:35 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> On 21.02.2012 17:56, Jake Smith wrote:
>
> > Np thanks for adding - I
22.02.2012 20:55, Ante Karamatic write:
> On 16.02.2012 05:23, Vladislav Bogdanov wrote:
>
>> Newer versions of pacemaker and lrmd are able to deal with upstart
>> resources via dbus.
>> However I do not like this way, so please find resource-agent attached,
>> which is able to manage arbitrary up
On 21.02.2012 16:30, Florian Haas wrote:
> [1] "Why do I need to use a PPA if this release is ostensibly on
> long-term support?" Don't ask me, ask someone from Canonical. :)
Pacemaker isn't really supported cluster stack in Ubuntu 10.04 (it's in
universe). RHCS is in main and supported. There ar
On 21.02.2012 17:56, Jake Smith wrote:
> Np thanks for adding - I was asking because the exit codes on the
> upstart jobs I'm using didn't align (I believe) with the LSB spec and
> I wasn't sure if they were supposed to. Haven't really seen the
> level of documentation (as LSB resource) for upsta
On 16.02.2012 05:23, Vladislav Bogdanov wrote:
> Newer versions of pacemaker and lrmd are able to deal with upstart
> resources via dbus.
> However I do not like this way, so please find resource-agent attached,
> which is able to manage arbitrary upstart job (just like Anything but
> for upstart
ces. I would assume since they are Ubuntu
specific. Mine seems to be working OK so far but haven't stressed it yet.
- Original Message -
> From: "Florian Haas"
> To: "The Pacemaker cluster resource manager"
> Sent: Tuesday, February 21, 2012 10:30:27 AM
Jake,
sorry, I missed your original post due to travel; let me toss in one
more thing here:
On Tue, Feb 21, 2012 at 3:32 PM, Jake Smith wrote:
>> > Are upstart jobs expected to conform to the LSB spec with regards
>> > to exit codes, etc?
>> > Is there any reference documentation using upstart r
Thanks!
Jake
- Original Message -
> From: "Vladislav Bogdanov"
> To: pacemaker@oss.clusterlabs.org
> Sent: Wednesday, February 15, 2012 11:23:01 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> Hi,
>
> 16.02.2012 02:02, Jake Smith wrote:
> >
Hi,
16.02.2012 02:02, Jake Smith wrote:
> When using upstart jobs in Pacemaker I haven't been able to find
> much of anything for documentation. After reading a post a few minutes ago by
> Andreas I wanted to verify...
>
> Are upstart jobs expected to conform to the LSB spec with regards to exit
When using upstart jobs in Pacemaker I haven't been able to find much of
anything for documentation. After reading a post a few minutes ago by Andreas
I wanted to verify...
Are upstart jobs expected to conform to the LSB spec with regards to exit
codes, etc?
Is there any reference documentatio
32 matches
Mail list logo
