Open Stack

On Fri, Jun 24, 2016 at 7:42 PM, Hongbin Lu <hongbin.lu at huawei.com> wrote:

>
>
>
>
> *From:* Vikas Choudhary [mailto:choudharyvikas16 at gmail.com]
> *Sent:* June-22-16 3:58 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers
> and Magnum Integration
>
>
>
> 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?
>
> *[Hongbin Lu] The alternative is native CLI tool (i.e. kubectl, docker).
> This is unrelated to Zun. Zun is a totally independent service, regardless
> of Magnum exists or not.*
>
[Vikas] Thanks for the info Hongbin. Eli Qiao also helped clearing this
aspect over irc.

>
>
>
>
>
>    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
>
>
>
> __________________________________________________________________________
> 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/20160625/061d8ce3/attachment.html>