Hi,
I was reading through the following votequorum manpage:
https://www.systutorials.com/docs/linux/man/5-votequorum/
and read the following about the allow_downscale feature:
---
allow_downscale: 1
On Thu, 2020-09-24 at 11:30 -0400, Digimer wrote:
> On 2020-09-24 5:00 a.m., Klaus Wenninger wrote:
> > On 9/24/20 9:19 AM, Reid Wahl wrote:
> > > **Directly via the CIB**, I don't see a more obvious way than
> > > looking
> > > for the most recent (perhaps by last-rc-change) successful
> > >
This is the kind of stuff I've been working on a lot, so hopefully I've
added enough tools to make this easy to do. If not, I guess I've got
more work to do.
What's your time frame, are you lucky enough to be able to use the latest
pacemaker releases, and are you going to use command line tools
On 2020-09-24 5:00 a.m., Klaus Wenninger wrote:
> On 9/24/20 9:19 AM, Reid Wahl wrote:
>> **Directly via the CIB**, I don't see a more obvious way than looking
>> for the most recent (perhaps by last-rc-change) successful
>> (rc-code="0" or rc-code="8") monitor operation. That might be
>>
On 2020-09-24 3:19 a.m., Reid Wahl wrote:
> **Directly via the CIB**, I don't see a more obvious way than looking
> for the most recent (perhaps by last-rc-change) successful
> (rc-code="0" or rc-code="8") monitor operation. That might be
> error-prone. I haven't looked into exactly how
On 9/24/20 9:19 AM, Reid Wahl wrote:
> **Directly via the CIB**, I don't see a more obvious way than looking
> for the most recent (perhaps by last-rc-change) successful
> (rc-code="0" or rc-code="8") monitor operation. That might be
> error-prone. I haven't looked into exactly how crm_simulate
**Directly via the CIB**, I don't see a more obvious way than looking
for the most recent (perhaps by last-rc-change) successful
(rc-code="0" or rc-code="8") monitor operation. That might be
error-prone. I haven't looked into exactly how crm_simulate parses
resource status from the CIB XML yet.
Hi all,
I'm trying to parse the CIB to determine which node a given resource
(VM) is currently running on. I notice that the 'monitor' shows in both
node's status element (from when it last ran when the node previously
hosted the resource).
https://pastebin.com/6RCMWdgq
Specifically, I see
