[openstack-dev] [cyborg] [glance] [nova] Cyborg/Nova spec for os-acc is out

Hi all,     The Cyborg compute node specification has been published: https://review.openstack.org/#/c/566798/ . Please review it. The main factors defined in this spec are: * The behavior with respect to accelerators when various Compute API [1] operations are applied. E.g. On a

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

Hi Matt, On 5/17/2018 3:18 PM, Matt Riedemann wrote: On 5/17/2018 3:36 PM, Nadathur, Sundar wrote: This applies only to the resources that Nova handles, IIUC, which does not handle accelerators. The generic method that Alex talks about is obviously preferable but, if that is not available

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

On 5/18/2018 5:06 AM, Sylvain Bauza wrote: Le ven. 18 mai 2018 à 13:59, Nadathur, Sundar <sundar.nadat...@intel.com <mailto:sundar.nadat...@intel.com>> a écrit : Hi Matt, On 5/17/2018 3:18 PM, Matt Riedemann wrote: On 5/17/2018 3:36 PM, Nadathur,

[openstack-dev] [cyborg] [nova] Cyborg quotas

Hi,    The Cyborg quota spec [1] proposes to implement a quota (maximum usage) for accelerators on a per-project basis, to prevent one project (tenant) from over-using some resources and starving other tenants. There are separate resource classes for different accelerator types (GPUs, FPGAs,

Re: [openstack-dev] [cyborg] [nova] Cyborg quotas

Hi all,     Thanks for all the feedback. Please see below. 2018-05-17 1:24 GMT+08:00 Jay Pipes >: Placement already stores usage information for all allocations of resources. There is already even a /usages API endpoint that you can

Re: [openstack-dev] [Cyborg] [Nova] Cyborg traits

On 5/30/2018 1:18 PM, Eric Fried wrote: This all sounds fully reasonable to me. One thing, though... * There is a resource class per device category e.g. CUSTOM_ACCELERATOR_GPU, CUSTOM_ACCELERATOR_FPGA. Let's propose standard resource classes for these ASAP.

[openstack-dev] [Cyborg] [Nova] Cyborg traits

Hi all,    The Cyborg/Nova scheduling spec [1] details what traits will be applied to the resource providers that represent devices like GPUs. Some of the traits referred to vendor names. I got feedback that traits must not refer to products or specific models of devices. I agree. However, we

Re: [openstack-dev] [Cyborg] [Nova] Cyborg traits

Hi Sylvain,   Glad to know we are on the same page. I haven't updated the spec with this proposal yet, in case I got more comments :). I will do so by today. Thanks, Sundar On 5/30/2018 12:34 AM, Sylvain Bauza wrote: On Wed, May 30, 2018 at 1:33 AM, Nadathur, Sundar mailto:sundar.nadat

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

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

[openstack-dev] [Nova] [Cyborg] Updates to os-acc proposal

Hi Eric and all,     With recent discussions [1], we have convergence on how Power and other architectures can use Cyborg. Before I update the spec [2], I am setting down some key aspects of the updates, so that we are all aligned. The accelerator - instance attachment has two parts: * The

Re: [openstack-dev] [Nova] [Cyborg] Updates to os-acc proposal

Hi Eric,     Please see my responses inline. On an unrelated note, thanks for the pointer to the GPU spec (https://review.openstack.org/#/c/579359/10/doc/source/specs/rocky/device-passthrough.rst). I will review that. On 7/31/2018 10:42 AM, Eric Fried wrote: Sundar- * Cyborg drivers

[openstack-dev] [Cyborg] Agent - Conductor update

Hi,    The Cyborg agent in a compute node collects information about devices from the Cyborg drivers on that node. It then needs to push that information to the Cyborg conductor in the controller, which then needs to persist it in the Cyborg db and update Placement. Further, the agent needs

Re: [openstack-dev] [Cyborg] Agent - Conductor update

Hi Zhenghao, On 8/8/2018 4:10 AM, Zhenghao ZH21 Wang wrote: Hi Sundar, All look good to me. And I agreed with the new solution as your suggestion. But I still confused why we will lost some device info if we do diff on agent? Could u give me an example to explain how to lost and what we will

[openstack-dev] [Cyborg] Update device info in db via REST API or RPC?

Hi all,   Apparently a decision was taken to have the Cyborg agent update the Cyborg database with device information using REST APIs, as part of discovery. The use of REST API has many implications: * It is open to public. So, we have to authenticate the users and check for   abuse. Even if

Re: [openstack-dev] [Cyborg] Zoom URL for Aug 29 meeting

/22/2018 11:39 PM, Nadathur, Sundar wrote: For the August 29 weekly meeting [1], the main agenda is the discussion of Cyborg device/data models. We will use this meeting invite to present slides: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/189707867 Or iPhone one-tap :     US

[openstack-dev] [Cyborg] Zoom URL for Aug 29 meeting

For the August 29 weekly meeting [1], the main agenda is the discussion of Cyborg device/data models. We will use this meeting invite to present slides: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/189707867 Or iPhone one-tap :     US: +16465588665,,189707867#  or

[openstack-dev] [Neutron] [Cyborg] Cyborg-Neutron interaction for programmable NICs

Hello Neutron folks, There is emerging interest in programmable NICs that combine FPGAs and networking in different ways. I wrote up about one category of them here: https://etherpad.openstack.org/p/fpga-networking This was discussed at the Neutron meeting on Sep 3 [1]. This approach

Re: [openstack-dev] [cyborg]Weekly Team Meeting 2018.03.14 Agenda (No Time Change For US)

Hi Howard, Can we discuss the possibility of using a filter/weigher that invokes Cyborg API, as we discussed during the Cyborg/Nova discussion in the PTG? This is line 56 in https://etherpad.openstack.org/p/cyborg-ptg-rocky-nova-cyborg-interaction . Regards, Sundar From: Zhipeng Huang

Re: [openstack-dev] [cyborg] Promote Li Liu as new core reviewer

Agreed! +1 Regards, Sundar Hi Team, This is an email for my nomination of adding Li Liu to the core reviewer team. Li Liu has been instrumental in the resource provider data model implementation for Cyborg during Queens release, as well as metadata standardization and programming design

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

no different than for any other resource. efried On 03/28/2018 12:27 PM, Nadathur, Sundar wrote: > Hi Eric and all, >     I should have clarified that this race condition happens only for > the case of devices with multiple functions. There is a prior thread

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

that already have it loaded so you can prefer those. Am I missing something? efried On 03/22/2018 11:27 PM, Nadathur, Sundar wrote: Hi all,     There seems to be a possibility of a race condition in the Cyborg/Nova flow. Apologies for missing this earlier. (You can refer to

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

GMT+08:00 Nadathur, Sundar <sundar.nadat...@intel.com <mailto:sundar.nadat...@intel.com>>: Hi all,     There seems to be a possibility of a race condition in the Cyborg/Nova flow. Apologies for missing this earlier. (You can refer to the proposed Cyborg/Nov

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

, Nadathur, Sundar wrote: Hi Eric and all,     I should have clarified that this race condition happens only for the case of devices with multiple functions. There is a prior thread <http://lists.openstack.org/pipermail/openstack-dev/2018-March/127882.html> about it. I was trying to get a solution

[openstack-dev] [cyborg] Cyborg/Nova scheduling spec

Thanks to everybody who has commented on the Cyborg/Nova scheduling spec (https://review.openstack.org/#/c/554717/). As you may have noted, some issues were raised (*1), discussed (*2) and a potential solution was offered (*3). I have tried to synthesize the new solution from Nova team here:

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

ctions separately. Please let me know if I missed something. Thanks & Regards, Sundar Am I missing something? efried On 03/22/2018 11:27 PM, Nadathur, Sundar wrote: Hi all,     There seems to be a possibility of a race condition in the Cyborg/Nova flow. Apologies f

Re: [openstack-dev] [Nova] [Cyborg] Tracking multiple functions

il.com <mailto:jaypi...@gmail.com>         <mailto:jaypi...@gmail.com <mailto:jaypi...@gmail.com>>> wrote:             On 03/02/2018 02:00 PM, Nadathur, Sundar wrote:                 Hello Nova team,                  

Re: [openstack-dev] [cyborg]Summary of Mar 14 Meeting

Hi Howard and all,     Re. my AR to write a spec, please confirm the following: * Since the weigher is part of the overall scheduling flow, I presume the spec has to cover the scheduling flow that we hashed out in the PTG. The compute node aspects could be a separate spec. * Since there

[openstack-dev] [Nova] [Cyborg] Separate spec for compute node flows?

Hi all,     The Cyborg Nova scheduling specification addresses the scheduling aspects alone. There needs to be a separate spec to address: * Cyborg/Nova interactions in the compute node, incl. the newly

[openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

Hi all,     There seems to be a possibility of a race condition in the Cyborg/Nova flow. Apologies for missing this earlier. (You can refer to the proposed Cyborg/Nova spec for details.) Consider the scenario

[openstack-dev] [Nova] [Cyborg] Tracking multiple functions

Hello Nova team, During the Cyborg discussion at Rocky PTG, we proposed a flow for FPGAs wherein the request spec asks for a device type as a resource class, and optionally a function (such as encryption) in the extra specs. This does not seem to work well for the usage model that I'll

[openstack-dev] [Nova] [Cyborg] [Glance] Updated spec for Cyborg-Nova-Glance interaction, including os-acc

Hello folks, The os-acc spec [1] has been updated substantially. Please review the new version is https://review.openstack.org/#/c/577438/ . The background for the update is that several important aspects were raised as comments on the previous spec ([1], [2]). An alternative workflow for

Re: [openstack-dev] [Nova] [Cyborg] [Glance] Updated spec for Cyborg-Nova-Glance interaction, including os-acc

s/review the new version is/review the new version/ Regards, Sundar On 6/22/2018 8:06 AM, Nadathur, Sundar wrote: Hello folks, The os-acc spec [1] has been updated substantially. Please review the new version is https://review.openstack.org/#/c/577438/ . The background for the update

[openstack-dev] [cyborg] [nova] Poll: Name for VARs

Hi, The name VAR (Virtual Accelerator Request) is introduced in https://review.openstack.org/#/c/603955/. It came up during the Stein PTG and is being used by default, but some folks have said they find the name VAR to be confusing. I would like to resolve this to completion, so that whatever

Re: [openstack-dev] [cyborg] [nova] Poll: Name for VARs

Thanks for all who participated in the discussion and/or voted. The most votes, such as there were, went for the name 'Accelerator Requests' abbrev. ARQs. The specs will be updated over the next couple of days. Have a good weekend. Best Regards, Sundar On 10/22/2018 11:37 AM, Nadathur

[openstack-dev] [cyborg] New time for Cyborg weekly IRC meetings

Hi, The current time for the weekly Cyborg IRC meeting is 1400 UTC, which is 6 am Pacific and 10pm China time. That is a bad time for most people in the call. Please vote in this doodle for what time you prefer. If you need more options, please respond in this thread. [1]