Expose & Document Cisco plugin configuration for Havana

Bug #1276168 reported by Pradeep Kilambi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
Fix Released
Critical
Mark T. Voelker
Havana
Fix Released
Critical
Mark T. Voelker

Bug Description

In our current havana release, the cisco plugin configuration is not easily visible to the end user to configure in the user.yaml files. We need to expose the default options for cisco-nexus plugin configuration and document the same.

Changed in openstack-cisco:
assignee: nobody → Mark T. Voelker (mvoelker)
status: New → In Progress
Revision history for this message
Mark T. Voelker (mvoelker) wrote :

A few things that would make life easier for people here:

1.) There's a bug in the Neutron sample configs. Starting in Havana, section headers (with one exception apparently) were normalized to lowercase, but the OVS sample configs were never updated. I've got a patch out for that:

https://bugs.launchpad.net/neutron/+bug/1279418
https://review.openstack.org/#/c/72986/

2.) The Cisco plugin wiki page (which the Neutron README links to) similarly mis-capitalizes section headers. I've fixed that:

https://wiki.openstack.org/w/index.php?title=Cisco-neutron&diff=prev&oldid=42037

3.) The Cisco plugin wiki page also doesn't mention that the OVS and Cisco plugin configs can now both go in /etc/neutron/plugins/cisco/cisco_plugins.ini file. Doing so allows you to start neutron-server with:

/usr/bin/python /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file /var/log/neutron/server.log --config-file /etc/neutron/plugins/cisco/cisco_plugins.ini

instead of:

/usr/bin/python /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file /var/log/neutron/server.log --config-file /etc/neutron/plugins/cisco/cisco_plugins.ini --config-file/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

The distinction is somewhat important because most init scripts seem to only call neutron-server with a single --config-file argument. I've amended the documentation to reflect this:

https://wiki.openstack.org/w/index.php?title=Cisco-neutron&diff=prev&oldid=42040

There's also going to be a refactor needed of the puppet-neutron module, the puppet-coe module, and some of the YAML files in puppet_openstack_builder to make this all easier and clean out some junk leftover from Grizzly. I have a starter branch for puppet-coe here and I'll add links to the rest as I get them posted:
https://github.com/CiscoSystems/puppet-coe/pull/38

Revision history for this message
Mark T. Voelker (mvoelker) wrote :

The puppet-coe patch has been tested and landed successfully. I'd like to make a small change to the composition layer to tidy up the configuration and make it more obvious to the end user how to set it up. Once that's done we can add more in-depth documentation to the wiki if necessary and call this done.

Revision history for this message
Mark T. Voelker (mvoelker) wrote :
Changed in openstack-cisco:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.