Re: [openstack-dev] [kuryr] Nominate Kirill Zaitsev as kuryr-tempest-core reviewer

+1 On Tue, Jul 4, 2017 at 7:59 PM, Antoni Segura Puimedon wrote: > On Tue, Jul 4, 2017 at 12:23 PM, Gal Sagie wrote: > > +1 > +1 > > > > On Tue, Jul 4, 2017 at 12:28 PM, Daniel Mellado < > daniel.mellado...@ieee.org> > > wrote: > >> > >> Hi Team, > >> > >> I wanted to nominate Kirill for kuryr-

Re: [openstack-dev] [kuryr] Ocata cycle ending and proposing new people as Kuryr cores

+1 for both. On Sun, Jan 15, 2017 at 12:42 PM, Gal Sagie wrote: > +1 for both. > > On Sun, Jan 15, 2017 at 9:05 AM, Irena Berezovsky > wrote: > >> >> >> On Fri, Jan 13, 2017 at 6:49 PM, Antoni Segura Puimedon < >> celeb...@gmail.com> wrote: >> >>> Hi fellow kuryrs! >>> >>> We are getting close

Re: [openstack-dev] [kuryr][magnum] Notes from Summit fishbowl session

On Thu, Nov 3, 2016 at 12:33 AM, Antoni Segura Puimedon wrote: > Hi magna and kuryrs! > > Thank you all for joining last week meetings. I am now writing a few > emails to have persistent notes of what was talked about and discussed > in the Kuryr work sessions. In the Magnum joint session the poi

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

. -Vikas > > > Regards, > Liping Mao > > From: Vikas Choudhary > Reply-To: OpenStack List > Date: 2016年9月14日 星期三 下午1:10 > > To: OpenStack List > Subject: Re: [openstack-dev] [Kuryr] IPVLAN data path proposal > > > > On Wed, Sep 14, 2016 at 10:33 AM

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 10:33 AM, Vikas Choudhary < choudharyvika...@gmail.com> wrote: > > > On Wed, Sep 14, 2016 at 9:39 AM, Liping Mao (limao) > wrote: > >> > Though, not the best person to comment on macvlan vs ipvlan, one >> limitation of macvlan is

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

> need a very new kernel , it maybe a little bit hard to use in prod > env(AFAIK). > You have a valid point regarding ipvlan support in newer kernel versions but IIUC overlay mode might not help if nic has a limit on max number of macs that it supports in hardware. > > Regards, >

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Wed, Sep 14, 2016 at 7:10 AM, Liping Mao (limao) wrote: > Hi Ivan and Gary, > > maybe we can use macvlan as ipvlan need very new kernel. > allow-address-pairs can aslo allow different mac in vm. > Do we consider macvlan here? Thanks. > Though, not the best person to comment on macvlan vs ipvl

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 11:13 PM, Antoni Segura Puimedon wrote: > On Tue, Sep 13, 2016 at 5:05 PM, Hongbin Lu wrote: > > > > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary > > wrote: > >> > >> > >> > >> On Mon,

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 5:26 PM, Liping Mao (limao) wrote: > Hi Ivan， > > It sounds cool！ > > for security group and allowed address pair， > Maybe we can disable port-security，because all the docker in one vm will > share one security group on the vm port. I'm not sure how to use sg for > each do

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Tue, Sep 13, 2016 at 8:35 PM, Hongbin Lu wrote: > > > On Tue, Sep 13, 2016 at 2:10 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> >> >> On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote: >> >>> Ivan, >>> >>

Re: [openstack-dev] [kuryr] Spec and devref placement

