You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Daniel Alvarez ad1fea3e7b Metadata agent support in networking-ovn ... Initial implementation Changes in the mechanism driver: * Automatically create a port with device_owner=network:dhcp to serve metadata and eventually DHCP. * Auto-allocate an IP for the metadata port on subnet creation. * Push static route for 169.254.169.254 in DHCP options. * Wait until metadata service is provisioned in the chassis where a port resides before sending the event to Nova. Agent: * Implementation of [0]. Devstack plugin: * Starts networking-ovn-agent with the proper config files. * Disables config drive in nova.conf for tempest against master branch. * Enables TEMPEST_RUN_VALIDATION for tempest against master branch. In order to test this patch out we need to make these changes to nova.conf: * [DEFAULT] section: force_config_drive = False * [neutron] section: service_metadata_proxy = True This patch depends on [1] and [2] (already merged into OVS master). NOTE: Metadata tests are only enabled for the non-voting tempest job which runs against OVS master branch. The release job runs against OVS 2.7 which doesn't include [1][2] so those tests are disabled until OVS 2.8 is released. [0] https://docs.openstack.org/developer/networking-ovn/design/metadata_api.html [1] https://patchwork.ozlabs.org/patch/767369/ [2] https://patchwork.ozlabs.org/patch/771297/ Change-Id: Ife2fd18f2f88050429e70c7e557fa41d2d54b034		6 years ago
..
networking-ovn	Metadata agent support in networking-ovn	6 years ago