Open Stack

On Fri, 2013-06-14 at 07:26 +0100, Mark McLoughlin wrote:
> > The first potential solution is to simply encrypt the password in the
> > database.  (Actually, I intend to first merge all of the RPC information
> > into a single database field, then encrypt that; that will make it
> > easier to allow for alternate communication mechanisms in the future.)
> 
> Bear in mind that we're adding the notion of a transport URL to
> oslo.messaging, partly for cells:
> 
>   https://wiki.openstack.org/wiki/Oslo/Messaging#Transport_URLs

Ah, interesting.  I had two different approaches to storing the RPC
connection information, and one of them was a URI-esque approach.  The
other was a JSON blob, which I felt might be better in the end, but I'll
definitely take a look at this…

> > The second potential solution is to drop the cells table from the
> > database and place all the data regarding cells (including the
> > connection information) into a configuration file.  (Not the master
> > configuration file; my vision here is to add a single option that says
> > to load cells data from an auxiliary JSON file, a la policies.)  The
> > problem with this approach, of course, is that the data has to be
> > migrated out of the database and into that JSON file in some fashion;
> > this can't really be adequately handled via database migrations.  We
> > also necessarily lose the ability to add and remove cells via the API.
> 
> Putting it in a config file and losing the cells management API seems
> fine to me. Not entirely sure why, but it doesn't feel unlike a lot of
> other stuff we have in our config files.
> 
> Is there any reason not to just put it in nova.conf as transport URLs?

We need different credentials for each cell, and this approach pulls
*all* of the cells information out of the database, including such
things as weighting factors; that wouldn't fit well in a transport URL.
-- 
Kevin L. Mitchell <kevin.mitchell at rackspace.com>