diff --git a/doc/common/section_dashboard_sessions.xml b/doc/common/section_dashboard_sessions.xml
index ef16a7e70f..972143f294 100644
--- a/doc/common/section_dashboard_sessions.xml
+++ b/doc/common/section_dashboard_sessions.xml
@@ -43,6 +43,7 @@ CACHES = {
}
+
Key-value stores
You can use applications such as Memcached or Redis for external
caching. These applications offer persistence and shared storage
diff --git a/doc/install-guide/ch_basics.xml b/doc/install-guide/ch_basics.xml
index c8dee4fcc0..1ab795f0c0 100644
--- a/doc/install-guide/ch_basics.xml
+++ b/doc/install-guide/ch_basics.xml
@@ -257,7 +257,11 @@ hwclock -w
and the MySQL Python library.
# apt-get install python-mysqldb mysql-server
# yum install mysql mysql-server MySQL-python
- # zypper install mysql-community-server-client mysql-community-server python-mysql
+ # zypper install mysql-community-server-client mysql-community-server python-mysql
+ When you install the server package, you will
+ be asked to enter a root password for the database. Be sure to choose
+ a strong password and remember it - it will be needed later.
+
On any nodes besides the controller node, just install the MySQL
client and the MySQL Python library. This is all you need to do on any
system not hosting the MySQL database.
@@ -265,9 +269,7 @@ hwclock -w
# yum install mysql MySQL-python
# zypper install mysql-community-server-client python-mysql
- When you install the server package, you will
- be asked to enter a root password for the database. Be sure to choose
- a strong password and remember it - it will be needed later.
+
Start the MySQL database server and set it to start automatically when
the system boots.
@@ -284,7 +286,7 @@ hwclock -w
Messaging Server
- Install the messaging queue server. Typically this is On the controller node, install the messaging queue server. Typically this is RabbitMQQpid but QpidRabbitMQ and ZeroMQ (0MQ) are also
@@ -366,7 +368,7 @@ hwclock -w
- Edit /etc/apt/sources.list.d/cloud-archive.list:
+ Create a new repository sources file /etc/apt/sources.list.d/cloud-archive.list containing:
deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/havana main
diff --git a/doc/install-guide/section_dashboard-install.xml b/doc/install-guide/section_dashboard-install.xml
index 40e00ad7d4..d2d6fbfd4d 100644
--- a/doc/install-guide/section_dashboard-install.xml
+++ b/doc/install-guide/section_dashboard-install.xml
@@ -30,43 +30,52 @@
# apt-get install memcached libapache2-mod-wsgi openstack-dashboard
# yum install memcached python-memcached mod_wsgi openstack-dashboard
# zypper install memcached python-python-memcached apache2-mod_wsgi openstack-dashboard
-
-
- Modify the value of
- CACHES['default']['LOCATION']
- in /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
- to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached.conf.
- Open /etc/openstack-dashboard/local_settings.py
- /etc/openstack-dashboard/local_settings
- and look for this line:
- CACHES = {
- 'default': {
- 'BACKEND' : 'django.core.cache.backends.memcached.MemcachedCache',
- 'LOCATION' : '127.0.0.1:11211'
- }
- }
-
- Notes
-
-
- The address and port must match the ones
- set in /etc/memcached.conf/etc/sysconfig/memcached.
- If you change the memcached settings,
- you must restart the Apache web server for
+
+
+ Remove the
+ openstack-dashboard-ubuntu-theme
+ package. This theme prevents translations, several menus
+ as well as the network map from rendering correctly:
+ # apt-get remove --purge openstack-dashboard-ubuntu-theme
+
+
+
+
+ Modify the value of
+ CACHES['default']['LOCATION']
+ in /etc/openstack-dashboard/local_settings.py/etc/openstack-dashboard/local_settings/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
+ to match the ones set in /etc/memcached.conf/etc/sysconfig/memcached.conf.
+ Open /etc/openstack-dashboard/local_settings.py
+ /etc/openstack-dashboard/local_settings
+ and look for this line:
+ CACHES = {
+'default': {
+'BACKEND' : 'django.core.cache.backends.memcached.MemcachedCache',
+'LOCATION' : '127.0.0.1:11211'
+}
+}
+
+ Notes
+
+
+ The address and port must match the ones
+ set in /etc/memcached.conf/etc/sysconfig/memcached.
+ If you change the memcached settings,
+ you must restart the Apache web server for
the changes to take effect.
@@ -93,6 +102,21 @@
+
+ This guide assumes that you are running the Dashboard on the controller node.
+ You can easily run the dashboard on a separate server, by changing the appropriate settings in
+ local_settings.py
+ Edit /etc/openstack-dashboard/local_settings/etc/openstack-dashboard/local_settings.py/usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
+ and change OPENSTACK_HOST to the hostname of your Identity Service.
+ OPENSTACK_HOST = "controller"
+
+
You can now access the dashboard at http://controller/horizon.
Login with credentials for any user that you created with the OpenStack Identity Service.
diff --git a/doc/install-guide/section_nova-compute.xml b/doc/install-guide/section_nova-compute.xml
index 8ce028a5ed..ff112f23a5 100644
--- a/doc/install-guide/section_nova-compute.xml
+++ b/doc/install-guide/section_nova-compute.xml
@@ -60,11 +60,7 @@
...
[DEFAULT]
...
-auth_strategy=keystone
-auth_host=controller
-admin_user=nova
-admin_tenant_name=service
-admin_password=NOVA_DBPASS
+auth_strategy=keystone
# openstack-config --set /etc/nova/nova.conf \
DEFAULT rpc_backend nova.openstack.common.rpc.impl_qpid
@@ -114,8 +110,10 @@ admin_password=NOVA_DBPASS
Ensure that api_paste_config=/etc/nova/api-paste.ini is set in
/etc/nova/nova.conf.
- Start the Compute service and configure it to start when the system boots.
- # service nova-compute start
+
+ Start the Compute service and configure it to start when the system boots.
+ Restart the Compute service.
+ # service nova-compute restart
# service openstack-nova-compute start
# chkconfig openstack-nova-compute on
# systemctl start openstack-nova-compute
diff --git a/doc/install-guide/section_nova-controller.xml b/doc/install-guide/section_nova-controller.xml
index 0c906d7249..e446637cc6 100644
--- a/doc/install-guide/section_nova-controller.xml
+++ b/doc/install-guide/section_nova-controller.xml
@@ -73,7 +73,7 @@ IDENTIFIED BY 'NOVA_DBPASS';
Set the configuration keys my_ip,
vncserver_listen, and
- vncserver_proxyclient_address to the IP address of the
+ vncserver_proxyclient_address to the internal IP address of the
controller node.
# openstack-config --set /etc/nova/nova.conf DEFAULT my_ip 192.168.0.10
@@ -101,9 +101,8 @@ vncserver_proxyclient_address=192.168.0.10
# keystone user-role-add --user=nova --tenant=service --role=admin
- For the Compute Service to use these credentials, you must add
- them to the nova.conf configuration file.
-
+ For the Compute Service to use these credentials, you must alter the nova.conf configuration file.
+
# openstack-config --set /etc/nova/nova.conf DEFAULT auth_strategy keystone
# openstack-config --set /etc/nova/nova.conf DEFAULT auth_host controller
# openstack-config --set /etc/nova/nova.conf DEFAULT admin_user nova
@@ -115,10 +114,6 @@ vncserver_proxyclient_address=192.168.0.10
[DEFAULT]
...
auth_strategy=keystone
-auth_host=controller
-admin_user=nova
-admin_tenant_name=service
-admin_password=NOVA_DBPASS
@@ -134,8 +129,8 @@ admin_password=NOVA_DBPASS
[filter:authtoken]
paste.filter_factory=keystoneclient.middleware.auth_token:filter_factory
auth_host=controller
-admin_user=nova
admin_tenant_name=service
+admin_user=nova
admin_password=NOVA_DBPASS
Ensure that api_paste_config=/etc/nova/api-paste.ini
@@ -172,8 +167,7 @@ admin_password=NOVA_DBPASS
Configure the Compute Service to use the RabbitMQ
- message broker by setting the following configuration keys. They are found in
- the DEFAULT configuration group of the
+ message broker by setting the following configuration keys. Add them in the DEFAULT configuration group of the
/etc/nova/nova.conf file.
rpc_backend = nova.rpc.impl_kombu
rabbit_host = controller
@@ -186,15 +180,15 @@ rabbit_host = controller
# openstack-config --set /etc/nova/nova.conf DEFAULT rabbit_host controller
- Finally, start the various Nova services and configure them
+ Finally, start the various Nova services and configure them
to start when the system boots.
-
+ Finally, restart the various Nova services.
# service nova-api start
-# service nova-cert start
-# service nova-consoleauth start
-# service nova-scheduler start
-# service nova-conductor start
-# service nova-novncproxy start
+# service nova-cert restart
+# service nova-consoleauth restart
+# service nova-scheduler restart
+# service nova-conductor restart
+# service nova-novncproxy restart
# service openstack-nova-api start
# service openstack-nova-cert start
# service openstack-nova-consoleauth start