When using DVR and L3HA neutron deployment options,
Nova API Metadata requests are served from compute nodes,
instead of from neutron-gateway nodes.
This change allows nova-compute to receive vendor_data
configuration values from nova-cloud-controller charm
relation and write to nova-compute's nova.conf
appropriately.
This will be effictive for Queens and later OpenStack
releases.
Synced charm-helpers in order to import new context
for writing the vendor_data.json file.
Reviewed: https:/ /review. opendev. org/657672 /git.openstack. org/cgit/ openstack/ charm-nova- compute/ commit/ ?id=af051c4fba0 b5ff2db62a908ab 9fad688353750c
Committed: https:/
Submitter: Zuul
Branch: master
commit af051c4fba0b5ff 2db62a908ab9fad 688353750c
Author: Rodrigo Barbieri <email address hidden>
Date: Thu May 9 16:15:04 2019 -0300
Propagate vendor_data from nova-cloud- controller
When using DVR and L3HA neutron deployment options,
Nova API Metadata requests are served from compute nodes,
instead of from neutron-gateway nodes.
This change allows nova-compute to receive vendor_data controller charm
configuration values from nova-cloud-
relation and write to nova-compute's nova.conf
appropriately.
This will be effictive for Queens and later OpenStack
releases.
Synced charm-helpers in order to import new context
for writing the vendor_data.json file.
Change-Id: I0c79e1bfac9fbe 7009a7e862ad010 cfa2de8cfda
Closes-Bug: #1777714