Description of problem:
This bug is created to track the progress of Stackforge sumission for Cisco VSM(Virtual Supervisor Module) Foreman puppet agent deployment logic.
VSM is a Cisco NX-OS based virtual machine which uses its northbound REST API to communicate with OpenStack Nova Cloud Controller. It maintains a virtual chassis where each slot (from slot 3 to slot 66 or 3 to slot 130) is taken a VEM module (Virtual Ethernet Module) which, in turn, is a virtual switch infra structure provided by N1KV on each server.
Slot 1 and 2 are reserved by Primary and Secondary VSM to provide an High Availability for the whoe distribute virtual switch.
This submission is tracked by two IDs due to some firewall port issues:
I am merging the 2nd one to the 1st one based on reviewers' input.
This is also tracking the work needed to integrate VSM into Foreman from RedHat side..
It's passed all Jenkins/Zuul auto tests.
This is showing the gates. Can you link to the actual puppet modules you want to consider for inclusion?
The source is now in https://github.com/CiscoSystems/puppet-n1k-vsm-archive/tree/rh-n1k-vsm.
Considering the stackforege upstream practice for whole git movement we learn at the code review, we are creating a new git at https://github.com/CiscoSystems/puppet-n1k-vsm where the source files are only contained in the master branch.
This task will
VSM puppetry is accepted at
Creating a pull request to the openstack puppet modules repo. Once accepted the module will be added to the Openstack Puppet Modules RPM
created pull request for openstack puppet modules
Mike, is this likely to land in R5A2 ?
i'm creating a package that includes this bug but i need QA ack in order to push it
corrected to the proper package version
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.
Need to integrate the latest VSM puppetry into the OSP6
Do I need to open a new bug for this request ?
I move the status to New for now, please let me know otherwise
I think you are requesting that we update the version of an existing puppet module. I'd prefer to see a net new bug to so we maintain a clear audit trail.
I'll return this bug to CLOSED_ERRATA so it represents state and we can notify the opm team that a bug will be incoming to request the puppet update.