Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
On Fri, Jun 24, 2016 at 7:42 PM, Hongbin Lu wrote: > > > > > *From:* Vikas Choudhary [mailto:choudharyvika...@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 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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
From: Vikas Choudhary [mailto:choudharyvika...@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 mailto:qiaoliy...@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. 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-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
Minor correction regarding kuryr-agent role. On Wed, Jun 22, 2016 at 1:27 PM, Vikas Choudhary wrote: > Hi Eli Qiao, > > Please find my responses inline. > > On Wed, Jun 22, 2016 at 12:47 PM, taget 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, it will be working on > compute machine. Only kuryr-agent will be tagging data traffic from > containers. > >> >> >> >> -- >> Best Regards, >> Eli Qiao (乔立勇), Intel OTC. >> >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
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 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
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 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? -- Best Regards, Eli Qiao (乔立勇), Intel OTC. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
Hi All, Following is the tasks split-up: *Kuryr:* 1. Refactoring existing code into kuryr common library(kuryr-server)(to be run on controller node and responsible for communication with other openstack services) and kuryr agent(vif binding) including rpc support. 2. Enhancing Kuryr server and agent for subport CRUD operations and vlan tagging of subports. Magnum: 1. Support to pass neutron network names at container creation apis such as pod-create in k8s case. 2. 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. Please feel free to update any action item which i might have missed. I have started working on refactoring part. Soon will push first patch for review comments. -Vikas On Tue, Jun 21, 2016 at 9:15 PM, Hongbin Lu wrote: > Gal, > > > > Thanks for starting this ML. Since the work involves both team, I think it > is a good idea to start by splitting the task first. Then, we can see which > items go to which teams. Vikas, do you mind to update this ML once the task > is spitted? Thanks in advance. > > > > Best regards, > > Hongbin > > > > *From:* Gal Sagie [mailto:gal.sa...@gmail.com] > *Sent:* June-21-16 2:14 AM > *To:* OpenStack Development Mailing List (not for usage questions); Vikas > Choudhary; Antoni Segura Puimedon; Irena Berezovsky; Fawad Khaliq; Omer > Anson; Hongbin Lu > *Subject:* [Kuryr][Magnum] - Kuryr nested containers and Magnum > Integration > > > > Hello all, > > > > I am writing this out to provide awareness and hopefully get some work > started > > on the above topic. > > > > We have merged a spec about supporting nested containers and integration > with Magnum > > some time ago [1] , Fawad (CCed) led this spec. > > > > We are now seeking for volunteers to start implementing this on both Kuryr > and the needed > > parts in Magnum. > > > > Vikas (CCed) volunteered in the last IRC meeting [2] to start and split > this work into sub-tasks > > so it will be easier to share, anyone else that is interested to join this > effort is more then welcome to join in and contact Vikas. > > I do know several other people showed interest to work on this so i hope > we can pull everyone > > together in this thread, or online at IRC. > > > > Thanks > > Gal. > > > > [1] https://review.openstack.org/#/c/269039/ > > [2] > http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-06-20-14.00.html > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
Gal, Thanks for starting this ML. Since the work involves both team, I think it is a good idea to start by splitting the task first. Then, we can see which items go to which teams. Vikas, do you mind to update this ML once the task is spitted? Thanks in advance. Best regards, Hongbin From: Gal Sagie [mailto:gal.sa...@gmail.com] Sent: June-21-16 2:14 AM To: OpenStack Development Mailing List (not for usage questions); Vikas Choudhary; Antoni Segura Puimedon; Irena Berezovsky; Fawad Khaliq; Omer Anson; Hongbin Lu Subject: [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration Hello all, I am writing this out to provide awareness and hopefully get some work started on the above topic. We have merged a spec about supporting nested containers and integration with Magnum some time ago [1] , Fawad (CCed) led this spec. We are now seeking for volunteers to start implementing this on both Kuryr and the needed parts in Magnum. Vikas (CCed) volunteered in the last IRC meeting [2] to start and split this work into sub-tasks so it will be easier to share, anyone else that is interested to join this effort is more then welcome to join in and contact Vikas. I do know several other people showed interest to work on this so i hope we can pull everyone together in this thread, or online at IRC. Thanks Gal. [1] https://review.openstack.org/#/c/269039/ [2] http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-06-20-14.00.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration
Hello all, I am writing this out to provide awareness and hopefully get some work started on the above topic. We have merged a spec about supporting nested containers and integration with Magnum some time ago [1] , Fawad (CCed) led this spec. We are now seeking for volunteers to start implementing this on both Kuryr and the needed parts in Magnum. Vikas (CCed) volunteered in the last IRC meeting [2] to start and split this work into sub-tasks so it will be easier to share, anyone else that is interested to join this effort is more then welcome to join in and contact Vikas. I do know several other people showed interest to work on this so i hope we can pull everyone together in this thread, or online at IRC. Thanks Gal. [1] https://review.openstack.org/#/c/269039/ [2] http://eavesdrop.openstack.org/meetings/kuryr/2016/kuryr.2016-06-20-14.00.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
