{"push_id":597601306,"size":2,"distinct_size":2,"ref":"refs/heads/stable/juno","head":"336bfc4955784605e126a0280ab199d09bd78f40","before":"df097533ff2a298d1df4acc9200170e47efa0b7b","commits":[{"sha":"acefbcb20408ec6ee1fe666524a2a20449969f1f","author":{"email":"aa71f94694e581551b4f662abcc23a9271bdb41d@vmware.com","name":"Gary Kotton"},"message":"VMware: fix exception when multiple compute nodes are running\n\nA number of operations in the VMwareVCDriver class first validate\nthat instances node is the cluster that is mapped to the compute\nnode. This is problematic when the compute nodes have different\nconfigurations, for example, each compute node is mapped to a\ndifferent cluster.\n\nIn this case many operations that are just performing instance operations\nwill fail. This patch ensure that all instance operations that do not\nrequire a cluster or volume will make use of the base _vmops class.\nThis is due to the fact that it only requires the instance details\nto interface with the VC and there are no specific cluster operations.\n\nChange-Id: I2bc38a480f2feb12ea41e7d28f80b29dd49a79b8\nCloses-bug: #1345460\n(cherry picked from commit 8e4a9156f4dccf003970848c28b8a9d15c55212d)","distinct":true,"url":"https://api.github.com/repos/mandeepdhami/nova/commits/acefbcb20408ec6ee1fe666524a2a20449969f1f"},{"sha":"336bfc4955784605e126a0280ab199d09bd78f40","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"VMware: fix exception when multiple compute nodes are running\" into stable/juno","distinct":true,"url":"https://api.github.com/repos/mandeepdhami/nova/commits/336bfc4955784605e126a0280ab199d09bd78f40"}]}