This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: I5934001d156c2e8061a1de16733ea3076d75efce
Added a check to skip ip configuration in all existing bridge cases.
This was sporadically causing connectivity issue in some setups.
Change-Id: Ia759a84409d477b5be459033aeda37d353c93332
Relaxed the requirment for VSM version to always be specified. The
new code will find the newest available VSM iso and create a copy
of the iso called "current-n1000v.iso". This file will be used for
the remainder of the module.
Change-Id: Icdaa0dba83cb05e8c082786e578a9170666aa3ee
Add support for creating a bridge when the management port is
tagged. Also allows use of management ports that don't have IPs.
Change-Id: I9810fe68b62e690c5e206898eec1320b15eac24b
Added unit tests for the remainder of the module as it stands
today. Also fixed missing dependency for the ovs module.
Change-Id: I498f7d4d2b18a66b782ddb64b5a9f125ea58e416
* Add the required files for unit testing.
* Add a basic test to validate packaging version.
* Fix stdlib syntax to be Puppet compliant.
* Fix lint
Change-Id: I36fd23534e0c724da8d6683fbf2a1e67aa616ebf
Setting the specific version for the nexus-1000v-iso package
causes problems.
Change-Id: I1aaea3a50e5347fe49d516e98e44d9acaa1ab393
Resolves: rhbz#1265389
This patch adds in the option to support pacemaker integration in OSP7.
Specifically when pacemaker integration is enabled two VMs will be
created- one for the primary, and one for the secondary. Neither VM
will be defined or started. Addditionally MACs will be generated for
both VMs to prevent an issue on VSM switchover.
Code was also added to support cases where the VSM needs to be
brought up in setups where there's an existing bridge.
Change-Id: I2ca2ccc12a9db56348440d210eef4bde25142aef
Currently the module can't deploy VSM on a management interface
that is tagged. This commit adds support for these interfaces by
properly handling them from a puppet perspective. Additionally
rather than calling similar code to check if OVS exists we call
the OVS module directly.
Change-Id: I148ee63e354701dbe4db6debc34660e47588ebb7
Changing the class names to avoid duplicate declaration error when adding n1k_vsm
puppet module to controller host group. The conflict is with ovs.pp
Change-Id: I5b49c7b2ec3fbb3a7078bc388c00b42f722f4081
Since puppet 3.x, Puppet Labs Forge accept only the metadata.json file
for module description (Modulefile is now deprecated).
This patch :
- convert the Modulefile to metadata.json.
- switch to stackforge namespace.
- relax pe version_requirement to 3.x.
- added a common gitignore (ignore pkg)
Change-Id: Idc82bed42bc2955bd5f46dd2bd80fff13542d97b
Cisco stackforge/puppet-n1k-vsm misses some files and changes to succesfully start
the puppet-n1k-vsm project. This commit addresses those changes to make sure we
can start committing stuff to this project.
Details of the changes:
- Rake and Gemfile files are needed for gate tests.
- Added the license and Modulefile files
- Changed manifest files to pass lint case and initial Unit Testing.
Change-Id: Ia65c8e09c9388709d1834ec7a4a120dfaef807ed