On 09/07/2018 11:17 AM, Dan Smith wrote:
The other obvious thing is the database. The placement repo code as-is
today still has the check for whether or not it should use the
placement database but falls back to using the nova_api database
[5]. So technically you could point the extracted
On Fri, Sep 7, 2018 at 11:18 AM Dan Smith wrote:
>
> > The other obvious thing is the database. The placement repo code as-is
> > today still has the check for whether or not it should use the
> > placement database but falls back to using the nova_api database
> > [5]. So technically you could
> The other obvious thing is the database. The placement repo code as-is
> today still has the check for whether or not it should use the
> placement database but falls back to using the nova_api database
> [5]. So technically you could point the extracted placement at the
> same nova_api database
On 9/6/2018 8:29 PM, Erik McCormick wrote:
We are planning to attend the upgrade sessions on Monday as a group. How
about we put it there?
I threw it in the upgrades sig ptg etherpad. Where it goes in the agenda
on Monday afternoon is up to you guys.
--
Thanks,
Matt
lists.openstack.org
> > Subject: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-
> > specific news on extraction
> >
> > I wanted to recap some upgrade-specific stuff from today outside of the
> > other [1] technical extraction thread.
> >
> > Chris h
ment Mailing List (not for usage questions)
> ; openstack-
> operat...@lists.openstack.org
> Subject: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-
> specific news on extraction
>
> I wanted to recap some upgrade-specific stuff from today outside of the
> othe
I wanted to recap some upgrade-specific stuff from today outside of the
other [1] technical extraction thread.
Chris has a change up for review [2] which prompted the discussion.
That change makes placement only work with placement.conf, not
nova.conf, but does get a passing tempest run in
