Merge lp:~annegentle/nova/installdoc into lp:~hudson-openstack/nova/trunk

Proposed by Anne Gentle
Status: Merged
Approved by: Eric Day
Approved revision: 449
Merged at revision: 458
Proposed branch: lp:~annegentle/nova/installdoc
Merge into: lp:~hudson-openstack/nova/trunk
Diff against target: 221 lines (+67/-36)
6 files modified
doc/source/adminguide/managing.networks.rst (+1/-1)
doc/source/adminguide/multi.node.install.rst (+9/-27)
doc/source/adminguide/single.node.install.rst (+2/-2)
doc/source/cloud101.rst (+8/-3)
doc/source/index.rst (+1/-3)
doc/source/livecd.rst (+46/-0)
To merge this branch: bzr merge lp:~annegentle/nova/installdoc
Reviewer Review Type Date Requested Status
Eric Day (community) Approve
Soren Hansen (community) Approve
Jonathan Bryce (community) Approve
Review via email: mp+43022@code.launchpad.net

Description of the change

Added LiveCD info as well as some changes to reflect consolidation of .conf files.

To post a comment you must log in.
Revision history for this message
Soren Hansen (soren) wrote :

2010/12/7 Anne Gentle <email address hidden>:
> === modified file 'doc/source/adminguide/multi.node.install.rst'
> --- doc/source/adminguide/multi.node.install.rst        2010-12-02 19:48:39 +0000
> +++ doc/source/adminguide/multi.node.install.rst        2010-12-07 22:51:58 +0000
[...]
> -4. Create a nova group
> -
> -::
> +   --fixed_range=<network/prefix>   # ip network to use for VM guests, ex 192.168.2.64/26
> +   --network_size=<# of addrs>      # number of ip addrs to use for VM guests, ex 64
> +
> +   --fixed_range=<network/prefix>   # ip network to use for VM guests, ex 192.168.2.64/26
> +   --network_size=<# of addrs>      # number of ip addrs to use for VM guests, ex 64
> +

I think specifying these once is sufficient :)

--
Soren Hansen
Ubuntu Developer    http://www.ubuntu.com/
OpenStack Developer http://www.openstack.org/

Revision history for this message
Anne Gentle (annegentle) wrote :

Heh. Yes. :)

lp:~annegentle/nova/installdoc updated
448. By Anne Gentle

removing extraneous config ilnes

Revision history for this message
Jonathan Bryce (jbryce) wrote :

looks good now

review: Approve
lp:~annegentle/nova/installdoc updated
449. By Anne Gentle

Fixed spelling errors in index.rst

Revision history for this message
Soren Hansen (soren) wrote :

Looks great!

review: Approve
Revision history for this message
Eric Day (eday) wrote :

