Support for Cisco ML2 Mech Driver

Partially Implements: blueprint support-ml2-nexus-driver

Change-Id: I5e0486c9db22abfcbab205e6f57bbafe8f0b5dd4
(Cherry-picked from master:
68ddc7a81145999594a4b52d2e59e5874aac0d10
3848a2b411f9a78b7f773b789a2d57daff176cc5)

Conflicts:
	manifests/plugins/ml2/cisco/nexus.pp
	manifests/plugins/ml2/cisco/nexus_creds.pp
	spec/classes/neutron_plugins_cisco_ml2_spec.rb
Add plugin config file to /etc/default/neutron-server

Debian platforms uses /etc/default/neutron-server to tell
neutron-server service which plugin configuration file to load.

Configure it.

Change-Id: I0638d2584ad327ae1ed77f672d5efb1c28064aa2
Closes-bug: #1357431
(cherry picked from commit c848aff801e7c84740eae661da3c0c101a930628)
Makes ca_file parameter optional when use_ssl => true

The ca_file parameter should not be required when use_ssl => true.  Rather,
use_ssl must be true when ca_file is specified.

Change-Id: Ifb4b5acccdce0be63e763b4d837eb452827cd6d4
Closes-Bug: 1356089
New manifest file to deploy Cisco N1KV-VEM

Background on 'N1KV-VEM’: It is the host-side component of N1KV
implementing the notion of Virtual Ports for VM Interfaces and also
handling the VM data-traffic. VEM is implemented as a couple of
user-space processes and also has a KLM for efficient data-path
switching.

VEM manifests does: setting up the Config-File for VEM service,
Starting VEM service and finally adding physical ports (along with
port-profile) to the VEM

Change-Id: Ibc8f1c4d2d743589e452ae6d1d87b5bfa123bc3a
Add ability to manage Neutron ML2 plugin package state

Introduce the package_ensure parameter to add the ability
to manage Neutron ML2 plugin package state.

Closes-bug: #1355370
Change-Id: I3bf6ed68015c13cf61db1b43dfbf4fd3c845d00f