{"push_id":2863586818,"size":3,"distinct_size":3,"ref":"refs/heads/fernet-initial-sync-8","head":"ee5ce93bd99aa20f39ca7ddae4adcb71af77926a","before":"acb44c5c54680a8c17eaf5466e11cea969c8fb75","commits":[{"sha":"e898bfd31382f13a4a60379345685dd346e63ee2","author":{"name":"Jacek Tomasiak","email":"e09ceaaec8e6e5d02a5e2a59b166644e946f988c@gmail.com"},"message":"keystone: Always try to rsync keys to new nodes\n\nWhen adding new node to existing cluster, fernet keys need to be pushed from\nthe founder to keep all keystone nodes in sync. Before this change the keys\nwere pushed to all nodes when cluster was initially set up and then rotated\nperiodically.\n\nThis commit introduces internal node attribute which indicates that the keys\nare already in place. Founder pushes the fernet keys to all nodes which don't\nhave this attribute set. The same code covers initial cluster setup as well\nas adding new node to existing cluster.\n\nIn addition the lookup of cluster member nodes was changed. Helper function\nfrom crowbar-pacemaker cookbook which was based on Chef search was replaced\nwith direct lookup of `elements` attribute (based on deployment part of\nproposal). This way, new soon-to-be-cluster-member node will be included in\nthe list even before Chef search index is updated and/or chef-client is run\non that node. This guarantees that fernet keys are pushed to the new node as\nsoon as possible.\n\n(based on commit 901d3bd4e00e438fa31d2e64dfa49c75f6cf8ddd)","distinct":true,"url":"https://api.github.com/repos/skazi0/crowbar-openstack/commits/e898bfd31382f13a4a60379345685dd346e63ee2"},{"sha":"08247da255a2a6a03628a532a7b26b43529ae600","author":{"name":"Jacek Tomasiak","email":"e09ceaaec8e6e5d02a5e2a59b166644e946f988c@gmail.com"},"message":"nova: Increase HA resources creation timeout\n\nWhen new node is added to existing cluster, all cloned resources need to be\nextended to include the new node. This operation takes more time than initial\ncreation of resources as it is implemented as a series of \"update\" calls\nrather than single transaction. Updated timeout was based on timing stats\ncollected from test runs.\n\n(cherry picked from commit 7eaf4773b62c5454530ccd2d9aa553bc5058f65a)","distinct":true,"url":"https://api.github.com/repos/skazi0/crowbar-openstack/commits/08247da255a2a6a03628a532a7b26b43529ae600"},{"sha":"ee5ce93bd99aa20f39ca7ddae4adcb71af77926a","author":{"name":"Jacek Tomasiak","email":"e09ceaaec8e6e5d02a5e2a59b166644e946f988c@gmail.com"},"message":"horizon: Increase HA timeout\n\nWhen new node is added to existing cluster, Horizon needs to be installed and\nconfigured on that node. Because \"old\" nodes have most of required packages\nand configurations already in place, this step caused the new node to fall\nbehind so much that the default sync window was breached.\nUpdated timeout was based on timing stats collected from test runs.\n\n(cherry picked from commit 890237ed7e870b5acaf83aec5557c8d7db497273)","distinct":true,"url":"https://api.github.com/repos/skazi0/crowbar-openstack/commits/ee5ce93bd99aa20f39ca7ddae4adcb71af77926a"}]}
{"actor":{"display_login":"skazi0"}}