Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-22 Thread Michael Still
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

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-22 Thread Michael Still
On Wed, Jul 22, 2015 at 5:12 PM, Daniel Comnea comnea.d...@gmail.com wrote: Michael, Just to clear an assumption on my head: by new mysql database you mean a new mysql instance? If is the latter one, how do you see the deployment to be with 2 mysql instances (possible in different

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-22 Thread Matt Van Winkle
I think I primarily echo Mike's questions. For me, I'd like to see the primary DB in cells v2 only have the data necessary for the APIs to know which cell an instance is associate with - versus having to copy every detail from every cell DB. I do wonder, for those of us using cells v1, what that

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-22 Thread Daniel Comnea
Michael, Just to clear an assumption on my head: by new mysql database you mean a new mysql instance? If is the latter one, how do you see the deployment to be with 2 mysql instances (possible in different clusters)? Cheers, Dani On Wed, Jul 22, 2015 at 12:21 AM, Mike Dorman

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread David Medberry
Also, if there is feedback, getting it in today or tomorrow would be most effective. Michael, this plan works for me/us. TWC. -d On Tue, Jul 21, 2015 at 9:45 AM, Michael Still mi...@stillhq.com wrote: Heya, the nova developer mid-cycle meetup is happening this week. We've been talking

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread gustavo panizzo (gfa)
On 2015-07-21 22:45, Michael Still wrote: We therefore propose the following: - all operators when they hit Liberty will need to add a new connection string to their nova.conf which configures this new mysql database, there will be a release note to remind you to do this. - we will add

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread Michael Still
On Wed, Jul 22, 2015 at 1:14 AM, gustavo panizzo (gfa) g...@zumbi.com.ar wrote: On 2015-07-21 22:45, Michael Still wrote: We therefore propose the following: - all operators when they hit Liberty will need to add a new connection string to their nova.conf which configures this new mysql

[Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread Michael Still
Heya, the nova developer mid-cycle meetup is happening this week. We've been talking through the operational impacts of cells v2, and thought it would be a good idea to mention them here and get your thoughts. First off, what is cells v2? The plan is that _every_ nova deployment will be running

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread Robert Collins
On 22 July 2015 at 02:45, Michael Still mi...@stillhq.com wrote: Heya, ... So what's the actual question? We're introducing an additional mysql database that every nova deployment will need to possess in Liberty. We talked through having this data be in the existing database, but that wasn't

Re: [Openstack-operators] Nova cells v2 and operational impacts

2015-07-21 Thread Mike Dorman
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? Somewhat beyond the scope of this thread, but my main concern is the acrobatics going from v1 in Kilo to the hybrid