commit 568ea90f5a52331c64f81302303ced72143e50a1
Author: Adam Gandelman <email address hidden>
Date: Wed Dec 9 16:48:15 2015 -0800
Push orchestrator config into the appliance
This pushes a couple of flags into the appliance that are specific to the
individual orchestrator instance managing that appliance. Initially, we use
it to tell the appliance where the metadata proxy is listening. Previously,
this was hard-coded to a known address on the network. With multiple
orchestrators in a clustered env, this will allow each to run their own
metadata proxy and have only their managed appliances querying that.
Another patch will follow that will ensure this is up to date when rebalances
occur and orchestrators take over new appliances.
Reviewed: https:/ /review. openstack. org/255612 /git.openstack. org/cgit/ openstack/ astara/ commit/ ?id=568ea90f5a5 2331c64f8130230 3ced72143e50a1
Committed: https:/
Submitter: Jenkins
Branch: master
commit 568ea90f5a52331 c64f81302303ced 72143e50a1
Author: Adam Gandelman <email address hidden>
Date: Wed Dec 9 16:48:15 2015 -0800
Push orchestrator config into the appliance
This pushes a couple of flags into the appliance that are specific to the
individual orchestrator instance managing that appliance. Initially, we use
it to tell the appliance where the metadata proxy is listening. Previously,
this was hard-coded to a known address on the network. With multiple
orchestrators in a clustered env, this will allow each to run their own
metadata proxy and have only their managed appliances querying that.
Another patch will follow that will ensure this is up to date when rebalances
occur and orchestrators take over new appliances.
Change-Id: Ib502507b29f171 46da81f61f34957 cd96a1548f4
Partial-bug: #1524068