{"push_id":675390207,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"dac4414bcc87e029a41f872814a8647dd95d043f","before":"eee6d7778d377c11de34d2b0b2c45e3439ebb24a","commits":[{"sha":"051cac62ebe60f720dd1844ab0d64b6880c42f98","author":{"email":"f131bf03abf9995c2a0d18ad727a0a4241b4f24e@redhat.com","name":"Greg Blomquist"},"message":"Create unique binding queue names for RabbitMQ\n\nWhen CFME connects to RabbitMQ to collect OpenStack events, it creates queues to\nbind to the OpenStack services' exchanges.  The queues were named after the\nservices to which they were bound.  For example, binding to the \"nova\" service\nwould result in a binding queue called \"nova\".\n\nIf more than one appliance attempted to connect to RabbitMQ to collect OpenStack\nevents, only the first appliance to create the binding queue would receive any\nevents.\n\nNow, the binding queue is named after the appliance connecting to the RabbitMQ\nservice.  The new binding queue name will look like \"miq-<host|ip>-<exchange>\"\n\n * e.g.: \"miq-10.10.10.10-nova\"\n\nThis allows for two things:  individual appliances will get their own binding\nqueue per service, and administrators will be able to tell which binding queues\nbelong to which appliances.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=1223976","distinct":true,"url":"https://api.github.com/repos/ManageIQ/manageiq/commits/051cac62ebe60f720dd1844ab0d64b6880c42f98"},{"sha":"dac4414bcc87e029a41f872814a8647dd95d043f","author":{"email":"4404c26c82eea684eb4004177464b4faaf5500a0@gmail.com","name":"Jason Frey"},"message":"Merge pull request #2995 from blomquisg/bz1223976-no-openstack-rabbit-events\n\nRename RabbitMQ binding queues","distinct":true,"url":"https://api.github.com/repos/ManageIQ/manageiq/commits/dac4414bcc87e029a41f872814a8647dd95d043f"}]}