Installation guide

d. If you are running Django 1.5 (or later), you must ensure that there is a correctly
configured ALLO WED _HO ST S setting in your l o cal _setti ng s file.
ALLO WED _HO ST S contains a list of host names that can be used to contact your
Dashboard service:
If people will be accessing the Dashboard service using
"http://dashboard.example.com", you would set:
ALLOWED_HOSTS=['dashboard.example.com']
If you are running the Dashboard service on your local system, you can use:
ALLOWED_HOSTS=['localhost']
If people will be using IP addresses instead of, or in addition to, hostnames, an
example might be:
ALLOWED_HOSTS=['dashboard.example.com', '192.168.122.200']
Note
For more information about the ALLO WED _HO ST S setting, see the Django
Documentation.
9. Start all OpenStack services on all nodes; on each host, run:
# o penstack-servi ce start
3.3. Met hod - Upgrade Service-by-Service
This method allows you to upgrade one service at a time. At a high level, you:
1. Ensure you are subscribed to the right Red Hat Enterprise Linux OpenStack Platform 4
channels on all of your hosts (see Section 1.3, “ RHN/CD N Channels” ).
2. Update and test each of the services (Section 3.3.1, “ Upgrade an individual service” )
3. Do a final complete-system upgrade (Section 3.3.2, “ Finalize system upgrade” )
3.3.1. Upgrade an individual service
The following steps provide the generic procedure for upgrading a service; upgrade order and
individual service notes are contained in Table 3.3, “ Service Upgrade Order and Instructions” .
1. Stop the service, using:
# o penstack-servi ce sto p serviceName
For example, to stop all Compute services on a host, use:
# o penstack-servi ce sto p no va
Red Hat Ent erprise Linux O penSt ack Plat form 4 Release Not es
52