summaryrefslogtreecommitdiffstats
path: root/doc/source
diff options
context:
space:
mode:
authorAnne Gentle <anne@openstack.org>2010-12-02 13:48:39 -0600
committerAnne Gentle <anne@openstack.org>2010-12-02 13:48:39 -0600
commita8df0a7d6c2de55d7906fa311f79887ccf575508 (patch)
tree6466546bb5999b8f24b5fe4b59f07c2227b6b6a5 /doc/source
parent15663b4d4686a6c42810e86940d5b7e27b207d26 (diff)
downloadnova-a8df0a7d6c2de55d7906fa311f79887ccf575508.tar.gz
nova-a8df0a7d6c2de55d7906fa311f79887ccf575508.tar.xz
nova-a8df0a7d6c2de55d7906fa311f79887ccf575508.zip
Fixing single node install doc
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/adminguide/multi.node.install.rst13
-rw-r--r--doc/source/adminguide/single.node.install.rst20
2 files changed, 21 insertions, 12 deletions
diff --git a/doc/source/adminguide/multi.node.install.rst b/doc/source/adminguide/multi.node.install.rst
index dcceb539b..1eed30c5b 100644
--- a/doc/source/adminguide/multi.node.install.rst
+++ b/doc/source/adminguide/multi.node.install.rst
@@ -19,7 +19,7 @@ Installing Nova on Multiple Servers
===================================
When you move beyond evaluating the technology and into building an actual
-production environemnt, you will need to know how to configure your datacenter
+production environment, you will need to know how to configure your datacenter
and how to deploy components across your clusters. This guide should help you
through that process.
@@ -161,7 +161,7 @@ Step 3 Setup the sql db
GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' WITH GRANT OPTION;
SET PASSWORD FOR 'root'@'%' = PASSWORD('nova');
-7. branch and install Nova
+7. Branch and install Nova
::
@@ -186,9 +186,7 @@ Step 4 Setup Nova environment
Note: The nova-manage service assumes that the first IP address is your network (like 192.168.0.0), that the 2nd IP is your gateway (192.168.0.1), and that the broadcast is the very last IP in the range you defined (192.168.0.255). If this is not the case you will need to manually edit the sql db 'networks' table.o.
-On running this command, entries are made in the 'networks' and 'fixed_ips' table. However, one of the networks listed in the 'networks' table needs to be marked as bridge in order for the code to know that a bridge exists. We ended up doing this manually, (update query fired directly in the DB). Is there a better way to mark a network as bridged?
-
-Update: This has been resolved w.e.f 27/10. network is marked as bridged automatically based on the type of n/w manager selected.
+On running this command, entries are made in the 'networks' and 'fixed_ips' table. However, one of the networks listed in the 'networks' table needs to be marked as bridge in order for the code to know that a bridge exists. The Network is marked as bridged automatically based on the type of network manager selected.
More networking details to create a network bridge for flat network
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -233,7 +231,6 @@ unzip them in your home directory, and add them to your environment::
echo ". creds/novarc" >> ~/.bashrc
~/.bashrc
-
Step 6 Restart all relevant services
------------------------------------
@@ -249,8 +246,8 @@ Restart relevant nova services::
.. todo:: do we still need the content below?
-Bare-metal Provisioning
------------------------
+Bare-metal Provisioning Notes
+-----------------------------
To install the base operating system you can use PXE booting.
diff --git a/doc/source/adminguide/single.node.install.rst b/doc/source/adminguide/single.node.install.rst
index 27597962a..f6b2290bc 100644
--- a/doc/source/adminguide/single.node.install.rst
+++ b/doc/source/adminguide/single.node.install.rst
@@ -63,8 +63,20 @@ You see an access key and a secret key export, such as these made-up ones:::
export EC2_ACCESS_KEY=4e6498a2-blah-blah-blah-17d1333t97fd
export EC2_SECRET_KEY=0a520304-blah-blah-blah-340sp34k05bbe9a7
+Step 5: Create the network
+--------------------------
+
+Type or copy/paste in the following line to create a network prior to creating a project.
+
+::
+
+ sudo nova-manage network create 10.0.0.0/8 1 64
+
+For this command, the IP address is the cidr notation for your netmask, such as 192.168.1.0/24. The value 1 is the total number of networks you want made, and the 64 value is the total number of ips in all networks.
+
+After running this command, entries are made in the 'networks' and 'fixed_ips' table in the database.
-Step 5: Create a project with the user you created
+Step 6: Create a project with the user you created
--------------------------------------------------
Type or copy/paste in the following line to create a project named IRT (for Ice Road Truckers, of course) with the newly-created user named anne.
@@ -94,7 +106,7 @@ Type or copy/paste in the following line to create a project named IRT (for Ice
Data Base Updated
-Step 6: Unzip the nova.zip
+Step 7: Unzip the nova.zip
--------------------------
You should have a nova.zip file in your current working directory. Unzip it with this command:
@@ -116,7 +128,7 @@ You'll see these files extract.
extracting: cacert.pem
-Step 7: Source the rc file
+Step 8: Source the rc file
--------------------------
Type or copy/paste the following to source the novarc file in your current working directory.
@@ -125,7 +137,7 @@ Type or copy/paste the following to source the novarc file in your current worki
. novarc
-Step 8: Pat yourself on the back :)
+Step 9: Pat yourself on the back :)
-----------------------------------
Congratulations, your cloud is up and running, you’ve created an admin user, retrieved the user's credentials and put them in your environment.