[openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
Vikas Choudhary
choudharyvikas16 at gmail.com
Wed Jun 22 07:57:59 UTC 2016
Hi Eli Qiao,
Please find my responses inline.
On Wed, Jun 22, 2016 at 12:47 PM, taget <qiaoliyong at gmail.com> wrote:
> hi Vikas,
> thanks for you clarify, relied in lines.
>
> On 2016年06月22日 14:36, Vikas Choudhary wrote:
>
>
> Magnum:
>
> 1. Support to pass neutron network names at container creation apis
> such as pod-create in k8s case.
>
> Hmm. Magnum has deleted all wrapper API for container creation and
> pod-create
>
Oh, I was referring to older design then. In that case, What would be
corresponding alternative now?
Is this related to Zun somehow?
>
>
> 1. If Kuryr is used as network driver at bay creation, update heat
> template creation logic for kuryr-agent provisioning on all the bay nodes.
> This will also include passing required configuration and credentials also.
>
>
> In this case, I am confused, we need to install kuryr-agent on all bay
> nodes, so and kuryr-agent's for binding neutron ports and containers port,
> we will need to install neutron-agent on bay nodes too?
>
Neutron-agent will not be required on bay nodes. Only kuryr-agent will be
sufficient to plumb the vifs and vlan tagging.
>
>
>
> --
> Best Regards,
> Eli Qiao (乔立勇), Intel OTC.
>
>
> __________________________________________________________________________
> 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/20160622/41940400/attachment.html>
More information about the OpenStack-dev
mailing list