From: Matt Van Winkle
Sent: Wednesday, July 22, 2015 9:28 AM
To: Mike Dorman; Michael Still; openstack-operators@lists.openstack.org
Cc: Andrew Laski
Subject: Re: [Openstack-operators] Nova cells v2 and operational impacts
I think I primarily echo Mike&#
On Wed, Jul 22, 2015 at 5:12 PM, Daniel Comnea 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 clusters)?
Good questio
Heya.
On Wed, Jul 22, 2015 at 9:21 AM, Mike Dorman 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
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 tha
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 wrote:
> Seems re
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 v1
Sounds like a good plan to me.
Thanks,
Kevin
From: David Medberry
Sent: Tuesday, July 21, 2015 7:51:50 AM
To: Michael Still
Cc: openstack-operators@lists.openstack.org; Andrew Laski
Subject: Re: [Openstack-operators] Nova cells v2 and operational impacts
Also
On Wed, Jul 22, 2015 at 1:14 AM, gustavo panizzo (gfa)
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
>> datab
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
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 wrote:
> Heya,
>
> the nova developer mid-cycle meetup is happening this week. We've been
> talking through the operati
On Wed, Jul 22, 2015 at 12:48 AM, Robert Collins
wrote:
> On 22 July 2015 at 02:45, Michael Still 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 th
On 22 July 2015 at 02:45, Michael Still 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 a plan that
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 a
13 matches
Mail list logo
