Merge lp:~jose/charms/precise/vsm/fix-readme into lp:~springfield-team/charms/precise/vsm/trunk

Proposed by José Antonio Rey
Status: Merged
Merged at revision: 29
Proposed branch: lp:~jose/charms/precise/vsm/fix-readme
Merge into: lp:~springfield-team/charms/precise/vsm/trunk
Diff against target: 144 lines (+54/-68)
1 file modified
README.md (+54/-68)
To merge this branch: bzr merge lp:~jose/charms/precise/vsm/fix-readme
Reviewer Review Type Date Requested Status
Marga Millet Pending
Review via email: mp+215973@code.launchpad.net

Description of the change

I have fixed the README.md file to be in Markdown, in order for it to display properly on the Juju GUI.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'README.md'
2--- README.md 2014-04-15 21:45:09 +0000
3+++ README.md 2014-04-15 22:04:35 +0000
4@@ -1,86 +1,72 @@
5-<h2>Overview</h2>
6+# Overview
7
8-<p>There are two major components in a Cisco Nexus 1000V environment:
9+There are two major components in a Cisco Nexus 1000V environment:
10 VSM (Virtual Switch Supervisor) and VEM (Virtual Ethernet Module).
11 VSM is a virtual machine on a baremetal server. VEM runs inside each host.
12-VSM, as the name goes, supervises and manages multiple VEMs. <br />
13+VSM, as the name goes, supervises and manages multiple VEMs.
14+
15 In the OpenStack deployment environment, VSM prepares north
16 bound REST APIs that communicate with OpenStack Nova Cloud
17 Controller for network profile configuration, policy profile
18 notification, network creation, subnet creation, and virtual
19-machine workload administration.</p>
20+machine workload administration.
21
22-<p>VSM charm installs the Nexus 1000V virtual switch Supervisor
23+VSM charm installs the Nexus 1000V virtual switch Supervisor
24 Module virtual machine onto a MaaS cluster node. A cluster can
25 have up to 2 VSM in active/standby mode (generally in two different servers).
26-When the active one fails, the standby will take over within bounded time.</p>
27-
28-<h2>Usage</h2>
29-
30-<p>In order to use Cisco Openstack solution we would need to install
31+When the active one fails, the standby will take over within bounded time.
32+
33+# Usage
34+
35+In order to use Cisco Openstack solution we would need to install
36 VSM on a cluster node as well as VEM module that goes into each
37 host. In order to provide High Availability for VSM you'll need
38 to deploy two VSMs (one will be the primary and another the secondary)
39-in two different hosts. </p>
40+in two different hosts.
41
42-<p>In order to deploy the VSMs (both primary and secondary), you will
43+In order to deploy the VSMs (both primary and secondary), you will
44 need to create a configuration file where you need to provide specific
45 configuration of your VSM. To differentiate the different primary
46 and secondary VSM configuration, we create separate sections for them
47 on the configuration file and also you deploy as two different service
48-names.</p>
49-
50-<p>For example, you create a myconfig.yaml configuration file with the
51-following info:</p>
52-
53-<p>vsm-primary:</p>
54-
55-<pre><code>n1kv-vsm-domain-id: 101
56-
57-n1kv-vsm-password: password
58-
59-n1kv-vsm-name: vsm-p
60-
61-n1kv-vsm-role: primary
62-
63-n1kv-vsm-mgmt-ip: 10.10.10.10
64-
65-n1kv-vsm-mgmt-netmask: 255.255.255.0
66-
67-n1kv-vsm-mgmt-gateway: 10.10.10.1
68-
69-.....
70-</code></pre>
71-
72-<p>vsm-secondary:</p>
73-
74-<pre><code>n1kv-vsm-domain-id: 101
75-
76-n1kv-vsm-password: password
77-
78-n1kv-vsm-name: vsm-s
79-
80-n1kv-vsm-role: secondary
81-
82-.....
83-</code></pre>
84-
85-<p>Then you deploy the primary VSM with the following command:</p>
86-
87-<p><code>juju deploy --config myconfig.yaml vsm vsm-primary</code></p>
88-
89-<p>Then you deploy the secondary VSM with the following command:</p>
90-
91-<p><code>juju deploy --config myconfig.yaml vsm vsm-secondary</code></p>
92-
93-<p>To put VEM into VSM supervision, you need to do the following:</p>
94-
95-<p><code>juju add-relation vsm vem</code></p>
96-
97-<h2>Contact Information</h2>
98-
99-<p>Author: Marga Millet <a href="&#x6D;&#x61;i&#x6C;&#116;o:&#x6D;&#105;&#108;&#x6C;&#101;&#x74;&#64;&#99;&#105;&#115;&#99;&#111;&#46;&#99;&#x6F;&#109;">&#x6D;&#105;&#108;&#x6C;&#101;&#x74;&#64;&#99;&#105;&#115;&#99;&#111;&#46;&#99;&#x6F;&#109;</a></p>
100-
101-<p>Report bugs at: http://bugs.launchpad.net/charms/+source/vsm</p>
102-
103-<p>Location: http://jujucharms.com/charms/distro/vsm</p>
104+names.
105+
106+For example, you create a myconfig.yaml configuration file with the
107+following info:
108+
109+ vsm-primary:
110+ n1kv-vsm-domain-id: 101
111+ n1kv-vsm-password: password
112+ n1kv-vsm-name: vsm-p
113+ n1kv-vsm-role: primary
114+ n1kv-vsm-mgmt-ip: 10.10.10.10
115+ n1kv-vsm-mgmt-netmask: 255.255.255.0
116+ n1kv-vsm-mgmt-gateway: 10.10.10.1
117+ .....
118+
119+ vsm-secondary:
120+ n1kv-vsm-domain-id: 101
121+ n1kv-vsm-password: password
122+ n1kv-vsm-name: vsm-s
123+ n1kv-vsm-role: secondary
124+ .....
125+
126+
127+Then you deploy the primary VSM with the following command:
128+
129+ juju deploy --config myconfig.yaml vsm vsm-primary
130+
131+Then you deploy the secondary VSM with the following command:
132+
133+ juju deploy --config myconfig.yaml vsm vsm-secondary
134+
135+To put VEM into VSM supervision, you need to do the following:
136+
137+ juju add-relation vsm vem
138+
139+
140+# Contact Information
141+
142+Author: Marga Millet <millet@cisco.com>
143+Report bugs at: http://bugs.launchpad.net/charms/+source/vsm
144+Location: http://jujucharms.com/

Subscribers

People subscribed via source and target branches