[openstack-dev] [kuryr][kuryr-kubernetes] Propose to support Kubernetes Network Custom Resource Definition De-facto Standard Version 1

Antoni Segura Puimedon celebdor at gmail.com
Thu Jun 7 08:08:00 UTC 2018


On Thu, Jun 7, 2018 at 3:52 AM, Peng Liu <pliu at redhat.com> wrote:
> Cool.
> I'll start to prepare a BP for this, so we can have more detailed
> discussion.

Great!

>
> On Wed, Jun 6, 2018 at 11:08 PM, Antoni Segura Puimedon <celebdor at gmail.com>
> wrote:
>>
>> On Wed, Jun 6, 2018 at 2:37 PM, Irena Berezovsky <irenab.dev at gmail.com>
>> wrote:
>> > Sounds like a great initiative.
>> >
>> > Lets follow up on the proposal by the kuryr-kubernetes blueprint.
>>
>> I fully subscribe what Irena said. Let's get on this quick!
>>
>> >
>> > BR,
>> > Irena
>> >
>> > On Wed, Jun 6, 2018 at 6:47 AM, Peng Liu <pliu at redhat.com> wrote:
>> >>
>> >> Hi Kuryr-kubernetes team,
>> >>
>> >> I'm thinking to propose a new BP to support  Kubernetes Network Custom
>> >> Resource Definition De-facto Standard Version 1 [1], which was drafted
>> >> by
>> >> network plumbing working group of kubernetes-sig-network. I'll call it
>> >> NPWG
>> >> spec below.
>> >>
>> >> The purpose of NPWG spec is trying to standardize the multi-network
>> >> effort
>> >> around K8S by defining a CRD object 'network' which can be consumed by
>> >> various CNI plugins. I know there has already been a BP VIF-Handler And
>> >> Vif
>> >> Drivers Design, which has designed a set of mechanism to implement the
>> >> multi-network functionality. However I think it is still worthwhile to
>> >> support this widely accepted NPWG spec.
>> >>
>> >> My proposal is to implement a new vif_driver, which can interpret the
>> >> PoD
>> >> annotation and CRD defined by NPWG spec, and attach pod to additional
>> >> neutron subnet and port accordingly. This new driver should be mutually
>> >> exclusive with the sriov and additional_subnets drivers.So the endusers
>> >> can
>> >> choose either way of using mult-network with kuryr-kubernetes.
>> >>
>> >> Please let me know your thought, any comments are welcome.
>> >>
>> >>
>> >>
>> >> [1]
>> >>
>> >> https://docs.google.com/document/d/1Ny03h6IDVy_e_vmElOqR7UdTPAG_RNydhVE1Kx54kFQ/edit#heading=h.hylsbqoj5fxd
>> >>
>> >>
>> >> Regards,
>> >>
>> >> --
>> >> Peng Liu
>> >>
>> >>
>> >> __________________________________________________________________________
>> >> 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
>> >>
>> >
>> >
>> >
>> > __________________________________________________________________________
>> > 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
>> >
>>
>> __________________________________________________________________________
>> 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
>
>
>
>
> --
> Peng Liu
>
> __________________________________________________________________________
> 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
>



More information about the OpenStack-dev mailing list