Configuring keystone -------------------- No database has been set up for Keystone to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Keystone will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow keystone". Set up a database for Keystone? yes Configuring keystone -------------------- No database has been set up for Keystone to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Keystone will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow keystone". Set up a database for Keystone? yes The keystone package must have a database installed and configured before it can be used. This can be optionally handled with dbconfig-common. If you are an advanced database administrator and know that you want to perform this configuration manually, or if your database has already been installed and configured, you should refuse this option. Details on what needs to be done should most likely be provided in /usr/share/doc/keystone. Otherwise, you should probably choose this option. Configure database for keystone with dbconfig-common? yes The keystone package can be configured to use one of several database types. Below, you will be presented with the available choices. 1. sqlite3 2. mysql 3. pgsql Database type to be used by keystone: 2 By default, keystone will be configured to use a MySQL server through a local unix socket (this provides the best performance). However, if you would like to connect with a different method, or to a different server entirely, select an option from the choices below. 1. unix socket 2. tcp/ip Connection method for MySQL database of keystone: 1 Please provide the password for the administrative account with which this package should create its MySQL database and user. Password of the database's administrative user: Starting OpenStack Identity service : keystone. Sleeping 5 seconds to make sure the keystone daemon is up and running: 5...4...3...2...1...0 Upgrading db... Creating tenants... Registering keystone endpoint...done! Configuring cinder-common ------------------------- No database has been set up for Cinder to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Cinder will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow cinder-common". Set up a database for Cinder? yes Configuring cinder-api ---------------------- Each Openstack services (each API) should be registered in order to be accessible. This is done using "keystone service-create" and "keystone endpoint-create". Select if you want to run these commands now. Note that you will need to have an up and running keystone server on which to connect using the Keystone auth token. Register Cinder in the keystone endpoint catalog? yes To configure its endpoint in Keystone, cinder-api needs the Keystone auth token. Keystone Auth Token: ADMIN Configuring glance-common ------------------------- No database has been set up for glance-registry or glance-api to use. Before continuing, you should make sure you have: - the server host name (that server must allow TCP connections from this machine); - a username and password to access the database. - A database type that you want to use. If some of these requirements are missing, reject this option and run with regular sqlite support. You can change this setting later on by running 'dpkg-reconfigure -plow glance-common'. Set up a database for glance? yes Configuring glance-api ---------------------- Each Openstack services (each API) should be registered in order to be accessible. This is done using "keystone service-create" and "keystone endpoint-create". Select if you want to run these commands now. Note that you will need to have an up and running keystone server on which to connect using the Keystone auth token. Register Glance in the keystone endpoint catalog? yes To configure its endpoint in Keystone, glance-api needs the Keystone auth token. Keystone Auth Token: ADMIN Configuring nova-common ----------------------- No database has been set up for Nova to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Nova will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow nova-common". Set up a database for Nova? yes Configuring nova-api -------------------- Each Openstack services (each API) should be registered in order to be accessible. This is done using "keystone service-create" and "keystone endpoint-create". Select if you want to run these commands now. Note that you will need to have an up and running keystone server on which to connect using the Keystone auth token. Register Nova in the keystone endpoint catalog? yes To configure its endpoint in Keystone, nova-api needs the Keystone auth token. Keystone Auth Token: ADMIN Configuring openstack-dashboard-apache -------------------------------------- In Debian, Apache comes with a default website and a default page, configured in /etc/apache2/sites-available/default. Select if this configuration should be disabled and replaced by the Openstack Dashboard configuration. Activate Dashboard and disable default VirtualHost? yes Please choose if you would like Horizon to be installed on HTTPS only, with a redirection to HTTPS if HTTP is in use. Should the Dashboard be installed on HTTPS? yes Configuring libguestfs0 ----------------------- A "supermin appliance" is mandatory for libguestfs. It contains lists of files and directories. These will be copied into an ad-hoc file system whenever libguestfs starts a virtual machine. To generate or update a supermin appliance, network access to a package repository is needed. This can be done later by using the update-guestfs-appliance(8) utility. Create or update supermin appliance now? no Configuring cinder-common ------------------------- No database has been set up for Cinder to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Cinder will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow cinder-common". Set up a database for Cinder? yes If you are an advanced database administrator and know that you want to perform this configuration manually, or if your database has already been installed and configured, you should refuse this option. Details on what needs to be done should most likely be provided in /usr/share/doc/cinder-common. Otherwise, you should probably choose this option. Configure database for cinder-common with dbconfig-common? yes The cinder-common package can be configured to use one of several database types. Below, you will be presented with the available choices. 1. sqlite3 2. mysql 3. pgsql Database type to be used by cinder-common: 2 By default, cinder-common will be configured to use a MySQL server through a local unix socket (this provides the best performance). However, if you would like to connect with a different method, or to a different server entirely, select an option from the choices below. 1. unix socket 2. tcp/ip Connection method for MySQL database of cinder-common: 1 Please provide the password for the administrative account with which this package should create its MySQL database and user. Password of the database's administrative user: Please provide a password for cinder-common to register with the database server. If left blank, a random password will be generated. MySQL application password for cinder-common: Please specify the URL of your Cinder authentication server. Typically this is also the URL of your OpenStack Identity Service (Keystone). Auth server hostname: 192.168.42.1 Auth server password: ADMIN Please choose whether you want to start Cinder services when the machine is booted up. Start cinder services at boot? yes Cinder volume group: volumes Configuring glance-common ------------------------- No database has been set up for glance-registry or glance-api to use. Before continuing, you should make sure you have: - the server host name (that server must allow TCP connections from this machine); - a username and password to access the database. - A database type that you want to use. If some of these requirements are missing, reject this option and run with regular sqlite support. You can change this setting later on by running 'dpkg-reconfigure -plow glance-common'. Set up a database for glance? yes If you are an advanced database administrator and know that you want to perform this configuration manually, or if your database has already been installed and configured, you should refuse this option. Details on what needs to be done should most likely be provided in /usr/share/doc/glance-common. Otherwise, you should probably choose this option. Configure database for glance-common with dbconfig-common? yes The glance-common package can be configured to use one of several database types. Below, you will be presented with the available choices. 1. sqlite3 2. mysql 3. pgsql Database type to be used by glance-common: 2 By default, glance-common will be configured to use a MySQL server through a local unix socket (this provides the best performance). However, if you would like to connect with a different method, or to a different server entirely, select an option from the choices below. 1. unix socket 2. tcp/ip Connection method for MySQL database of glance-common: 1 Please provide the password for the administrative account with which this package should create its MySQL database and user. Password of the database's administrative user: Please provide a password for glance-common to register with the database server. If left blank, a random password will be generated. MySQL application password for glance-common: Please specify the flavor of pipeline to be used by Glance. If you use the OpenStack Identity Service (Keystone), you might want to select "keystone". If you don't use this service, you can safely choose "caching" only. 1. keystone 2. caching 3. keystone+caching 4. cachemanagement 5. keystone+cachemanagement Pipeline flavor: 1 Please specify the URL of your Glance authentication server. Typically this is also the URL of your OpenStack Identity Service (Keystone). Auth server hostname: 192.168.42.1 Auth server password: ADMIN Configuring nova-common ----------------------- No database has been set up for Nova to use. If you want to set one up now, please make sure you have all needed information: * the host name of the database server (which must allow TCP connections from this machine); * a username and password to access the database; * the type of database management software you want to use. If you don't choose this option, no database will be set up and Nova will use regular SQLite support. You can change this setting later on by running "dpkg-reconfigure -plow nova-common". Set up a database for Nova? yes The nova-common package must have a database installed and configured before it can be used. This can be optionally handled with dbconfig-common. If you are an advanced database administrator and know that you want to perform this configuration manually, or if your database has already been installed and configured, you should refuse this option. Details on what needs to be done should most likely be provided in /usr/share/doc/nova-common. Otherwise, you should probably choose this option. Configure database for nova-common with dbconfig-common? yes The nova-common package can be configured to use one of several database types. Below, you will be presented with the available choices. 1. sqlite3 2. mysql 3. pgsql Database type to be used by nova-common: 2 By default, nova-common will be configured to use a MySQL server through a local unix socket (this provides the best performance). However, if you would like to connect with a different method, or to a different server entirely, select an option from the choices below. 1. unix socket 2. tcp/ip Connection method for MySQL database of nova-common: 1 Please provide the password for the administrative account with which this package should create its MySQL database and user. Password of the database's administrative user: Please provide a password for nova-common to register with the database server. If left blank, a random password will be generated. MySQL application password for nova-common: Please specify the URL of your Nova authentication server. Typically this is also the URL of your OpenStack Identity Service (Keystone). Auth server hostname: 192.168.42.1 Auth server password: ADMIN Please choose whether you want to start Nova services when the machine is booted up. Start nova services at boot? yes Openstack Nova supports different API services, each of them binding on a different port. Select which one nova-api should support. If it is a compute node that you are setting-up, then you only need to run the metadata API server. If you run Cinder, then you don't need osapi_volume (you cannot run osapi_volume and cinder-api on the same server: they bind on the same port). 1. ec2 2. osapi_compute 3. metadata 4. osapi_volume (Enter the items you want to select, separated by spaces.) API to activate: 1 2 3 Openstack Nova supports different networking models. Select which one you wish to use. 1. FlatDHCPManager 2. FlatManager 3. FloatingIP 4. VlanManager 5. RPCAllocateFixedIP Nova network manager type: 4 Enter the IP address that will be set in the my_ip directive of nova.conf. Value for my_ip: 192.168.42.1