[openstack-dev] [ptg][nova][neutron] modelling network capabilities and capacity in placement and nova neutron port binding negociation.

Miguel Angel Ajo Pelayo majopela at redhat.com
Mon Sep 11 17:33:42 UTC 2017


I'm also interested in this topic. :)

On Mon, Sep 11, 2017 at 11:12 AM, Jay Pipes <jaypipes at gmail.com> wrote:

> I'm interested in this. I get in to Denver this evening so if we can do
> this session tomorrow or later, that would be super.
>
> Best,
> -jay
>
>
> On 09/11/2017 01:11 PM, Mooney, Sean K wrote:
>
>> Hi everyone,
>>
>> I’m interested in set up a white boarding session at the ptg to discuss
>>
>> How to model network backend in placement and use that info as part of
>> scheduling
>>
>> This work would also intersect on the nova neutron port binding
>> negotiation
>>
>> Work that is also in flight so I think there is merit in combining both
>> topic into one
>>
>> Session.
>>
>> For several release we have been discussing a negotiation protocol that
>> would
>>
>> Allow nova/compute services to tell neutron what virtual and physical
>> interfaces
>>
>> a hypervisor can support and then allow neutron to select from that set
>> the most appriote
>>
>> vif type based on the capabilities of the network backend deployed by the
>> host.
>>
>> Extending that concept with the capabilities provided by placement and
>> trait
>>
>> Will enable us to model the network capablites of a specific network
>> backend
>>
>> In an scheduler friendly way without nova needing to understand
>> networking.
>>
>> To that end  if people are interested in  having a while boarding session
>> to dig
>>
>> Into this let me know.
>>
>> Regards
>>
>> Seán
>>
>> --------------------------------------------------------------
>> Intel Shannon Limited
>> Registered in Ireland
>> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
>> Registered Number: 308263
>> Business address: Dromore House, East Park, Shannon, Co. Clare
>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170911/c90e89fd/attachment.html>


More information about the OpenStack-dev mailing list