[Openstack-devel] Splitting the nova package (and possibly others)?

[Roland Mas]

  Hi all,

  I'm still working on getting the HOWTO to lead to a working multi-node
setup, and I think we have a problem with (at least) nova regarding the
database configuration.

  The recent work led to the nova-common package creating, configuring
and populating the novadb database locally.  This works nice for the
"management" node where everything gets installed.  However, for
supplementary "compute" nodes (forgive me if I haven't got the
terminology exactly right), the various nova-* packages should be
installed but use the remote database instead.  The current nova-common
package asks the user whether to configure the database with the
dbconfig-common framework; if the user says yes, we're in business and
the database gets configured locally.  But if the user says no,
absolutely no configuration happens, nova stuff gets configured to use a
(non-existing) SQLite database, without an option to configure a remote
database.

  Based on my reading of the appropriate section of the dbconfig-common
docs at [1], I believe the way forward would be to add two more binary
packages for nova; one would be nova-localdb and create the database
locally as is currently done; the other would be nova-remotedb, and
would ask where the remote database can be found and configure the
nova.conf file accordingly.

  It may also be possible to just change nova-common to ask for the
remote database information if the user chooses not to create the
database with dbconfig-common.  I'll investigate both approaches, but
would welcome ideas if anyone has previous experience with this kind of
stuff.

Roland.

[1] http://people.debian.org/~seanius/policy/dbconfig-common.html/ch-develguide.html#s-frontends
-- 
Roland Mas

... all in all it's just another rule in the firewall.
  -- Ping Flood