Public bug reported:
While extending the existing ML2 port binding unit tests to cover DVR
distributed port binding (bug 1453943), I ran into a number of issues
where the PortContext passed to ML2 mechanism drivers does not provide
the information needed for distributed ports or provides it
inconsistently. This is likely to prevent existing mechanism drivers for
ToR switches from working with DVR ports, and tests have reportedly
shown this to be the case.
When DVR was introduced, the host, original_host, status, and
original_status attributes were added to PortContext to provide drivers
with the host-specific details of distributed (or normal) ports. But the
current and previous port dictionary attributes also contain some host-
specific information, such as the VIF type, for distributed ports. New
attributes need to be added for host-specific current and previous VIF
type and details, and the current and previous port dictionaries should
contain only the host-independent information that is returned from REST
operations.
Also, the existing original_status and original_host PortContext
attributes should return None when in the context of create or delete
operations, and original_host should reflect the host for which a
distributed port operation is being performed.
** Affects: neutron
Importance: High
Assignee: Robert Kukura (rkukura)
Status: In Progress
** Tags: l3-dvr-backlog ml2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1453955
Title:
ML2 mechanism driver DVR PortContext info incomplete/inconsistent
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
While extending the existing ML2 port binding unit tests to cover DVR
distributed port binding (bug 1453943), I ran into a number of issues
where the PortContext passed to ML2 mechanism drivers does not provide
the information needed for distributed ports or provides it
inconsistently. This is likely to prevent existing mechanism drivers
for ToR switches from working with DVR ports, and tests have
reportedly shown this to be the case.
When DVR was introduced, the host, original_host, status, and
original_status attributes were added to PortContext to provide
drivers with the host-specific details of distributed (or normal)
ports. But the current and previous port dictionary attributes also
contain some host-specific information, such as the VIF type, for
distributed ports. New attributes need to be added for host-specific
current and previous VIF type and details, and the current and
previous port dictionaries should contain only the host-independent
information that is returned from REST operations.
Also, the existing original_status and original_host PortContext
attributes should return None when in the context of create or delete
operations, and original_host should reflect the host for which a
distributed port operation is being performed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1453955/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
