diff --git a/docs/source/configuration.html b/docs/source/configuration.html index fbcead7ab4..044bafc70d 100644 --- a/docs/source/configuration.html +++ b/docs/source/configuration.html @@ -146,7 +146,7 @@ SERVICE_TOKEN=a682f596-76f3-11e3-b3b2-e716f9080d50
One syslog to bind them all
Default: SYSLOG=False SYSLOG_HOST=$HOST_IP SYSLOG_PORT=516
- Logging all services to a single syslog can be convenient. Enable syslogging by seting SYSLOG to True. If the destination log host is not localhost SYSLOG_HOST and SYSLOG_PORT can be used to direct the message stream to the log host. + Logging all services to a single syslog can be convenient. Enable syslogging by setting SYSLOG to True. If the destination log host is not localhost SYSLOG_HOST and SYSLOG_PORT can be used to direct the message stream to the log host. 
SYSLOG=True
 SYSLOG_HOST=$HOST_IP
 SYSLOG_PORT=516
diff --git a/docs/source/guides/multinode-lab.html b/docs/source/guides/multinode-lab.html index a286954e7d..db8be08e87 100644 --- a/docs/source/guides/multinode-lab.html +++ b/docs/source/guides/multinode-lab.html @@ -114,11 +114,11 @@ GATEWAY=192.168.42.1

OpenStack runs as a non-root user that has sudo access to root. There is nothing special about the name, we'll use stack here. Every node must use the same name and preferably uid. If you created a user during the OS install you can use it and give it - sudo priviledges below. Otherwise create the stack user:

+ sudo privileges below. Otherwise create the stack user:

groupadd stack
 useradd -g stack -s /bin/bash -d /opt/stack -m stack

This user will be making many changes to your system during installation and operation - so it needs to have sudo priviledges to root without a password:

+ so it needs to have sudo privileges to root without a password:

echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers

From here on use the stack user. Logout and login as the stack user.

@@ -221,7 +221,7 @@ sudo virsh list | grep inst | awk '{print $1}' | xargs -n1 virsh destroy

Additional Users

-

DevStack creates two OpenStack users (admin and demo) and two tenants (also admin and demo). admin is exactly what it sounds like, a priveleged administrative account that is a member of both the admin and demo tenants. demo is a normal user account that is only a member of the demo tenant. Creating additional OpenStack users can be done through the dashboard, sometimes it is easier to do them in bulk from a script, especially since they get blown away every time +

DevStack creates two OpenStack users (admin and demo) and two tenants (also admin and demo). admin is exactly what it sounds like, a privileged administrative account that is a member of both the admin and demo tenants. demo is a normal user account that is only a member of the demo tenant. Creating additional OpenStack users can be done through the dashboard, sometimes it is easier to do them in bulk from a script, especially since they get blown away every time stack.sh runs. The following steps are ripe for scripting:

# Get admin creds
 . openrc admin admin
@@ -275,7 +275,7 @@ keystone user-role-add --user-id=<bob-user-id> --tenant-id=<bob-tenant-
 vgcreate stack-volumes /dev/sdc

Syslog

-

DevStack is capable of using rsyslog to agregate logging across the cluster. +

DevStack is capable of using rsyslog to aggregate logging across the cluster. It is off by default; to turn it on set SYSLOG=True in local.conf. SYSLOG_HOST defaults to HOST_IP; on the compute nodes it must be set to the IP of the cluster controller to send syslog output there. In the example diff --git a/docs/source/guides/single-machine.html b/docs/source/guides/single-machine.html index ca9cafac4e..9471972382 100644 --- a/docs/source/guides/single-machine.html +++ b/docs/source/guides/single-machine.html @@ -69,9 +69,9 @@

Add your user

-

We need to add a user to install DevStack. (if you created a user during install you can skip this step and just give the user sudo priviledges below)

+

We need to add a user to install DevStack. (if you created a user during install you can skip this step and just give the user sudo privileges below)

adduser stack
-

Since this user will be making many changes to your system, it will need to have sudo priviledges:

+

Since this user will be making many changes to your system, it will need to have sudo privileges:

apt-get install sudo -y || yum install -y sudo
 echo "stack ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers

From here on you should use the user you created. Logout and login as that user.

@@ -113,7 +113,7 @@ SERVICE_PASSWORD=iheartksl

Using OpenStack

At this point you should be able to access the dashboard from other computers on the local network. In this example that would be http://192.168.1.201/ for the dashboard (aka Horizon). - Launch VMs and if you give them floating IPs and security group access those VMs will be accessable from other machines on your network.

+ Launch VMs and if you give them floating IPs and security group access those VMs will be accessible from other machines on your network.

Some examples of using the OpenStack command-line clients nova and glance are in the shakedown scripts in devstack/exercises. exercise.sh diff --git a/docs/source/openrc.html b/docs/source/openrc.html index b84d26839b..da6697fb92 100644 --- a/docs/source/openrc.html +++ b/docs/source/openrc.html @@ -60,7 +60,7 @@

The introduction of Keystone to the OpenStack ecosystem has standardized the term tenant as the entity that owns resources. In some places references still exist to the original Nova term project for this use. Also, - tenant_name is prefered to tenant_id. + tenant_name is preferred to tenant_id. 
OS_TENANT_NAME=demo
OS_USERNAME
diff --git a/tools/build_docs.sh b/tools/build_docs.sh index e999eff751..96bd8924d6 100755 --- a/tools/build_docs.sh +++ b/tools/build_docs.sh @@ -17,7 +17,7 @@ ## prevent stray files in the workspace being added tot he docs) ## -o Write the static HTML output to ## (Note that will be deleted and re-created to ensure it is clean) -## -g Update the old gh-pages repo (set PUSH=1 to actualy push up to RCB) +## -g Update the old gh-pages repo (set PUSH=1 to actually push up to RCB) # Defaults # -------- diff --git a/tools/xen/install_os_domU.sh b/tools/xen/install_os_domU.sh index 9bf8f73c92..75d56a8465 100755 --- a/tools/xen/install_os_domU.sh +++ b/tools/xen/install_os_domU.sh @@ -394,7 +394,7 @@ if [ "$WAIT_TILL_LAUNCH" = "1" ] && [ -e ~/.ssh/id_rsa.pub ] && [ "$COPYENV" = # Watch devstack's output (which doesn't start until stack.sh is running, # but wait for run.sh (which starts stack.sh) to exit as that is what - # hopefully writes the succeded cookie. + # hopefully writes the succeeded cookie. pid=`ssh_no_check -q stack@$OS_VM_MANAGEMENT_ADDRESS pgrep run.sh` ssh_no_check -q stack@$OS_VM_MANAGEMENT_ADDRESS "tail --pid $pid -n +1 -f /tmp/devstack/log/stack.log"