[nova][kolla] questions on cells
moreira.belmiro.email.lists at gmail.com
Tue Oct 1 15:12:55 UTC 2019
just to clarify,
CERN runs the superconductor.
Yes, affinity check is an issue. We plan work on it in the next cycle.
The metadata API runs per cell. The main reason is that we still run
nova-network in few cells.
On Mon, Sep 30, 2019 at 8:56 PM Matt Riedemann <mriedemos at gmail.com> wrote:
> On 9/30/2019 12:27 PM, Dan Smith wrote:
> >> 4. Does the cell conductor need access to the API DB?
> > Technically it should not be allowed to talk to the API DB for
> > "separation of concerns" reasons. However, there are a couple of
> > features that still rely on the cell conductor being able to upcall to
> > the API database, such as the late affinity check.
> In case you haven't seen this yet, we have a list of operations
> requiring "up-calls" from compute/cell-conductor to the API DB in the
> docs here:
> Some have been fixed for awhile and some are still open because they are
> not default configuration we normally deal with (cross_az_attach=False)
> or hit in CI* runs (reschedules).
> I think the biggest/hardest problem there to solve is the late affinity
> check which long-term should be solved with placement but no one is
> working on that. The reschedule stuff related to getting AZ/aggregate
> info is simpler but involves some RPC changes so it's not trivial and
> again no one is working on fixing that.
> I think for those reasons CERN is running without a superconductor mode
> and can hit the API DB from the cells. Devstack superconductor mode is
> the ideal though for the separation of concerns Dan pointed out.
> *Note we do hit the reschedule issue sometimes in multi-cell jobs:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss