{"push_id":2994056505,"size":2,"distinct_size":2,"ref":"refs/heads/stable/5.0-pike","head":"840d3217b51397a14a4b8d8d5a9f1532c2e18cc0","before":"34ebbac3a66f0f17118be4fb214c220ed4ba0dca","commits":[{"sha":"0d26f8b119e1a3b0f6df75e554001956504d19c6","author":{"name":"Itxaka","email":"42e101dc888a514bad9d9ee51575d1b619c722d8@suse.com"},"message":"rabbitmq: block client port on startup\n\nThis script blocks the connection to the rabbitmq cluster in case the number of nodes decay below the half\nof the total. In this case the remaining rabbit nodes won't accept new connections until quorum is reached.\n\nIt takes advantage of the ClusterMon agent that notifies when a rabbitmq has failed or has restored.\n\nAll nodes rabbitmq ports will be blocked if the total number of alive nodes are below to the half of\nnodes of the cluster, or unblock if its over this value.\n\nThe reasoning behind this patch is to allow waiting for more than one node in the cluster to be ready,\nwhich is useful for two reasons:\n\n - clients would connect to more than one node\n - master for queues would be spread more evenly\n\nCurrently most of the connections and master queues are created on the master node, as its the first\nto come up when the cluster is restarted/new master promoted.\n\nco-authored-by: Ivan Lausuch <ilausuch@suse.com>","distinct":true,"url":"https://api.github.com/repos/crowbar/crowbar-openstack/commits/0d26f8b119e1a3b0f6df75e554001956504d19c6"},{"sha":"840d3217b51397a14a4b8d8d5a9f1532c2e18cc0","author":{"name":"Itxaka","email":"42a1f9426daf5f4f16c5cda2bd024855b8924610@gmail.com"},"message":"Merge pull request #1681 from Itxaka/block\n\n[5.0] rabbitmq: block client port on startup","distinct":true,"url":"https://api.github.com/repos/crowbar/crowbar-openstack/commits/840d3217b51397a14a4b8d8d5a9f1532c2e18cc0"}]}
{"actor":{"display_login":"Itxaka"}}