Please also note, that all open patches created *before* the stable/5.1 branch
should now be reconsidered as targeted to 6.0 release instead of 5.1 as they
initially were upon the submission.
Therefore, all backporting stuff needed should be not forgotten and related
bugs should be updated as
> Why do you use [puppet] tag?
> Is there anything related to Puppet OpenStack modules we should take
> care of?
There are several deployment automation tools leveraging the puppet-openstack
modules.
Those are under the Big Tent and each has its own composition layer and
deployment patterns wit
Thank you Andrew.
Answers below.
>>>
Sounds interesting, can you give any comment about how it differs to the
other[i] upstream agent?
Am I right that this one is effectively A/P and wont function without some kind
of shared storage?
Any particular reason you went down this path instead of full A
Hi Roman.
That's interesting, although’s hard to believe (there is no slave lag in galera
multi master). I can only suggest us to create another jepsen test to verify
exactly scenario you describe. As well as other OpenStack specific patterns.
Regards,
Bogdan.
Od: Roman Podoliaka
Wys
I suggest to use pacemaker multistate clone resource to rotate and rsync fernet
tokens from local directories across cluster nodes. The resource prototype is
described here https://etherpad.openstack.org/p/fernet_tokens_pacemaker
Pros: Pacemaker will care about CAP/split-brain stuff for us, we ju
