[openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-04 Thread Nadathur, Sundar
Hi, Cyborg needs to create RCs and traits for accelerators. The original plan was to do that with nested RPs. To avoid rushing the Nova developers, I had proposed that Cyborg could start by applying the traits to the compute node RP, and accept the resulting caveats for Rocky, till we get

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-04 Thread Eric Fried
Sundar- We've been discussing the upgrade path on another thread [1] and are working toward a solution [2][3] that would not require downtime or special scripts (other than whatever's normally required for an upgrade). We still hope to have all of that ready for Rocky, but if you'

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Stephen Finucane
On Mon, 2018-06-04 at 10:49 -0700, Nadathur, Sundar wrote: > Hi, > > Cyborg needs to create RCs and traits for accelerators. The > original plan was to do that with nested RPs. To avoid rushing > the > Nova developers, I had proposed that Cyborg could start by > applying >

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Jay Pipes
On 06/05/2018 08:50 AM, Stephen Finucane wrote: I thought nested resource providers were already supported by placement? To the best of my knowledge, what is /not/ supported is virt drivers using these to report NUMA topologies but I doubt that affects you. The placement guys will need to weigh

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Eric Fried
To summarize: cyborg could model things nested-wise, but there would be no way to schedule them yet. Couple of clarifications inline. On 06/05/2018 08:29 AM, Jay Pipes wrote: > On 06/05/2018 08:50 AM, Stephen Finucane wrote: >> I thought nested resource providers were already supported by >> plac

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Alex Xu
Maybe I missed something. Is there anyway the nova-compute can know the resources are allocated from which child resource provider? For example, the host has two PFs. The request is asking one VF, then the nova-compute needs to know the VF is allocated from which PF (resource provider). As my under

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Eric Fried
Alex- Allocations for an instance are pulled down by the compute manager and passed into the virt driver's spawn method since [1]. An allocation comprises a consumer, provider, resource class, and amount. Once we can schedule to trees, the allocations pulled down by the compute manager w

Re: [openstack-dev] [Cyborg] [Nova] Backup plan without nested RPs

2018-06-05 Thread Alex Xu
2018-06-05 22:53 GMT+08:00 Eric Fried : > Alex- > > Allocations for an instance are pulled down by the compute manager > and > passed into the virt driver's spawn method since [1]. An allocation > comprises a consumer, provider, resource class, and amount. Once we can > schedule to trees