VSD/VSC rollback, DNS/NTP/Generic VM deploy, bug fixes

What's new

1. Rollback for VSD and VSC on KVM platform. See UPGRADE.md.
2. Added support to specify custom xmpp URL for clustered VSD deployments
3. Added support for preserving gateway purge timer during upgrades. See UPGRADE.md.
4. Added fix for ElasticSearch bug reported in Issue #162.
5. Added support for DNS/NTP server
6. Added fix to enable TLS on all VSDs when deploying VNS on a VSD cluster.
7. Added support for deploying DNS (Uses STATS VM as image...)
8. Added support for deploy/destroy generic VM (qcow2 only with XML predefined)
9. Created Metro Playbook Categories (Core, Experimental, Lab) to indicate the support model for various playbooks.

Build vars, unzip, and upgrade preview

What's new

1. Preview support for VSD/VSC upgrade. See UPGRADE.md.
2. Moved build variables out of build.yml, creating build_vars.yml. See BUILD.md.
3. Simplified and renamed a few build variables.
4. Renamed nuage-unpack to nuage-unzip and decoupled from build. Now you run nauge_unzip.yml if and only if you want to unzip tar.gz files.
5. Added support for identifying the operation you are performing on each component. See build_vars.yml.
6. Added support to use custom hypervisor and Ansible host usernames. Default is root.
7. Added check to verify that NTP servers are specified using the proper format.
8. Added support for up to 6 NSGV ports and enhanced bootstrap support.
9. Added acpi support for NSGV.
10. Added support for specifying ssh keys to be used during deployment and upgrades.
11. Moved user credentials to an external file, user_creds.yml.
12. Added support to launch Spirent STCv test ports.
13. Added RELEASE_NOTES.md

Bug fix for VSD deploy of pre-4.0 code

Found and fixed a bug that was not pinning the VSD OS prior to executing yum update. Without the fix, CentOS on the VSD would be updated to 6.8, causing the VSD install to fail.

VMware ESXi, mixed VRS target architecture

What's new:

1. Added pre-deploy support for VMware. Tested on R4.0R6.1 and 4.0R7.
2. Added support for mixed VRS architectures. That is, you can have some VRSs deployed on Ubuntu and some on RedHat/CentOS all using a single build.yml file.
3. Enhanced support for Dockermon install.
4. Documentation enhancements, including examples and how-tos.
5. Several bug fixes and infrastructure upgrades, including enhanced OpenStack deployment support and Jenkins CI integration.
6. Tested with 3.2R8, 4.0R4, and 4.0R7

Added HOWTO and examples

Added HOWTO.md and an examples\ directory. Fixed bugs in unpack. Made consistency changes to the configuration files for our automated tests.

Enable single-element unpack

Previously, the nuage-unpack role was expecting to find all possible binary files on disk in order to run without error. This change makes it possible to create a build.yml file that deploys only VSD, or only VSD+VSC. In these cases, only the VSD and VSC binary files will need to be present.

Heat, VNS, Health

What's new:

1. Added VRS Health check.
2. Added Dockermon version support.
3. Enhanced testing of stand-alone component deployments.
4. Added support for deploying on OpenStack via HEAT.
5. Added support for vnsutil and nsg-v.
6. Enhanced NTP sync on VSD.
7. Tested with 3.2R8 and 4.0R4

Phase 1 VNS support, new build step, and archive unpacking

This release delivers many updates to the v1.0 release, including but not limited to:

• Introduction of VNS support in the form of dispatchers that deploy the VNS utility VM and an NSG-V configured for zero-factor bootstrap
• Introduction of a new build step, consolidating all user-modified variables into a single file, build.yml. The build playbook uses those inputs to populate ansible variables in several places required so that you don't have to.
• Introduction of a nuage-unpack step that takes binary archives, unpacks them to the appropriate places, and updates the ansible variables that specify their location. You can still supply unpacked qcow2 files and binary packages if you prefer.
• Refactoring to enable the support of target servers other than KVM. This is an architectural change that paves the way for support of VMware, HyperV, and so on.
• Many bug fixes