lgtm!

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/source/adminguide/managing.networks.rst'
2--- doc/source/adminguide/managing.networks.rst 2010-11-22 22:43:17 +0000
3+++ doc/source/adminguide/managing.networks.rst 2010-12-10 22:07:11 +0000
4@@ -23,7 +23,7 @@
5 Nova Network Strategies
6 -----------------------
7
8-Currently, Nova supports three kinds of networks, implemented in three "Network Manager" types respectively: Flat Network Manager, Flat DHCP Network Manager, and VLAN Network Manager. The three kinds of networks can c-exist in a cloud system. However, the scheduler for selecting the type of network for a given project is not yet implemented. Here is a brief description of each of the different network strategies, with a focus on the VLAN Manager in a separate section.
9+Currently, Nova supports three kinds of networks, implemented in three "Network Manager" types respectively: Flat Network Manager, Flat DHCP Network Manager, and VLAN Network Manager. The three kinds of networks can co-exist in a cloud system. However, the scheduler for selecting the type of network for a given project is not yet implemented. Here is a brief description of each of the different network strategies, with a focus on the VLAN Manager in a separate section.
10
11 Read more about Nova network strategies here:
12
13
14=== modified file 'doc/source/adminguide/multi.node.install.rst'
15--- doc/source/adminguide/multi.node.install.rst 2010-12-02 19:48:39 +0000
16+++ doc/source/adminguide/multi.node.install.rst 2010-12-10 22:07:11 +0000
17@@ -35,7 +35,6 @@
18 * For a recommended HA setup, consider a MySQL master/slave replication, with as many slaves as you like, and probably a heartbeat to kick one of the slaves into being a master if it dies.
19 * For performance optimization, split reads and writes to the database. MySQL proxy is the easiest way to make this work if running MySQL.
20
21-
22 Assumptions
23 ^^^^^^^^^^^
24
25@@ -69,14 +68,14 @@
26
27 It is highly likely that there will be errors when the nova services come up since they are not yet configured. Don't worry, you're only at step 1!
28
29-Step 2 Setup configuration files (installed in /etc/nova)
30+Step 2 Setup configuration file (installed in /etc/nova)
31 ---------------------------------------------------------
32
33 Note: CC_ADDR=<the external IP address of your cloud controller>
34
35-1. These need to be defined in EACH configuration file
36+Nova development has consolidated all .conf files to nova.conf as of November 2010. References to specific .conf files may be ignored.
37
38-::
39+#. These need to be defined in the nova.conf configuration file::
40
41 --sql_connection=mysql://root:nova@$CC_ADDR/nova # location of nova sql db
42 --s3_host=$CC_ADDR # This is where nova is hosting the objectstore service, which
43@@ -87,31 +86,14 @@
44 --ec2_url=http://$CC_ADDR:8773/services/Cloud
45 --network_manager=nova.network.manager.FlatManager # simple, no-vlan networking type
46
47-
48-2. nova-manage specific flags
49-
50-::
51-
52- --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
53- --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
54-
55-
56-3. nova-network specific flags
57-
58-::
59-
60- --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
61- --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
62-
63-4. Create a nova group
64-
65-::
66+ --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
67+ --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
68+
69+#. Create a nova group::
70
71 sudo addgroup nova
72
73-5. nova-objectstore specific flags < no specific config needed >
74-
75-Config files should be have their owner set to root:nova, and mode set to 0640, since they contain your MySQL server's root password.
76+The Nova config file should have its owner set to root:nova, and mode set to 0640, since they contain your MySQL server's root password.
77
78 ::
79
80@@ -121,7 +103,7 @@
81 Step 3 Setup the sql db
82 -----------------------
83
84-1. First you 'preseed' (using vishy's :doc:`../quickstart`). Run this as root.
85+1. First you 'preseed' (using the Quick Start method :doc:`../quickstart`). Run this as root.
86
87 ::
88
89
90=== modified file 'doc/source/adminguide/single.node.install.rst'
91--- doc/source/adminguide/single.node.install.rst 2010-12-02 19:48:39 +0000
92+++ doc/source/adminguide/single.node.install.rst 2010-12-10 22:07:11 +0000
93@@ -9,7 +9,7 @@
94 Step 1 and 2: Get the latest Nova code system software
95 ------------------------------------------------------
96
97-Depending on your system, the mehod for accomplishing this varies
98+Depending on your system, the method for accomplishing this varies
99
100 .. toctree::
101 :maxdepth: 1
102@@ -139,7 +139,7 @@
103
104 Step 9: Pat yourself on the back :)
105 -----------------------------------
106-Congratulations, your cloud is up and running, you’ve created an admin user, retrieved the user's credentials and put them in your environment.
107+Congratulations, your cloud is up and running, you’ve created an admin user, created a network, retrieved the user's credentials and put them in your environment.
108
109 Now you need an image.
110
111
112=== modified file 'doc/source/cloud101.rst'
113--- doc/source/cloud101.rst 2010-11-11 22:32:24 +0000
114+++ doc/source/cloud101.rst 2010-12-10 22:07:11 +0000
115@@ -54,6 +54,8 @@
116 The US-based National Institute of Standards and Technology offers definitions for cloud computing
117 and the service models that are emerging.
118
119+These definitions are summarized from http://csrc.nist.gov/groups/SNS/cloud-computing/.
120+
121 SaaS - Software as a Service
122 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
123
124@@ -72,12 +74,15 @@
125 Provides infrastructure such as computer instances, network connections, and storage so that people
126 can run any software or operating system.
127
128-.. todo:: Use definitions from http://csrc.nist.gov/groups/SNS/cloud-computing/ and attribute NIST
129
130 Types of Cloud Deployments
131 --------------------------
132-.. todo:: describe public/private/hybrid/etc
133-
134+
135+When you hear terms such as public cloud or private cloud, these refer to the deployment model for the cloud. A private cloud operates for a single organization, but can be managed on-premise or off-premise. A public cloud has an infrastructure that is available to the general public or a large industry group and is likely owned by a cloud services company.
136+
137+The NIST also defines community cloud as shared by several organizations supporting a specific community with shared concerns.
138+
139+A hybrid cloud can be a deployment model, as a composition of both public and private clouds, or a hybrid model for cloud computing may involve both virtual and physical servers.
140
141 Work in the Clouds
142 ------------------
143
144=== added file 'doc/source/images/novascreens.png'
145Binary files doc/source/images/novascreens.png 1970-01-01 00:00:00 +0000 and doc/source/images/novascreens.png 2010-12-10 22:07:11 +0000 differ
146=== added file 'doc/source/images/novashvirtually.png'
147Binary files doc/source/images/novashvirtually.png 1970-01-01 00:00:00 +0000 and doc/source/images/novashvirtually.png 2010-12-10 22:07:11 +0000 differ
148=== modified file 'doc/source/index.rst'
149--- doc/source/index.rst 2010-11-11 19:43:32 +0000
150+++ doc/source/index.rst 2010-12-10 22:07:11 +0000
151@@ -26,7 +26,7 @@
152
153 * **Component based architecture**: Quickly add new behaviors
154 * **Highly available**: Scale to very serious workloads
155-* **Fault-Tollerant**: Isloated processes avoid cascading failures
156+* **Fault-Tolerant**: Isolated processes avoid cascading failures
157 * **Recoverable**: Failures should be easy to diagnose, debug, and rectify
158 * **Open Standards**: Be a reference implementation for a community-driven api
159 * **API Compatibility**: Nova strives to provide API-compatible with popular systems like Amazon EC2
160@@ -62,8 +62,6 @@
161 adminguide/single.node.install
162 adminguide/multi.node.install
163
164-.. todo:: add swiftadmin
165-
166 Developer Docs
167 ==============
168
169
170=== modified file 'doc/source/livecd.rst'
171--- doc/source/livecd.rst 2010-11-11 19:07:47 +0000
172+++ doc/source/livecd.rst 2010-12-10 22:07:11 +0000
173@@ -1,2 +1,48 @@
174 Installing the Live CD
175 ======================
176+
177+If you'd like to set up a sandbox installation of Nova, you can use one of these Live CD images.
178+
179+If you don't already have VirtualBox installed, you can download it from http://www.virtualbox.org/wiki/Downloads.
180+
181+Download the zip or iso file and then follow these steps to try Nova in a virtual environment.
182+
183+http://c0047913.cdn1.cloudfiles.rackspacecloud.com/OpenStackNova.x86_64-2010.1.2.iso (OpenSUSE image; root password is "linux" for this image)
184+
185+http://c0028699.cdn1.cloudfiles.rackspacecloud.com/nova-vm.zip (~900 MB) (log in information is nova/nova)
186+
187+Once a VM is configured and started, here are the basics:
188+
189+ #. Login to Ubuntu using ID nova and Password nova.
190+
191+ #. Switch to running as sudo (enter nova when prompted for the password)::
192+
193+ sudo -s
194+
195+ #. To run Nova for the first time, enter::
196+
197+ cd /var/openstack/
198+
199+ #. Now that you're in the correct directory, enter::
200+
201+ ./nova.sh run
202+
203+ .. image:: images/novashvirtually.png
204+
205+If it's already running, use screen -ls, and when the nova screen is presented,then enter screen -d -r nova.
206+
207+These are the steps to get an instance running (the image is already provided in this environment). Enter these commands in the "test" screen.
208+
209+::
210+
211+ euca-add-keypair test > test.pem
212+ chmod 600 test.pem
213+ euca-run-instances -k test -t m1.tiny ami-tiny
214+ euca-describe-instances
215+
216+ ssh -i test.pem root@10.0.0.3
217+
218+To see output from the various workers, switch screen windows with Ctrl+A " (quotation mark).
219+
220+ .. image:: images/novascreens.png
221+