1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
|
<h2>Overview</h2>
<p>There are two major components in a Cisco Nexus 1000V environment:
VSM (Virtual Switch Supervisor) and VEM (Virtual Ethernet Module).
VSM is a virtual machine on a baremetal server. VEM runs inside each host.
VSM, as the name goes, supervises and manages multiple VEMs. <br />
In the OpenStack deployment environment, VSM prepares north
bound REST APIs that communicate with OpenStack Nova Cloud
Controller for network profile configuration, policy profile
notification, network creation, subnet creation, and virtual
machine workload administration.</p>
<p>VSM charm installs the Nexus 1000V virtual switch Supervisor
Module virtual machine onto a MaaS cluster node. A cluster can
have up to 2 VSM in active/standby mode (generally in two different servers).
When the active one fails, the standby will take over within bounded time.</p>
<h2>Usage</h2>
<p>In order to use Cisco Openstack solution we would need to install
VSM on a cluster node as well as VEM module that goes into each
host. In order to provide High Availability for VSM you'll need
to deploy two VSMs (one will be the primary and another the secondary)
in two different hosts. </p>
<p>In order to deploy the VSMs (both primary and secondary), you will
need to create a configuration file where you need to provide specific
configuration of your VSM. To differentiate the different primary
and secondary VSM configuration, we create separate sections for them
on the configuration file and also you deploy as two different service
names.</p>
<p>For example, you create a myconfig.yaml configuration file with the
following info:</p>
<p>vsm-primary:</p>
<pre><code>n1kv-vsm-domain-id: 101
n1kv-vsm-password: password
n1kv-vsm-name: vsm-p
n1kv-vsm-role: primary
n1kv-vsm-mgmt-ip: 10.10.10.10
n1kv-vsm-mgmt-netmask: 255.255.255.0
n1kv-vsm-mgmt-gateway: 10.10.10.1
.....
</code></pre>
<p>vsm-secondary:</p>
<pre><code>n1kv-vsm-domain-id: 101
n1kv-vsm-password: password
n1kv-vsm-name: vsm-s
n1kv-vsm-role: secondary
.....
</code></pre>
<p>Then you deploy the primary VSM with the following command:</p>
<p><code>juju deploy --config myconfig.yaml vsm vsm-primary</code></p>
<p>Then you deploy the secondary VSM with the following command:</p>
<p><code>juju deploy --config myconfig.yaml vsm vsm-secondary</code></p>
<p>To put VEM into VSM supervision, you need to do the following:</p>
<p><code>juju add-relation vsm vem</code></p>
<h2>Contact Information</h2>
<p>Author: Marga Millet <a href="mailto:millet@cisco.com">millet@cisco.com</a></p>
<p>Report bugs at: http://bugs.launchpad.net/charms/+source/vsm</p>
<p>Location: http://jujucharms.com/charms/distro/vsm</p>
|