diff --git a/doc/common/section_getstart_compute.xml b/doc/common/section_getstart_compute.xml index 6250291a0a..0b11f01dcd 100644 --- a/doc/common/section_getstart_compute.xml +++ b/doc/common/section_getstart_compute.xml @@ -38,8 +38,9 @@ Metadata service in the Cloud Administrator Guide. - Note for Debian users: on Debian system, it is included in the nova-api - package, and can be selected through debconf. + Note for Debian users: on Debian system, it is included in the + nova-api + package, and can be selected through debconf. @@ -141,11 +142,13 @@ daemon. Manages x509 certificates. - Note for Debian users: - A unique package called nova-consoleproxy contains nova-novncproxy, + In Debian, a unique package called + nova-consoleproxy contains nova-novncproxy, nova-spicehtml5proxy, and nova-xvpvncproxy. Selection of which to use is done either by configuring - /etc/default/nova-consoleproxy or through Debconf. + /etc/default/nova-consoleproxy or through + Debconf, or manually, by editing /etc/default/nova-consoleproxy + and stopping / starting the console daemons. Image Management (EC2 scenario) diff --git a/doc/install-guide/section_nova-controller.xml b/doc/install-guide/section_nova-controller.xml index 4de5729f41..1874f44d47 100644 --- a/doc/install-guide/section_nova-controller.xml +++ b/doc/install-guide/section_nova-controller.xml @@ -24,26 +24,27 @@ the OpenStack Compute services that will be run on the controller node in this guide. - # apt-get install nova-novncproxy novnc nova-api \ + # apt-get install nova-novncproxy novnc nova-api \ nova-ajax-console-proxy nova-cert nova-conductor \ nova-consoleauth nova-doc nova-scheduler - Note for Debian users - You can use nova-consoleproxy - instead of nova-novncproxy and novnc. The Debconf system will prompt - the user for setting-up the database, which will be automatically created - and configured with the correct access rights. Then nova-manage db sync - will automatically be called. The system will also prompt you for the - keystone auth token configuration, the RabbitMQ server access, and the - API service and endpoint configuration. You can therefore skip the steps - below. + # apt-get install nova-consoleproxy nova-api \ + nova-cert nova-conductor nova-consoleauth nova-scheduler + # zypper install openstack-nova-api openstack-nova-scheduler \ openstack-nova-cert openstack-nova-conductor openstack-nova-console \ openstack-nova-consoleauth openstack-nova-doc \ openstack-nova-novncproxy python-novaclient - + Answer to the debconf + prompts to configure the Nova Controller Services. This includes configuring the database, + the keystone_autotoken, the RabbitMQ credentials, and registering + nova-api in the Keystone catalogue. + The nova-manage db sync will then be done for you automatically. + + + The Compute Service stores information in a database. This guide uses the MySQL database used by other OpenStack services. Specify the location of the database in the @@ -70,7 +71,7 @@ connection = mysql://nova:NOVA_DBPASS@controller/nova # openstack-db --init --service nova --password NOVA_DBPASS - + Next, we need to create a database user called nova, by logging in as root using the password we set earlier. # mysql -u root -p @@ -80,7 +81,7 @@ IDENTIFIED BY 'NOVA_DBPASS'; mysql> GRANT ALL PRIVILEGES ON nova.* TO 'nova'@'%' \ IDENTIFIED BY 'NOVA_DBPASS'; - + We now create the tables for the nova service. # nova-manage db sync @@ -94,7 +95,13 @@ IDENTIFIED BY 'NOVA_DBPASS'; # openstack-config --set /etc/nova/nova.conf DEFAULT my_ip 192.168.0.10 # openstack-config --set /etc/nova/nova.conf DEFAULT vncserver_listen 192.168.0.10 # openstack-config --set /etc/nova/nova.conf DEFAULT vncserver_proxyclient_address 192.168.0.10 - Edit /etc/nova/nova.conf and add to the [DEFAULT] section. + Edit /etc/nova/nova.conf and add to the [DEFAULT] section. + Under Debian, the my_ip parameter + will be automatically setup by the debconf + system, but you still need to edit /etc/nova/nova.conf for the + vncserver_listen and + vncserver_proxyclient_address, which are located at + the end of the file. ... [DEFAULT] @@ -106,7 +113,7 @@ vncserver_proxyclient_address=192.168.0.10 - + Create a user called nova that the Compute Service can use to authenticate with the Identity Service. Use the service tenant and give the user the @@ -115,7 +122,7 @@ vncserver_proxyclient_address=192.168.0.10 # keystone user-create --name=nova --pass=NOVA_PASS --email=nova@example.com # keystone user-role-add --user=nova --tenant=service --role=admin - + 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 @@ -135,7 +142,7 @@ auth_strategy=keystone - + Add the credentials to the file /etc/nova/api-paste.ini. Open the file in a text editor and locate the section [filter:authtoken]. @@ -152,7 +159,7 @@ admin_password=NOVA_PASS Ensure that api_paste_config=/etc/nova/api-paste.ini is set in /etc/nova/nova.conf. - + You have to register the Compute Service with the Identity Service so that other OpenStack services can locate it. Register the service and @@ -162,7 +169,8 @@ admin_password=NOVA_PASS --description="Nova Compute Service" - Note the id property returned and use it when + + Note the id property returned and use it when creating the endpoint. # keystone endpoint-create \ --service-id=the_service_id_above \ @@ -181,7 +189,7 @@ admin_password=NOVA_PASS - + Configure the Compute Service to use the RabbitMQ message broker by setting the following configuration keys. Add them in the DEFAULT configuration group of the /etc/nova/nova.conf file. @@ -195,11 +203,11 @@ rabbit_host = controller DEFAULT rpc_backend nova.rpc.impl_kombu # openstack-config --set /etc/nova/nova.conf DEFAULT rabbit_host controller - + Finally, start the various Nova services and configure them to start when the system boots. - Finally, restart the various Nova services. - # service nova-api restart + Finally, restart the various Nova services. + # service nova-api restart # service nova-cert restart # service nova-consoleauth restart # service nova-scheduler restart