yahoo-eng-team team mailing list archive

[Ian Wells <iawells@xxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1640956

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

Status in neutron:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1640956/+subscriptions