Bug 1085172

Summary: [RFE][neutron]: Add the capability to sync neutron resources to the N1kv VSM
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-neutronAssignee: lpeer <lpeer>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: chrisw, dontu, ihrachys, markmc, nyechiel, sclewis, sthillma, tdunnon, yeylon
Target Milestone: z2Keywords: FutureFeature, OtherQA, Triaged, ZStream
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-2014.1.3-5.el7ost Doc Type: Enhancement
Doc Text:
Feature: Synchronize resources between Neutron and N1kV on Neutron startup. Reason: Neutron and N1kV configurations can end up out of sync, so there should be a mechanism to sync them to resolve this. Result: Add mechanism to sync the resources on Neutron boot.
Story Points: ---
Clone Of:
: 1156523 (view as bug list) Environment:
Last Closed: 2014-11-03 08:37:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1154159, 1154162, 1156523, 1174319, 1174326    

Description RHOS Integration 2014-04-08 04:05:05 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/cisco-n1kv-full-sync.

Description:

Add support to synchronize the state of the neutron database and N1kv VSM(controller) in Cisco N1kv neutron plugin.


Specification URL (additional information):

None

Comment 1 dontu 2014-07-08 19:22:40 UTC
BP filed... Waiting for approval. Need this enhancement in OSP5. Code currently in our local git repo. Will be pushed for review once UT tests are added.

Comment 2 dontu 2014-08-09 01:38:14 UTC
Patch pushed to master for review

Comment 6 errata-xmlrpc 2014-11-03 08:37:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2014-1786.html