OpenStack Architecture - Revision history

Drobbins at 20:56, 17 August 2012

2012-08-17T20:56:08Z

2012-06-07T11:18:14Z

‎Melange

2012-04-17T04:10:29Z

2012-04-16T19:19:04Z

2012-03-02T21:44:05Z

‎SQL Database

2012-03-02T21:42:05Z

‎nova

2012-03-02T21:41:53Z

‎SQL Database

2012-03-02T21:40:43Z

‎SQL Database

2012-03-02T21:20:02Z

‎SQL Database

2012-02-26T21:12:18Z

‎RabbitMQ

← Older revision		Revision as of 20:56, 17 August 2012
Line 1:		Line 1:
−	~~{{fancynote\|OpenStack is currently being integrated into Funtoo Experimental.}}~~
−
	This page exists to document [http://www.openstack.org OpenStack] configuration.		This page exists to document [http://www.openstack.org OpenStack] configuration.

@@ Line 135: / Line 135: @@
 <blockquote>
-Melange is intended to provide network information services for use across OpenStack services. The initial focus will be on IP address management (IPAM) and address discovery (DHCP/dnsmasq) functionality. Melange is intended to be a standalone service with it's own API. However, the initial use case will be to decouple existing IP management and VM address discovery from Nova and support the existing Nova networking caoabilities.
+Melange is intended to provide network information services for use across OpenStack services. The initial focus will be on IP address management (IPAM) and address discovery (DHCP/dnsmasq) functionality. Melange is intended to be a standalone service with it's own API. However, the initial use case will be to decouple existing IP management and VM address discovery from Nova and support the existing Nova networking capabilities.
 </blockquote>

@@ Line 10: / Line 10: @@
 A number of OpenStack services use a SQL back-end for storing various bits of data.
 === nova ===
 <console>
@@ Line 74: / Line 82: @@
 You have now validated that nova is connecting to your MySQL database correctly.
 === glance ===

← Older revision		Revision as of 21:42, 2 March 2012
Line 97:		Line 97:

	More info on glance configuration is available [http://docs.openstack.org/diablo/openstack-compute/install/content/glance-registry-conf-file.html here].		More info on glance configuration is available [http://docs.openstack.org/diablo/openstack-compute/install/content/glance-registry-conf-file.html here].
−
−	~~=== nova ===~~
−
−	Nova, the compute service, has its SQL connection specified in <tt>/etc/nova/nova.conf</tt>, using the <tt>--sql_connection=''connection''</tt> format. Connection string is identical to Glance, in SQLAlchemy format.

	=== keystone ===		=== keystone ===

@@ Line 9: / Line 9: @@
 == SQL Database ==
-A number of OpenStack services use a SQL back-end for storing various bits of data. Devstack (the official deployment script for OpenStack) uses MySQL as its deployment database.
+A number of OpenStack services use a SQL back-end for storing various bits of data.
 <console>

@@ Line 9: / Line 9: @@
 == SQL Database ==
-A number of OpenStack services use a SQL back-end for storing various bits of data. Devstack (the official deployment script for OpenStack) uses MySQL as its deployment database, and creates a database for each service that needs to store data, and grants the root MySQL user full privilieges in the database:
+A number of OpenStack services use a SQL back-end for storing various bits of data. Devstack (the official deployment script for OpenStack) uses MySQL as its deployment database.
-<pre>
+<console>
-sudo mysql -uroot -p$MYSQL_PASSWORD -h127.0.0.1 -e "GRANT ALL PRIVILEGES ON *.* TO '$MYSQL_USER'@'%' identified by '$MYSQL_PASSWORD';"
+mysql> ##i##create database nova character set latin1;
-</pre>
+Query OK, 1 row affected (0.02 sec)
-Or in raw SQL, something like:
+mysql> ##i##grant all privileges on nova.* to nova@localhost identified by 'foobar';
 <pre>
-grant all privileges on nova.* to nova@localhost identified by 'foobar';
+--sql_connection=mysql://nova:foobar@localhost/nova
 </pre>
 Using a single root user account for all services is not a good policy for production deployment. Ideally, each service should have its own restricted user account with only the ability to access its own database.

@@ Line 97: / Line 97: @@
 </console>
-I am not yet completely sure how RabbitMQ fits into the OpenStack architecture. It may be that the supporting services expect it to be running locally, and that Nova compute notes need to hook into a Nova instance, which would typically be running remotely. (Thus the ability for DevStack to target a remote RabbitMQ host.)
+I am not yet completely sure how RabbitMQ fits into the OpenStack architecture. It may be that the supporting services expect it to be running locally, and that Nova compute nodes need to hook into a Nova instance, which would typically be running remotely. (Thus the ability for DevStack to target a remote RabbitMQ host.)
 == Virtualization Technology ==