pcs: constraints, groups do not delay creation of primitives about puppet-corosync

[sammcj]

We too noticed this and it prevented us from using pcs with this module.

[fghaas]

@sammcj You mean it's been that way from the get-go? Then that would mean this provider was never usable except for the most trivial of configurations. @jonhattan and @roidelapluie, can you please comment?

[roidelapluie]

Yes this is true. I will use that module in complex situations and I plan to integrate that in this module. The solution is to use the shadow functionality.

[fghaas]

@roidelapluie My Ruby-fu is minimal, but I thought that's what the pcs implementations already do use?

[roidelapluie]

You can use the https://github.com/puppet-community/puppet-corosync/blob/master/lib/puppet/provider/cs_shadow/pcs.rb

But I have never tested it yet.

[fghaas]

@roidelapluie Ok, so since that appears to be undocumented, let's see if I get this correctly:

cs_shadow { 'puppet': }
cs_primitive { 'p_foo':
  cib => 'puppet',
  # etc.
}
cs_primitive { 'p_bar':
  cib => 'puppet',
  # etc.
}
cs_group { 'g_foobar':
  cib => 'puppet',
  primitives => [ 'p_foo', 'p_bar' ],
}

Is that how this is supposed to be used?

[roidelapluie]

Yes and it should work with the crm provider

[jonhattan]

I'm no longer using this module (neither puppet) for corosync config. In case it helps you figure out how to fix cs_shadow/pcs.rb, this is what I'm doing in a script:

# Do the config in a shadow cib
pcs cluster cib mysql_cfg

PCS="pcs -f mysql_cfg"

# Properties
$PCS property set stonith-enabled=false
$PCS property set symmetric-cluster=false

...
...

# Apply config
pcs cluster cib-push mysql_cfg

[roidelapluie]

thanks for your feedback it is very welcome!

[roidelapluie]

Pull request #162 fixes all of this

[jyaworski]

#162 is still in progress.

[igalic]

@roidelapluie what's the current pr for this issue?

[roidelapluie]

Fixed in #209