I like both, 'a' and 'b', options. Would give a slight preferance to 'a', all documentation at one place. -VikasC On Mon, Sep 12, 2016 at 8:48 PM, Irena Berezovsky wrote: > I am fine with option (b) as well. > We can add option (d): > Specs in openstack/*kuryr-specs* but devrefs in each specifi

Re: [openstack-dev] [Kuryr] IPVLAN data path proposal

On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote: > Ivan, > > Thanks for the proposal. From Magnum's point of view, this proposal > doesn't seem to require to store neutron/rabbitmq credentials in tenant VMs > which is more desirable. I am looking forward to the PoC. > Hogbin, Can you please el

Re: [openstack-dev] [Kuryr] Proposing vikasc for kuryr-libnetwork core

Thanks everyone! I really appreciate this. Happy to join Kuryr-Core :) We have a great team, very diverse and very dedicated. It's pleasure to work with all of you. Thanks, Vikas Choudhary On Sat, Aug 20, 2016 at 11:51 PM, Gal Sagie wrote: > The entire core team voted +1. > I

Re: [openstack-dev] [Kuryr] Need help in jenkins failure

Lets see :) > Regards, > Liping Mao > > From: Vikas Choudhary > Date: 2016年8月12日 星期五 下午1:33 > To: Liping Mao > Cc: OpenStack List , Irena Berezovsky < > ir...@midokura.com>, Antoni Segura Puimedon , > Gal Sagie , Mohammad Banikazemi > Subject: Re: [Kuryr] Ne

Re: [openstack-dev] [Kuryr] Need help in jenkins failure

schoudhary16/kuryr/blob/ > drop_libnet_specific_code/ku > ryr/lib/config.py#L105 > > Thanks. > > > > Regards, > Liping Mao > > > From: Vikas Choudhary > Date: 2016年8月12日 星期五 下午12:32 > To: OpenStack List , Irena Berezovsky > , Antoni Segura Puimedon >

[openstack-dev] [Kuryr] Need help in jenkins failure

y try this patch locally and provide some input on how can i fix this? Regards Vikas Choudhary [1] https://review.openstack.org/#/c/350406/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstac

[openstack-dev] [Kuryr] Questions regarding Kuryr

Hi Amir, Thank You for showing interest in Kuryr!!! One simple approach could be: 1> Have neutron and keystone running. 2> git clone kuryr-libnetwork repo and follow Readme instructions to install kuryr. Hope this helps. If you still face issues, p

Re: [openstack-dev] [Kuryr] Kuryr IRC Meeting time

On Tue, Jul 26, 2016 at 5:36 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Tue, Jul 26, 2016 at 12:53 PM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> +1 >> On 26 Jul 2016 15:45, "Liping Mao (limao)"

Re: [openstack-dev] [Kuryr] Kuryr IRC Meeting time

+1 On 26 Jul 2016 15:45, "Liping Mao (limao)" wrote: > Hi Team, > > Currently, kuryr team meeting time is as following: > > Every two weeks (on even weeks) on Tuesday at 0300 UTC in > #openstack-meeting-4 > > > Every two weeks (on odd weeks) on Monday at 1400 UTC in > #openstack-meeting-4 > > > >

[openstack-dev] [Kuryr] devref overlapping cidrs

Hello Everybody!!! I request everybody to lease review https://review.openstack.org/#/c/326894/ Regards Vikas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstac

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Hello Everybody !!! As we discussed in the meeting yesterday, I have submitted restructured patches now in kuryr-lib and kuryr-libnetwork to address only dropping non-relevant code and adding kuryr-lib as dependency to kuryr-libnetwork. Please provide review comments so that i quickly reiterate o

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

, 2016 at 3:45 PM, Vikas Choudhary wrote: > > > On Tue, Jun 28, 2016 at 3:41 PM, Antoni Segura Puimedon < > toni+openstac...@midokura.com> wrote: > >> >> >> On Tue, Jun 28, 2016 at 11:54 AM, Vikas Choudhary < >> choudharyvika...@gmail.com> wrote: >

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

tails for Vikas Choudhary ---07/01/2016 11:29:14 > AM---Hi Toni, There seems to be some problem with. I cloned ku]Vikas > Choudhary ---07/01/2016 11:29:14 AM---Hi Toni, There seems to be some > problem with. I cloned kuryr-libnetwork: > > From: Vikas Choudhary > To: Antoni Segura

Re: [openstack-dev] [kuryr] kuryr-libnetwork split

Hi Toni, There seems to be some problem with. I cloned kuryr-libnetwork: > git clone http://github.com/openstack/kuryr-libnetwork.git But when pushed patch, on gerrit its showing project "openstack/kuryr" PTAL, https://review.openstack.org/#/c/336617/ -Vikas On Fri, Jul 1, 2016 at 6:40 PM,

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Tue, Jun 28, 2016 at 3:41 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Tue, Jun 28, 2016 at 11:54 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> >> >> On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segur

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

On Tue, Jun 28, 2016 at 1:53 PM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Mon, Jun 27, 2016 at 11:10 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> >> >> On Mon, Jun 27, 2016 at 2:22 PM, Fawad Khaliq wro

Re: [openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

t; > On Fri, Jun 24, 2016 at 9:45 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi Team, >> >> As already discussed with some of teammates over irc and internally, >> thought of bringing discussionto ml for more opinions: >> >> My i

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] -

[openstack-dev] [Kuryr] Refactoring into common library and kuryr-libnetwork + Nested_VMs

: Vikas Choudhary Date: Thu, Jun 23, 2016 at 2:54 PM Subject: Re: Kuryr Refactoring into common library and kuryr-libnetwork + Nested_VMs To: Antoni Segura Puimedon @Toni, Can you please explain a bit on how the roles regarding vlan/segmentation id allocation, tagging ang untagging containers

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 lin

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

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

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 > Choudhar

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE",

yes, recheck fixed it this time. Thanks Vikas On Tue, Jun 21, 2016 at 11:13 AM, Will Zhou wrote: > recheck fix my problem. You can try that. Thanks. > > On Tue, Jun 21, 2016 at 1:21 PM Andreas Jaeger wrote: > >> On 06/21/2016 06:35 AM, Vikas Choudhary wrote: >> &g

Re: [openstack-dev] [Kuryr] jenkins failures "POST_FAILURE", logs not accessible

It seems to be working now after recheck. Ignore please for now. Regards Vikas On Tue, Jun 21, 2016 at 10:05 AM, Vikas Choudhary < choudharyvika...@gmail.com> wrote: > Hi Team, > > Since yesterday, I am observing abnormal jenkins failures on some of > patches while others

[openstack-dev] [Kuryr] jenkins failures "POST_FAILURE", logs not accessible

Hi Team, Since yesterday, I am observing abnormal jenkins failures on some of patches while others are fine. Also not able to access logs for failures. https://review.openstack.org/#/c/326303/8 Jenkins check Jun 20 12:32 PM gate-kuryr-docs

[openstack-dev] [Kuryr] roles of kuryr server in server/agent mode

To me it seems like all queries such vlan-ID allocation, subport creation, ips etc , kuryr(running inside vm) should be able to make to neutron. Will appreciate few inputs from your side. Thanks & Regards Vikas

Re: [openstack-dev] [Kuryr] IPAM issue with multiple docker networks having same cidr subnets

Hi All, I humbly request everybody to review this bp [1] and provide inputs once you got some time. Thanks Vikas [1] https://blueprints.launchpad.net/kuryr/+spec/address-scopes-spaces On Sat, May 28, 2016 at 10:08 AM, Vikas Choudhary < choudharyvika...@gmail.com> wrote: > Thanks To

Re: [openstack-dev] [Kuryr] IPAM issue with multiple docker networks having same cidr subnets

://blueprints.launchpad.net/kuryr/+spec/address-scopes-spaces On Sat, May 28, 2016 at 1:54 AM, Antoni Segura Puimedon < toni+openstac...@midokura.com> wrote: > > > On Thu, May 26, 2016 at 9:48 PM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi Al

Re: [openstack-dev] [Kuryr] Docker failed to add an existed network with GW interface already created

Hi Liping Mao, Please find my response inline. If still not clear or i am wrong somewhere please let me know. Regards Vikas On Fri, May 27, 2016 at 10:37 AM, 毛立平 wrote: > Hi Irena, > > Thanks for your comments. > > Currently, kuryr will create gw port with owner kuryr:container, but this > GW

[openstack-dev] [Kuryr] IPAM issue with multiple docker networks having same cidr subnets

Hi All, Recently, Banix observed and brought into notice this issue [1]. To solve this, i could think of two approaches: 1. Modifying the libnetwork apis to get PoolID also at network creation. OR 2. Enhancing the /network docker api to get PoolID details also Problem with the first approac

Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup

repo. Can i directly download kuryr.conf from somewhere else? or > tox does more than creating kuryr_sample.conf? > > Thanks > Akshay > > On Thu, May 26, 2016 at 9:08 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi Akshay, >> >> Sorr

Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup

Hi Akshay, Sorry about that. You need to run "tox -e genconfig" . After this inside kuryr/etc "kuryr.conf_sample" file will get generated. Copy this file to /etc/kuryr/ after renaming to kuryr.conf. Documentation will be updated soon. -Vikas . On Wed, May 25, 2016 at 8:44 PM, Akshay Kumar Sangh

Re: [openstack-dev] [kuryr] Did kuryr need to know about Docker's cluster store?

Since libnetwork talks to cluster store independent of plugin, I think no changes are required on Kuryr side. Regards Vikas On Thu, Mar 3, 2016 at 9:54 PM, Mike Spreitzer wrote: > On Feb 5 I was given a tarchive of kuryr with an install script that > configures the docker daemon to use consul

Re: [openstack-dev] [kuryr] Does Kuryr support multi-tenant

On 26 Jan 2016 13:30, "Liping Mao (limao)" wrote: > > Hi Gal, > > Thanks for your answer. > > >The question is what you mean by multi-tenancy, if you mean that different tenants each control their own bare-metal > >server then Kuryr already support this. (by tenant credential configuration) > >

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

Cheers :) !! On Wed, Jan 20, 2016 at 3:41 PM, Mars Ma wrote: > Much thanks to @Vikas > > Thanks & Best regards ! > Mars Ma > > > On Wed, Jan 20, 2016 at 5:55 PM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > &

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

',\n >u'description': u'Optionally, the IPAM driver may provide a Gateway for > the subnet represented by the Pool.'},\n u'Pool': > {u'$ref': u'#/definitions/commons/definitions/cidr',\n > u&#x

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

gt; it got invalid gateway CIDR address: /24 , I don't know why > > Thanks you & Best regards ! > Mars Ma > - > > On Wed, Jan 20, 2016 at 11:53 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi Mars, >

Re: [openstack-dev] [Kuryr] Need review help on IPAM patches

evstack/tools/worlddump.py - Will appreciate any help or pointers. -Vikas On Tue, Jan 19, 2016 at 9:15 AM, Vikas Choudhary wrote: > Hi Kuryr Team, > > As discussed in last meeting, here i am sharing review requests which are > related to IPAM. Please have a look: > > https:/

Re: [openstack-dev] [kuryr] Failed to create network with kuryr driver type

Hi Mars, Please use "--ipam-driver=kuryr" also. Kuryr has its own ipam driver. Please refer this also: https://github.com/openstack/kuryr/blob/master/doc/source/devref/libnetwork_remote_driver_design.rst#libnetwork-user-workflow-with-kuryr-as-remote-network-driver---host-networking Hope this hel

[openstack-dev] [Kuryr] Need review help on IPAM patches

094/> - https://review.openstack.org/#/c/265732/ - https://review.openstack.org/#/c/265744/ - https://review.openstack.org/#/c/267302/ Thanks & Regards Vikas Choudhary __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Kuryr] IRC Meeting - Tuesday 0300 UTC (12/15)

Hi All, I request you all to please go though IPAM changes and related changes in network driver. Its been a very long time since changes are in review state. https://review.openstack.org/#/q/owner:+vikaschoudhary16+status:open Thanks & Regards Vikas Choudhary On Sun, Dec 13, 2015 at 5:3

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

Hi Gal, Would be happy to help. Please count me IN. -Vikas Choudhary On Thu, Dec 10, 2015 at 7:41 PM, Gal Sagie wrote: > Hello everyone, > > As some of you have already noticed one of the top priorities for Kuryr > this cycle is to get > our CI and gate testing done. > >

[openstack-dev] [neutron][kuryr] ipam driver implementation

Hi Team, I would like to request you all to go through https://review.openstack.org/#/c/248042/ once you get some time, so that we can leverage next weekly meeting time efficiently. Thanks Vikas Choudhary __ OpenStack

Re: [openstack-dev] [kuryr] mutihost networking with nova vm as docker host

itly as vm-holding >> container. >> > > container-in-vm? > > >> >> On Fri, Nov 6, 2015 at 12:13 PM, Vikas Choudhary < >> choudharyvika...@gmail.com> wrote: >> >>> @Gal, I was asking about "container in nova vm" case. >>&g

Re: [openstack-dev] [Neutron][kuryr] network control plane (libkv role)

will result in two "source of truth" in that case. Thoughts? -Vikas On Fri, Nov 6, 2015 at 9:19 AM, Vikas Choudhary wrote: > @Taku, > > Please have a look on this discussion. This is all about local and global > scope: > https://github.com/docker/libnetwork/issues/486

Re: [openstack-dev] [kuryr] mutihost networking with nova vm as docker host

in the compute host > and only perform VLAN tagging inside the VM (as Toni mentioned) > > If you need more clarification you can catch me on IRC as well and we can > talk. > > On Thu, Nov 5, 2015 at 8:03 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > &g

Re: [openstack-dev] [Neutron][kuryr] network control plane (libkv role)

issue. Only networks created with kuryr were not getting synced. Thanks Vikas Choudhary On Fri, Nov 6, 2015 at 8:07 AM, Taku Fukushima wrote: > Hi Vikas, > > I thought the "capability" affected the propagation of the network state > across nodes as well. However, in m

Re: [openstack-dev] [Neutron][kuryr] network control plane (libkv role)

Thanks Toni. On 5 Nov 2015 16:02, "Antoni Segura Puimedon" wrote: > > > On Thu, Nov 5, 2015 at 10:47 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> ++ [Neutron] tag >> >> >> On Thu, Nov 5, 2015 at 10:40 AM, Vikas Choudhar

Re: [openstack-dev] [Neutron][kuryr] network control plane (libkv role)

++ [Neutron] tag On Thu, Nov 5, 2015 at 10:40 AM, Vikas Choudhary wrote: > Hi all, > > By network control plane i specifically mean here sharing network state > across docker daemons sitting on different hosts/nova_vms in multi-host > networking. > > libnetwork provi

Re: [openstack-dev] [Neutron] [kuryr] external-network-connectivity

++[Neutron] tag On Thu, Nov 5, 2015 at 2:43 PM, Fawad Khaliq wrote: > > On Thu, Nov 5, 2015 at 10:07 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> @Fawad, >> >> I could not get you completely. Are you suggesting to write a spec my >>

Re: [openstack-dev] [Neutron][kuryr] mutihost networking with nova vm as docker host

++[Neutron] tag On Thu, Nov 5, 2015 at 11:33 AM, Vikas Choudhary wrote: > Hi All, > > I would appreciate inputs on following queries: > 1. Are we assuming nova bm nodes to be docker host for now? > > If Not: > - Assuming nova vm as docker host and ovs

Re: [openstack-dev] [kuryr] external-network-connectivity

ere [1] > > [1] https://review.openstack.org/#/c/241935/ > > Thanks, > Fawad Khaliq > > > On Thu, Nov 5, 2015 at 7:08 AM, Vikas Choudhary < > choudharyvika...@gmail.com> wrote: > >> Hi All, >> >> Would appreciate your views on >> https://blueprint

[openstack-dev] [kuryr] external-network-connectivity

Hi All, Would appreciate your views on https://blueprints.launchpad.net/kuryr/+spec/external-network-connectivity . -Vikas Choudhary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

[openstack-dev] [kuryr] mutihost networking with nova vm as docker host

in any of the binding patches[2][3][4]. Dont we need that? [1] https://etherpad.openstack.org/p/Kuryr_vif_binding_unbinding [2] https://review.openstack.org/#/c/241558/ [3] https://review.openstack.org/#/c/232948/1 [4] https://review.openstack.org/#/c/227972/ -Vikas

[openstack-dev] [kuryr] network control plane (libkv role)

could create network in docker on other hosts. Is this correct? 2. Why we cannot set default scope as "Global" and let libkv do the network state sync work? Thoughts? Regards -Vikas Choudhary __ OpenStack De

Re: [openstack-dev] [kuryr] competing implementations

If we see from the angle of the contributor whose approach would not be better than other competing one, it will be far easy for him to accept logic at discussion stage rather after weeks of tracking review request and addressing review comments. On 5 Nov 2015 08:24, "Vikas Choudhary&qu

Re: [openstack-dev] [kuryr] competing implementations

@Toni , In scenarios where two developers, with different implementation approaches, are not able to reach any consensus over gerrit or ml, IMO, other core members can do a voting or discussion and then PTL should take a call which one to accept and allow for implementation. Anyways community has

Re: [openstack-dev] [Magnum] Coe components status

— > Egor > > From: Vikas Choudhary choudharyvika...@gmail.com>> > Date: Wednesday, October 21, 2015 at 16:04 > To: Walmart Associate mailto:e...@walmartlabs.com>> > Subject: Re: [openstack-dev] [Magnum] Coe components status > > @Egor, > > Kubectl commnad is &qu

Re: [openstack-dev] [Magnum] Coe components status

that it will be nice if could support this feature for all. I will prefer to start with k8s first and if similar feature is supported by mesos and swarm also, incrementally will implement that also. Regards Vikas Choudhary On Wed, Oct 21, 2015 at 6:50 AM, Qiao,Liyong wrote: > hi Vikas, > th

[openstack-dev] [Magnum] Coe components status

agnum like "magnum coe-component-status" leveraging coe provided rest api and result will be shown to user. [1] https://blueprints.launchpad.net/magnum/+spec/coe-component-status -Vikas Choudhary __ OpenStack Developme

Re: [openstack-dev] [magnum] Document adding --memory option to create containers

In my opinion, there should be a more detailed document explaining importance of commands and options. Though --memory is an important attribute, but since objective of quickstart is to get user a minimum working system within minimum time, it seems better to skip this option in quickstart. -Vika

[openstack-dev] [Kuryr] tox -egenconfig not working

ut I noticed it was during the documentation tests. On 10/1/15, 7:20 PM, "Michal Rostecki" http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>> wrote: >*Hi, *>>*On Wed, Sep 30, 2015 at 2:27 PM, Vikas Choudhary *>*http://lists.openstack.org/cgi-bin/mailman/li

[openstack-dev] [Kuryr] tox -egenconfig not working

Hi, I tried to generate sample kuryr.using "tox -e genconfig", but it is failing: genconfig create: /home/vikas/kuryr/.tox/genconfig genconfig installdeps: -r/home/vikas/kuryr/requirements.txt, -r/home/vikas/kuryr/test-requirements.txt ERROR: could not install deps [-r/home/vikas/kuryr/requiremen

[openstack-dev] [magnum] Handling password for k8s

Thanks Hongbin. I was not aware of stack-parameters visibility, so was not able to figure out actual concerns in Ton's initial approach. keystone domain approach seems secure enough. -Vikas Hongbin, I believe the domain approach

[openstack-dev] [magnum] Handling password for k8s

Hi Ton, kube-masters will be nova instances only and because any access to nova-instances is already being secured using keystone, I am not able to understand what are the concerns in storing password on master-nodes. Can you please list down concerns in our current approach? -Vikas Choudhary

[openstack-dev] [Magnum] Implementing a baymodel attributes validation restful api

Hi Team, Any thoughts on this? https://blueprints.launchpad.net/magnum/+spec/baymodel-all-attributes-validation Thanks Vikas Choudhary __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack

[openstack-dev] [magnum] Is magnum db going to be removed for k8s resources?

tps://blueprints.launchpad.net/openstack/?searchtext=objects-from-bay> 2015-09-14 14:39 GMT+08:00 Vikas Choudhary http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>>: >* Hi Team, *>>* As per object-from-bay blueprint implementation [1], all calls to magnum db *>

[openstack-dev] [magnum] Is magnum db going to be removed for k8s resources?

Hi Team, As per object-from-bay blueprint implementation [1], all calls to magnum db are being skipped for example pod.create() etc. Are not we going to use magnum db at all for pods/services/rc ? Thanks Vikas Choudhary [1] https://review.openstack.org/#/c/213368

[openstack-dev] [magnum] Is magnum db going to be removed for k8s resources?

Hi Team, As per object-from-bay blueprint implementation [1], all calls to magnum db are being skipped for example pod.create() etc. Are not we going to use magnum db at all for pods/services/rc ? Thanks Vikas Choudhary

[openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

Is it like keystone authenticating between magnum-client and magnum conductor, and barbican certs will be used b/w conductor and k8s/swarm? Thanks Vikas Choudhary _ Simply put, Keystone is designed to generate tokens that are to be

[openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

both keystone and Barbican features as they allow us to iterate toward a more secure integration. Adrian > On Aug 31, 2015, at 9:05 PM, Vikas Choudhary <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>> wrote: > > Hi, > > Can anybody please point me out

[openstack-dev] [magnum] Difference between certs stored in keystone and certs stored in barbican

Hi, Can anybody please point me out some etherpad discussion page/spec that can help me understand why we are going to introduce barbican for magnum when we already had keystone for security management? -Vikas Choudhary

[openstack-dev] Adding 'server_type' field to Baymodel

server_type' also be another field in baymodel? what i understand server-type can be baremetal_node also atleast. please correct me if i am wrong. Regards Vikas Choudhary __ OpenStack Development Mailing List (not for u

[openstack-dev] [Neutron] [DVR] easyOVS -- Smart tool to use/debug Neutron/DVR

Hi, One suggestion from my side is checking nova security groups against iptable rules for each vm.Doing this will ensure that there are no unwanted holes in security (for example, accidental messing up of iptable rules). Thanks -Vikas Choudhary

[openstack-dev] [Magnum] possible values for 'server_type', other tahn 'vm'

rmTemplateDefinition(BaseTemplateDefinition):provides = [{'server_type': 'vm', 'os': 'fedora-atomic', 'coe': 'swarm'},]* os and coe are being stored as attributes of baymodel.Should not 'server

[openstack-dev] (no subject)

is the issue, you need to set correct HOST_IP in localrc. -Vikas Choudhary ___ Hi Stanislaw, Your host with Fedora should have special config file, which will send signal to WaitCondition. For good example please take a look this

[openstack-dev] [Openstack-dev] [Containers] Magnum bay-create is getting stuck at CREATE_IN_PROGRESS

by setting HOST_IP in localrc as public network interface ip of host machine.Then bay creation got completed successfully. Thanks Vikas Choudhary ___ Hi Vikas, Please debug on these lines: - are you able to launch the instance based

[openstack-dev] [neutron] Expected cli behavior when ovs-agent is down

-agent restart binding does not recovers. Thanks & Regars Vikas Choudhary hi Vikas Choudhary, when ovs-agent service recover(ovs-agent process restart), the dhcp port will not re-binding successfully? At 2015-08-22 14:26:08, &q

[openstack-dev] [Containers] Magnum bay-create is getting stuck at CREATE_IN_PROGRESS

I am following https://github.com/openstack/magnum/blob/master/doc/source/dev/dev-quickstart.rst#using-kubernetes to try containers/magnum.After running "magnum bay-create --name k8sbay --baymodel k8sbaymodel --node-count 1" , it keeps showing : root@PRINHYLTPHP0400:/home/devstack/devstack# magnu

[openstack-dev] [neutron] Expected cli behavior when ovs-agent is down

Hi Everybody, I want to discuss on https://bugs.launchpad.net/neutron/+bug/1348589.This is there for more than a year and no discussion i could find on this. *Scenario:* ovs-agent is down and then a network and subnet under this newly created network are created using cli. No error visible to use

[openstack-dev] [ironic] baremetal server boot failing at iSCSI/tgtd

at kernel and ramdisk are you using for the deploy step? Did you download one, or build it with disk-image-builder? cirros is only suitable for the instance image, not the deploy. Regards, -Deva On Jul 29, 2015 5:56 PM, "Vikas Choudhary" http://lists.openstack.org/cgi-bin/mailman/lis

[openstack-dev] [ironic] baremetal server boot failing at iSCSI/tgtd

Hi, I am trying to boot an instance using pxe deployment process.I am using cirros-0.3.4-x86_64-uec image to boot the baremetal server VM.ramdisk and kernel images are being deployed successfully , but at kernel initialization time its getting stuck there.In console logs I can see that tgtd daemon

[openstack-dev] New subscriber:choudharyvika...@gmail.com is my email id.

__ 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