From: mikalst...@gmail.com <mikalst...@gmail.com> on behalf of Michael Still 
<mi...@stillhq.com>
Sent: Wednesday, July 22, 2015 9:56 AM
To: Mike Dorman
Cc: openstack-operators@lists.openstack.org; Andrew Laski
Subject: Re: [Openstack-operators] Nova cells v2 and operational impacts

Heya.

On Wed, Jul 22, 2015 at 9:21 AM, Mike Dorman <mdor...@godaddy.com> wrote:
Seems reasonable.

For us already running v1, will we be creating another new cell database
for v2?  Or will our existing v1 cell database become that second database
under v2?

Yes. Cells v2 will require a new database, you wont be able to reuse
your existing cells database.

The direction we're going is that your databases within a cell will remain but the global database that cells v1 replicates data up into will be replaced by the new api database.


Somewhat beyond the scope of this thread, but my main concern is the
acrobatics going from v1 in Kilo to the hybrid v1/v2 in Liberty, to full
v2 in Mitaka.  I think we all realize there will be some amount of pain to
get to v2, but as long as that case for us existing cells users can be
handled in a somewhat sane way, I’m happy.

I'm actually not too concerned about that bit, but then again I'm not
the primary developer on cells v2 so I might be confused. I don't
think we've documented the intended transition from cells v1 to cells
v2 in M, but perhaps Andrew Laski can chime in?

The transition path isn't fully determined and documented yet, but it will be sane for both current cells and non cells deployments. I personally will need to deal with the cells v1 to v2 transition so it will definitely be something that's thought about during development.

It's too early to get into details because multiple cells support isn't being worked on in this cycle, but ideally the migration for cells v1 and non cells will be essentially the same except that cells v1 users may need to run an upgrade script in each cell vs just running it once.


Michael

--
Rackspace Australia

_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to