RFE: Extension for improving Nova-Neutron callflow to cache port data

[Ian Wells]

Nova requires some data from a Neutron port and its friends to populate its port info cache, and ultimately to create the metadata constructs that are passed on to VMs to inform them of their addresses and routes. Today, it wanders the datastructures in Neutron, looking at ports' subnets, to get this information.

Instead, https://review.openstack.org/#/c/390513/ proposes that the port gain an attribute or attributes containing the required information. This is a companion RFE to detail that an extension is required in Neutron to provide those attributes (by doing the DB mining locally and returning additional attributes with the data on the port object).

The Nova spec will track the information and ultimately the format of the data (since I don't want to copy it into two locations) and the Neutron extension, being the simpler part of the problem, will implement the returning of this data. Please check and comment on the nova spec for that part of the detail.

[Armando Migliaccio (armando-migliaccio)]

I glanced over the nova spec

[Ian Wells (ijw-ubuntu)]

I need to update the nova spec with the data that's required (though what's there is a reasonable sample) - I'll not get there before the drivers meeting but I should be able to do it this afternoon

[Kevin Benton (kevinbenton)]

I'm okay with the high-level goal. I would rather add a completely new data structure that contains ports and everything else Nova needs so we don't bog down the ports API anymore than we need to.

[Kevin Benton (kevinbenton)]

Please write up a spec for what we need to do on the Neutron side to provide this to Nova.

[Ian Wells (ijw-ubuntu)]

By a 'new data structure' (given this is really a REST API) are you talking /magic-nova-ports/XXX as a thing that returns a read-only structure or did you have something else in mind?

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.