From 690e3c25742f47fd2a42d6407ffa30bc99288dc0 Mon Sep 17 00:00:00 2001
From: Davanum Srinivas OpenStack runs as a non-root user that has sudo access to root. There is nothing special
about the name, we'll use 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
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:
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.
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
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 @@
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=iheartkslAt 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 @@
OS_TENANT_NAME=demo