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
=== modified file 'doc/source/adminguide/managing.networks.rst'
--- doc/source/adminguide/managing.networks.rst 2010-11-22 22:43:17 +0000
+++ doc/source/adminguide/managing.networks.rst 2010-12-10 22:07:11 +0000
@@ -23,7 +23,7 @@
23Nova Network Strategies23Nova Network Strategies
24-----------------------24-----------------------
2525
26Currently, 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. 26Currently, 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.
2727
28Read more about Nova network strategies here:28Read more about Nova network strategies here:
2929
3030
=== 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-10 22:07:11 +0000
@@ -35,7 +35,6 @@
35* 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.35* 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.
36* For performance optimization, split reads and writes to the database. MySQL proxy is the easiest way to make this work if running MySQL.36* For performance optimization, split reads and writes to the database. MySQL proxy is the easiest way to make this work if running MySQL.
3737
38
39Assumptions38Assumptions
40^^^^^^^^^^^39^^^^^^^^^^^
4140
@@ -69,14 +68,14 @@
6968
70It 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!69It 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!
7170
72Step 2 Setup configuration files (installed in /etc/nova)71Step 2 Setup configuration file (installed in /etc/nova)
73---------------------------------------------------------72---------------------------------------------------------
7473
75Note: CC_ADDR=<the external IP address of your cloud controller>74Note: CC_ADDR=<the external IP address of your cloud controller>
7675
771. These need to be defined in EACH configuration file76Nova development has consolidated all .conf files to nova.conf as of November 2010. References to specific .conf files may be ignored.
7877
79::78#. These need to be defined in the nova.conf configuration file::
8079
81 --sql_connection=mysql://root:nova@$CC_ADDR/nova # location of nova sql db80 --sql_connection=mysql://root:nova@$CC_ADDR/nova # location of nova sql db
82 --s3_host=$CC_ADDR # This is where nova is hosting the objectstore service, which81 --s3_host=$CC_ADDR # This is where nova is hosting the objectstore service, which
@@ -87,31 +86,14 @@
87 --ec2_url=http://$CC_ADDR:8773/services/Cloud86 --ec2_url=http://$CC_ADDR:8773/services/Cloud
88 --network_manager=nova.network.manager.FlatManager # simple, no-vlan networking type87 --network_manager=nova.network.manager.FlatManager # simple, no-vlan networking type
8988
9089 --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
912. nova-manage specific flags90 --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
9291
93::92#. Create a nova group::
94
95 --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
96 --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
97
98
993. nova-network specific flags
100
101::
102
103 --fixed_range=<network/prefix> # ip network to use for VM guests, ex 192.168.2.64/26
104 --network_size=<# of addrs> # number of ip addrs to use for VM guests, ex 64
105
1064. Create a nova group
107
108::
10993
110 sudo addgroup nova94 sudo addgroup nova
11195
1125. nova-objectstore specific flags < no specific config needed >96The 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.
113
114Config files should be have their owner set to root:nova, and mode set to 0640, since they contain your MySQL server's root password.
11597
116::98::
11799
@@ -121,7 +103,7 @@
121Step 3 Setup the sql db103Step 3 Setup the sql db
122-----------------------104-----------------------
123105
1241. First you 'preseed' (using vishy's :doc:`../quickstart`). Run this as root.1061. First you 'preseed' (using the Quick Start method :doc:`../quickstart`). Run this as root.
125107
126::108::
127109
128110
=== modified file 'doc/source/adminguide/single.node.install.rst'
--- doc/source/adminguide/single.node.install.rst 2010-12-02 19:48:39 +0000
+++ doc/source/adminguide/single.node.install.rst 2010-12-10 22:07:11 +0000
@@ -9,7 +9,7 @@
9Step 1 and 2: Get the latest Nova code system software9Step 1 and 2: Get the latest Nova code system software
10------------------------------------------------------10------------------------------------------------------
1111
12Depending on your system, the mehod for accomplishing this varies12Depending on your system, the method for accomplishing this varies
1313
14.. toctree::14.. toctree::
15 :maxdepth: 115 :maxdepth: 1
@@ -139,7 +139,7 @@
139139
140Step 9: Pat yourself on the back :)140Step 9: Pat yourself on the back :)
141-----------------------------------141-----------------------------------
142Congratulations, your cloud is up and running, you’ve created an admin user, retrieved the user's credentials and put them in your environment.142Congratulations, 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.
143143
144Now you need an image.144Now you need an image.
145145
146146
=== modified file 'doc/source/cloud101.rst'
--- doc/source/cloud101.rst 2010-11-11 22:32:24 +0000
+++ doc/source/cloud101.rst 2010-12-10 22:07:11 +0000
@@ -54,6 +54,8 @@
54The US-based National Institute of Standards and Technology offers definitions for cloud computing54The US-based National Institute of Standards and Technology offers definitions for cloud computing
55and the service models that are emerging. 55and the service models that are emerging.
5656
57These definitions are summarized from http://csrc.nist.gov/groups/SNS/cloud-computing/.
58
57SaaS - Software as a Service59SaaS - Software as a Service
58^^^^^^^^^^^^^^^^^^^^^^^^^^^^60^^^^^^^^^^^^^^^^^^^^^^^^^^^^
5961
@@ -72,12 +74,15 @@
72Provides infrastructure such as computer instances, network connections, and storage so that people 74Provides infrastructure such as computer instances, network connections, and storage so that people
73can run any software or operating system.75can run any software or operating system.
7476
75.. todo:: Use definitions from http://csrc.nist.gov/groups/SNS/cloud-computing/ and attribute NIST
7677
77Types of Cloud Deployments78Types of Cloud Deployments
78--------------------------79--------------------------
79.. todo:: describe public/private/hybrid/etc80
8081When 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.
82
83The NIST also defines community cloud as shared by several organizations supporting a specific community with shared concerns.
84
85A 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.
8186
82Work in the Clouds87Work in the Clouds
83------------------88------------------
8489
=== added file 'doc/source/images/novascreens.png'
85Binary 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 differ90Binary 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
=== added file 'doc/source/images/novashvirtually.png'
86Binary 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 differ91Binary 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
=== modified file 'doc/source/index.rst'
--- doc/source/index.rst 2010-11-11 19:43:32 +0000
+++ doc/source/index.rst 2010-12-10 22:07:11 +0000
@@ -26,7 +26,7 @@
2626
27* **Component based architecture**: Quickly add new behaviors27* **Component based architecture**: Quickly add new behaviors
28* **Highly available**: Scale to very serious workloads28* **Highly available**: Scale to very serious workloads
29* **Fault-Tollerant**: Isloated processes avoid cascading failures29* **Fault-Tolerant**: Isolated processes avoid cascading failures
30* **Recoverable**: Failures should be easy to diagnose, debug, and rectify30* **Recoverable**: Failures should be easy to diagnose, debug, and rectify
31* **Open Standards**: Be a reference implementation for a community-driven api31* **Open Standards**: Be a reference implementation for a community-driven api
32* **API Compatibility**: Nova strives to provide API-compatible with popular systems like Amazon EC232* **API Compatibility**: Nova strives to provide API-compatible with popular systems like Amazon EC2
@@ -62,8 +62,6 @@
62 adminguide/single.node.install62 adminguide/single.node.install
63 adminguide/multi.node.install63 adminguide/multi.node.install
6464
65.. todo:: add swiftadmin
66
67Developer Docs65Developer Docs
68==============66==============
6967
7068
=== modified file 'doc/source/livecd.rst'
--- doc/source/livecd.rst 2010-11-11 19:07:47 +0000
+++ doc/source/livecd.rst 2010-12-10 22:07:11 +0000
@@ -1,2 +1,48 @@
1Installing the Live CD1Installing the Live CD
2======================2======================
3
4If you'd like to set up a sandbox installation of Nova, you can use one of these Live CD images.
5
6If you don't already have VirtualBox installed, you can download it from http://www.virtualbox.org/wiki/Downloads.
7
8Download the zip or iso file and then follow these steps to try Nova in a virtual environment.
9
10http://c0047913.cdn1.cloudfiles.rackspacecloud.com/OpenStackNova.x86_64-2010.1.2.iso (OpenSUSE image; root password is "linux" for this image)
11
12http://c0028699.cdn1.cloudfiles.rackspacecloud.com/nova-vm.zip (~900 MB) (log in information is nova/nova)
13
14Once a VM is configured and started, here are the basics:
15
16 #. Login to Ubuntu using ID nova and Password nova.
17
18 #. Switch to running as sudo (enter nova when prompted for the password)::
19
20 sudo -s
21
22 #. To run Nova for the first time, enter::
23
24 cd /var/openstack/
25
26 #. Now that you're in the correct directory, enter::
27
28 ./nova.sh run
29
30 .. image:: images/novashvirtually.png
31
32If it's already running, use screen -ls, and when the nova screen is presented,then enter screen -d -r nova.
33
34These are the steps to get an instance running (the image is already provided in this environment). Enter these commands in the "test" screen.
35
36::
37
38 euca-add-keypair test > test.pem
39 chmod 600 test.pem
40 euca-run-instances -k test -t m1.tiny ami-tiny
41 euca-describe-instances
42
43 ssh -i test.pem root@10.0.0.3
44
45To see output from the various workers, switch screen windows with Ctrl+A " (quotation mark).
46
47 .. image:: images/novascreens.png
48