The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Before you can deploy the Cisco Nexus 1000V for KVM, you need to configure several charms with specific configuration information. You do this by defining specific charm parameters in a global configuration file that you create.
Note | You must maintain consistency between the global configuration file parameter names and the charm's config.yaml file parameter names. Do not introduce new parameter names in the global configuration file. |
If your deployment requires it, you can deploy VEMs with unique configuration parameters instead of using the configuration parameters that are defined for all VEMs in the config.yaml file. To do this, you need to create a mapping file.
You must modify the global configuration file for the following Cisco Nexus 1000V for KVM-related OpenStack charms:
openstack-origin:deb https://user:password@private-ppa.launchpad.net/springfield-team/havana-staging-2013.2.2/ubuntu precise main|key-id
The following sections provide information about the OpenStack charm parameters that you need to define in the global configuration file.
Parameter |
Description |
---|---|
openstack-origin: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
n1kv-vsm-username: vsm-username |
Login for accessing the Cisco Nexus 1000V for KVM (VSM). |
n1kv-vsm-password: vsm-password |
Secure password for accessing the Cisco Nexus 1000V for KVM (VSM). |
n1kv-vsm-ip: vsm-ip-address |
IP address of the VSM. |
nova-cloud-controller: openstack-origin: deb https://joe:wxyPMyJlHt0WCbWCLzLc@private-ppa.launchpad.net/springfield-team/havana-staging-2013.2.2/ubuntu precise main|ABCDEFABCDEFABC n1kv-vsm-username: nexus n1kv-vsm-password: nexus123 n1kv-vsm-ip: 192.168.10.1 . . .
Parameter |
Description |
---|---|
openstack-origin: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
nova-comute: openstack-origin: deb https://joe:wxyPMyJlHt0WCbWCLzLc@private-ppa.launchpad.net/springfield-team/havana-staging-2013.2.2/ubuntu precise main|ABCDEFABCDEFABC . . .
Parameter |
Description |
---|---|
openstack-origin: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
l3-agent: {enable | disable} |
|
quantum-gateway: openstack-origin: deb https://joe:wxyPMyJlHt0WCbWCLzLc@private-ppa.launchpad.net/springfield-team/havana-staging-2013.2.2/ubuntu precise main|ABCDEFABCDEFABC n1kv-agent: enable . . .
Parameter |
Description |
---|---|
openstack-origin: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
This example shows the openstack-dashboard portion of the global configuration file:
openstack-dashboard: openstack-origin: deb https://joe:wxyPMyJlHt0WCbWCLzLc@private-ppa.launchpad.net/springfield-team/havana-staging-2013.2.2/ubuntu precise main|ABCDEFABCDEFABC . . .
This table lists the Cisco Nexus 1000V for KVM VSM charm parameters that you need to define in the global configuration file.
n1kv-source:deb https://user:password@private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|key-id
Parameter |
Description |
---|---|
n1kv-source: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
n1kv-vsm-domain-id: domain-id |
Domain number that the VSM will control. |
n1kv-vsm-password: vsm-password |
Secure password for accessing the Cisco Nexus 1000V for KVM (VSM). |
n1kv-vsm-name: vsm-name |
Name of the VSM. |
n1kv-vsm-role: {primary | secondary} |
High availability role. Valid values are primary or secondary. |
n1kv-vsm-ip: management-IP-address |
IP address of the management interface. |
n1kv-vsm-mgmt-netmask: management-ip-subnet-mask |
IP address subnet mask of the management interface. |
n1kv-vsm-gateway: management-subnet-default -gateway |
IP address of the management subnet default gateway. |
n1kv-vsm-ctrl-mac: |
MAC address of the VSM's control TAP interface. This parameter is optional for the primary VSM, but required for the secondary VSM. |
n1kv-vsm-mgmt-mac |
MAC address of the VSM's management TAP interface. This parameter is optional for the primary VSM, but required for the secondary VSM. |
n1kv-vsm-pkt-mac: |
MAC address of the VSM's packet TAP interface. This parameter is optional for the primary VSM, but required for the secondary VSM. |
n1kv-vsm-console-pts: |
(Optional) Console port of the VSM VM. |
n1kv-vsm-vm-vcpu: |
(Optional) Number of vCPUs in the VSM VM. The default and recommended value is two vCPUs. |
n1kv-vsm-disk-size: |
(Optional) Disk size (GB) of the VSM VM. |
n1kv-phy-intf-bridge: |
(Optional) Host interface to which the VSM bridge is attached. The bridge connects the VSM with the upstream network. The default value is Ethernet 0 (eth0). |
This example shows the primary VSM portion of the global configuration file:
vsm-primary: n1kv-source: deb https://joe:wxyPMyJlHt0WCbWCLzLc@https://private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|ABCDEFABCDEFABC n1kv-vsm-domain-id: 101 n1kv-vsm-password: nexus123 n1kv-vsm-name: vsm-primary n1kv-vsm-role: primary n1kv-vsm-ip: 192.168.10.2 n1kv-vsm-mgmt-netmask: 255.255.255.0 n1kv-mgmt-gateway: 192.168.10.3 . . .
This example shows the secondary VSM portion of the global configuration file:
vsm-secondary: n1kv-source: deb https://joe:wxyPMyJlHt0WCbWCLzLc@https://private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|ABCDEFABCDEFABC n1kv-vsm-domain-id: 101 n1kv-vsm-password: nexus123 n1kv-vsm-name: vsm-secondary n1kv-vsm-role: secondary n1kv-vsm-ip: 0.0.0.0 n1kv-vsm-mgmt-netmask: 0.0.0.0 n1kv-mgmt-gateway: 0.0.0.0 n1kv-vsm-ctrl-mac: 00:01:00:00:00:00 n1kv-vsm-mgmt-mac: 00:02:00:00:00:00 n1kv-vsm-pkt-mac: 00:03:00:00:00:00 . . .
This table lists the Cisco Nexus 1000V for KVM VEM charm parameters. You define the parameters that will be the same among all of the VEMs in your network. For any parameters that you want to customize, you create a mapping file in YAML syntax in the MAAS node’s file system. In the mapping file, you configure a section for each node by using the node ID and include any of the VEM configuration parameters listed in this table.
n1kv-source:deb https://user:password@private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|key-id
Parameter |
Description |
---|---|
n1kv-source: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
vtep_config: virt port-name profile profile-name [mode static | dhcp [address ip-address]] |
Virtual Tunnel Endpoint (VTEP) port configuration. Only static IP and MAC addresses are supported. |
n1kv-node_type: {compute | network} |
Type of node that the VEM is intended to be installed on. The default value is compute. |
n1kv-vtep_in_same_subnet: {yes | no} |
Setting that indicates whether multiple VTEPs are located in the same subnet. The default value is no. |
This example shows the VEM portion of the global configuration file:
vem: n1kv-source: deb https://joe:wxyPMyJlHt0WCbWCLzLc@private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|ABCDEFABCDEFABC vtep_config: node-type: network vtep_in_same_subnet: yes vtep_config:'virt vtep1-nw2 profile vxlan-vtep mode static address 6.0.8.253 netmask 255.255.0.0 mac 0e:1f:56:cf:82:53' . . .
This example shows a mapping file with configuration parameters for two nodes. Each section is separated by the node ID. Within each section, node-specific parameters are defined because they are different from the ones in the config.yaml file.
maas-node-6: host_mgamt_intf: eth1 uplink_profile: phys eth2 profile sys-uplink maas-node-11: host-mgmt-intf: eth0 uplink_profile: phys eth0 profile sys-uplink node_type: network vtep_config:'virt vtep1-nw2 profile vxlan-vtep mode static address 6.0.8.253 netmask 255.255.0.0 mac 0e:1f:56:cf:82:53'
You must modify the global configuration file for the vxlan-gateway charm.
The following table lists the Cisco Nexus 1000V for KVM VXLAN Gateway charm parameter that you need to define in the global configuration file.
n1kv-source:deb https://user:password@private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|key-id
Parameter |
Description |
---|---|
n1kv-source: debian-pkg-location |
Location of the Cisco Nexus 1000V for KVM Debian package. |
This example shows the VXLAN Gateway portion of the global configuration file:
vxlan-gateway: n1kv-source: deb https://joe:wxyPMyJlHt0WCbWCLzLc@https://private-ppa.launchpad.net/springfield-team/n1kv-staging/ubuntu precise main|ABCDEFABCDEFABC . . .