[openstack-dev] [openstack][infra]Including Functional Tests in Coverage

[reedip banerjee]

Hi All,

Has anyone ever experimented with including Functional Tests with
openstack-tox-cover job?
We would like to include Functional tests in the coverage jobs and already
have a dsvm-functional job in place. However,  openstack-tox-cover is , if
I am correct, an infra job which is directly called.

Has anyone tried to include the functional tests and all its pre-requisites
in the cover job? If so, any pointers would be great


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedipb
__
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] [neutron] Port mirroring for SR-IOV VF to VF mirroring

[reedip banerjee]

Wondering if Tap-as-a-Service would play a role here? :)
Related patch : https://review.openstack.org/#/c/584892/1

On Sun, Aug 5, 2018 at 9:57 PM Miguel Lavalle  wrote:

> Hi Forrest,
>
> Please place your name / irc nick next to the topics you propose
>
> Regards
>
>
>
>
> On Fri, Aug 3, 2018 at 8:18 PM, Zhao, Forrest 
> wrote:
>
>> Hi Miguel,
>>
>>
>>
>> Can we put the proposed topics to this PTG etherpad directly?  Or we
>> should first discuss it in weekly Neutron project meeting?
>>
>>
>>
>> Please advise; then we’ll follow the process to propose the PTG topics.
>>
>>
>>
>> Thanks,
>>
>> Forrest
>>
>>
>>
>> *From:* Miguel Lavalle [mailto:mig...@mlavalle.com]
>> *Sent:* Friday, August 3, 2018 11:41 PM
>> *To:* OpenStack Development Mailing List (not for usage questions) <
>> openstack-dev@lists.openstack.org>
>>
>> *Subject:* Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to
>> VF mirroring
>>
>>
>>
>> Forrest, Manjeet,
>>
>>
>>
>> Here you go: https://etherpad.openstack.org/p/neutron-stein-ptg
>>
>>
>>
>> Best regards
>>
>>
>>
>> On Wed, Aug 1, 2018 at 11:49 AM, Bhatia, Manjeet S <
>> manjeet.s.bha...@intel.com> wrote:
>>
>> Hi,
>>
>>
>>
>> Yes, we need to refine spec for sure, once a consensus is reached focus
>> will be on implementation,
>>
>> Here’s implementation patch (WIP)
>> https://review.openstack.org/#/c/584892/ , we can’t really
>>
>> review api part until spec if finalized but, other stuff like config and
>> common issues can
>>
>> still be pointed out and progress can be made until consensus on api is
>> reached. Miguel, I think
>>
>> this will be added to etherpad for PTG discussions as well ?
>>
>>
>>
>> Thanks and Regards !
>>
>> Manjeet
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* Miguel Lavalle [mailto:mig...@mlavalle.com]
>> *Sent:* Tuesday, July 31, 2018 10:26 AM
>> *To:* Zhao, Forrest 
>> *Cc:* OpenStack Development Mailing List <
>> openstack-dev@lists.openstack.org>
>> *Subject:* Re: [openstack-dev] [neutron] Port mirroring for SR-IOV VF to
>> VF mirroring
>>
>>
>>
>> Hi Forrest,
>>
>>
>>
>> Yes, in my email, I was precisely referring to the work around
>> https://review.openstack.org/#/c/574477. Now that we are wrapping up
>> Rocky, I wanted to raise the visibility of this spec. I am glad you
>> noticed. This week we are going to cut our RC-1 and I don't anticipate that
>> we will will have a RC-2 for Rocky. So starting next week, let's go back to
>> the spec and refine it, so we can start implementing in Stein as soon as
>> possible. Depending on how much progress we make in the spec, we may need
>> to schedule a discussion during the PTG in Denver, September 10 - 14, in
>> case face to face time is needed to reach an agreement. I know that Manjeet
>> is going to attend the PTG and he has already talked to me about this spec
>> in the recent past. So maybe Manjeet could be the conduit to represent this
>> spec in Denver, in case we need to talk about it there
>>
>>
>>
>> Best regards
>>
>>
>>
>> Miguel
>>
>>
>>
>> On Tue, Jul 31, 2018 at 4:12 AM, Zhao, Forrest 
>> wrote:
>>
>> Hi Miguel,
>>
>>
>>
>> In your mail “PTL candidacy for the Stein cycle”, it mentioned that “port
>> mirroring for SR-IOV VF to VF mirroring” is within Stein goal.
>>
>>
>>
>> Could you tell where is the place to discuss the design for this feature?
>> Mailing list, IRC channel, weekly meeting or others?
>>
>>
>>
>> I was involved in its spec review at
>> https://review.openstack.org/#/c/574477/; but it has not been updated
>> for a while.
>>
>>
>>
>> Thanks,
>>
>> Forrest
>>
>>
>>
>>
>> __
>> 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
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] Stepping down from core

[reedip banerjee]

Hi Armando,
Its not easy to hear this news.
But all the best of luck to you Armando for your future endeavors.

Best Regards,
Reedip


On Sat, Dec 23, 2017 at 1:38 AM, German Eichberger <
german.eichber...@rackspace.com> wrote:

> Hi,
>
>
>
> Thanks for all the help and support over the years. Both LBaaS (Octavia)
>  and FWaaS wouldn’t be what they are today without your leadership and
> advice –
>
>
>
> All the best + good luck,
>
> German
>
>
>
> *From: *"Armando M." <arma...@gmail.com>
> *Reply-To: *"OpenStack Development Mailing List (not for usage
> questions)" <openstack-dev@lists.openstack.org>
> *Date: *Friday, December 15, 2017 at 8:04 PM
> *To: *"OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> *Subject: *[openstack-dev] [neutron] Stepping down from core
>
>
>
> Hi neutrinos,
>
>
>
> To some of you this email may not come as a surprise.
>
>
>
> During the past few months my upstream community engagements have been
> more and more sporadic. While I tried hard to stay committed and fulfill my
> core responsibilities I feel like I failed to retain the level of quality
> and consistency that I would have liked ever since I stepped down from
> being the Neutron PTL back at the end of Ocata.
>
>
>
> I stated many times when talking to other core developers that being core
> is a duty rather than a privilege, and I personally feel like it's way
> overdue for me to recognize on the mailing list that it's the time that I
> state officially my intention to step down due to other commitments.
>
>
>
> This does not mean that I will disappear tomorrow. I'll continue to be on
> neutron IRC channels, support the neutron team, being the release liasion
> for Queens, participate at meetings, and be open to providing feedback to
> anyone who thinks my opinion is still valuable, especially when dealing
> with the neutron quirks for which I might be (git) blamed :)
>
>
>
> Cheers,
>
> Armando
>
>
>
> ______
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron] Propose Slawek Kaplonski for Neutron core

[reedip banerjee]

Just checked this ... +1 to Slaweq ... he is a real gem to Neutron :)

On Thu, Nov 30, 2017 at 12:51 AM, Miguel Lavalle <mig...@mlavalle.com>
wrote:

> Hi Neutron Team,
>
> I want to nominate Slawek Kaplonski (irc: slaweq) to Neutron core. Slawek
> has been an active contributor to the project since the Mitaka cycle. He
> has been instrumental in the development of the QoS capabilities in
> Neutron, becoming the lead of the sub-team focused on that set of features.
> More recently, he has collaborated in the implementation of OVO and is an
> active participant in the CI sub-team. His number of code reviews during
> the Queens cycle is on par with the leading core members of the team:
> http://stackalytics.com/?module=neutron
>
> In my opinion, his efforts are highly valuable to the team and we will be
> very lucky to have him as a fully voting core.
>
> I will keep this nomination open for a week as customary,
>
> Thank you,
>
> Miguel
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron][fwaas] Proposal to change the time for Firewall-as-a-Service Team Meeting

[reedip banerjee]

Hi All,
Thanks for your votes.
As per the majority votes, https://review.openstack.org/#/c/507172/ was
created and merged successfully.
FWaaS meeting would now be held on Thursday 1400 UTC in the
#openstack-fwaas channel from 5th October.

On 22-Sep-2017 5:50 AM, "Furukawa, Yushiro" <y.furukaw...@jp.fujitsu.com>
wrote:

> Hi,
>
>
>
> I’m sorry I’m late.  I just voted it.
>
>
>
> Thanks,
>
>
>
> ----
>
> Yushiro Furukawa
>
>
>
> *From:* reedip banerjee [mailto:reedi...@gmail.com]
> *Sent:* Tuesday, September 19, 2017 11:54 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* [openstack-dev] [neutron][fwaas] Proposal to change the time
> for Firewall-as-a-Service Team Meeting
>
>
>
> Dear All,
>
> Due to clashes of the Firewal-as-a-Service team meetup with the bi-weekly
> Neutron and Common-Classifier meeting, it was suggested in today's meetup
> to change the timing.
>
>
>
> https://doodle.com/poll/c5rgth6y54bpvncu is the Link to vote for the day
> when the meeting can be held.
>
>
>
> --
>
> Thanks and Regards,
> Reedip Banerjee
>
> IRC: reedip
>
>
>
>
>
>
> __
> 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-dev] [neutron][fwaas] Proposal to change the time for Firewall-as-a-Service Team Meeting

[reedip banerjee]

Dear All,
Due to clashes of the Firewal-as-a-Service team meetup with the bi-weekly
Neutron and Common-Classifier meeting, it was suggested in today's meetup
to change the timing.

https://doodle.com/poll/c5rgth6y54bpvncu is the Link to vote for the day
when the meeting can be held.

-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] - transitioning PTL role to Miguel Lavalle

[reedip banerjee]

Damn :(
Kevin , you have been excellent , and this is a sad, sad news ! I hope you
continue to work with the project you strengthen with your expertise...
Miguel Lavalle , +2 to you :)

On Wed, Sep 13, 2017 at 4:10 AM, Miguel Angel Ajo Pelayo <
majop...@redhat.com> wrote:

> Kevin!, and thank you for all the effort and energy you have put into
> openstack-neutron during the last few years. It's been great to have you on
> the project.
>
> On Mon, Sep 11, 2017 at 5:18 PM, Ihar Hrachyshka <ihrac...@redhat.com>
> wrote:
>
>> It's very sad news for the team, but I hope that Kevin will still be
>> able to contribute, or at least stay in touch. I am sure Miguel will
>> successfully lead the community in Queens and beyond. Thanks to Miguel
>> for stepping in the ring. Thanks to Kevin for his leadership in recent
>> cycles.
>>
>> King is dead, long live the King!
>>
>> Ihar
>>
>> On Fri, Sep 8, 2017 at 8:59 PM, Kevin Benton <ke...@benton.pub> wrote:
>> > Hi everyone,
>> >
>> > Due to a change in my role at my employer, I no longer have time to be
>> the
>> > PTL of Neutron. Effective immediately, I will be transitioning the PTL
>> role
>> > to Miguel Lavalle.
>> >
>> > Miguel is an excellent leader in the community and has experience
>> reviewing
>> > patches as a core, reviewing feature requests and specs as a driver,
>> > implementing cross-project features, handling docs, and on-boarding new
>> > contributors.
>> >
>> > We will make the switch official next week at the PTG with the
>> appropriate
>> > patches to the governance repo.
>> >
>> > If anyone has any concerns with this transition plan, please reach out
>> to
>> > me, Thierry, or Doug Hellmann.
>> >
>> > Cheers,
>> > Kevin Benton
>> >
>> > 
>> __
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.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:unsubscrib
>> e
>> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [openstack][neutron][fwaas] Migration of the Public attribute to Shared in FWaaS v2

[reedip banerjee]

Dear All,

In the meeting for FWaaS held on 21st of March 2017 [1], it was decided
that the "Public" attribute of FWaaS would be changed to "Shared" , keeping
in line with the meaning of the "Shared" attribute in Openstack.

[2] has been logged for the same.Note that this is targetted only for FWaaS
v2 and not for FWaaS v1 , as of now.

[1]
http://eavesdrop.openstack.org/meetings/fwaas/2017/fwaas.2017-03-21-14.00.log.html#l-136
[2] https://bugs.launchpad.net/neutron/+bug/1676922


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] - Neutron team social in Atlanta on Thursday

[reedip banerjee]

+1 from Rajiv Kumar as well :)

On Fri, Feb 24, 2017 at 3:07 AM, Vasudevan, Swaminathan (PNB Roseville) <
swaminathan.vasude...@hpe.com> wrote:

> +1
>
>
>
> *From:* Kevin Benton [mailto:ke...@benton.pub]
> *Sent:* Thursday, February 23, 2017 4:09 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron] - Neutron team social in Atlanta
> on Thursday
>
>
>
> Hi everyone,
>
>
>
> We will meet tonight at Mellow Mushroom at 6PM. It's about a 10-15 minute
> walk from the venue.
>
>
>
> Here is the location:
>
>
>
> https://goo.gl/maps/FAnmVEVEUSE2
>
>
>
> On Feb 23, 2017 13:27, "Duarte Cardoso, Igor" <
> igor.duarte.card...@intel.com> wrote:
>
> +1
>
>
>
> Best regards,
>
> Igor.
>
>
>
> *From:* Vasudevan, Swaminathan (PNB Roseville) [mailto:
> swaminathan.vasude...@hpe.com]
> *Sent:* Friday, February 17, 2017 8:30 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> *Subject:* Re: [openstack-dev] [neutron] - Neutron team social in Atlanta
> on Thursday
>
>
>
> Count me in.
>
>
>
> *From:* Kevin Benton [mailto:ke...@benton.pub <ke...@benton.pub>]
> *Sent:* Friday, February 17, 2017 11:19 AM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [neutron] - Neutron team social in Atlanta on
> Thursday
>
>
>
> Hi all,
>
>
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
> reservation.
>
>
>
> Cheers,
>
> Kevin Benton
>
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron][FWaaS][PTG] FWaaS team gathering Thursday for lunch

[reedip banerjee]

Hi All,
The lunch is in the Grand Ballroom ( if I am correct ) in the Level 1 on
Sheraton.
So lets catch up there

On Wed, Feb 22, 2017 at 8:24 PM, German Eichberger <
german.eichber...@rackspace.com> wrote:

> All,
>
>
>
> The FWaaS team will meet for lunch at the Sheraton tomorrow, Thursday, to
> tlak about Pike priorities (https://etherpad.openstack.org/p/fwaas-pike)
> and prepare for Friday’s Advanced Srrvices session. Ping us on irc if you
> can’t find our table.
>
>
>
> German
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] - Team photo

[reedip banerjee]

+1

On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton <ke...@benton.pub> wrote:

> Hello!
>
> Is everyone free Thursday at 11:20AM (right before lunch break) for 10
> minutes for a group photo?
>
> Cheers,
> Kevin Benton
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] - Neutron team social in Atlanta on Thursday

[reedip banerjee]

+1 :)

On Sat, Feb 18, 2017 at 4:42 AM, MCCASLAND, TREVOR <tm2...@att.com> wrote:

> +1
>
>
>
> *From:* Kevin Benton [mailto:ke...@benton.pub]
> *Sent:* Friday, February 17, 2017 1:19 PM
> *To:* openstack-dev@lists.openstack.org
> *Subject:* [openstack-dev] [neutron] - Neutron team social in Atlanta on
> Thursday
>
>
>
> Hi all,
>
>
>
> I'm organizing a Neutron social event for Thursday evening in Atlanta
> somewhere near the venue for dinner/drinks. If you're interested, please
> reply to this email with a "+1" so I can get a general count for a
> reservation.
>
>
>
> Cheers,
>
> Kevin Benton
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron][taas] IRC Meeting Canceled (week of 2/20/2017)

[reedip banerjee]

Adding to the earlier email, we would be having the next Tap-as-a-Service
meeting on the 1st of March, 2017.

:)

On Wed, Feb 15, 2017 at 12:20 PM, Soichi Shigeta <
shigeta.soi...@jp.fujitsu.com> wrote:

>
>  Hi,
>
> Next week's TaaS IRC meeting is being canceled because of
>   the week of OpenStack PTG.
>
>   Regards,
>   Soichi
>
>
> __
> 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
>



-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] Proposing Abhishek Raut as neutronclient core

[reedip banerjee]

Congrats Abhishek ...

On Fri, Dec 16, 2016 at 6:42 AM, Abhishek Raut <ra...@vmware.com> wrote:

> Thank you!
>
> From: "Armando M." <arma...@gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, December 15, 2016 at 2:57 PM
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [neutron] Proposing Abhishek Raut as
> neutronclient core
>
>
>
> On 15 December 2016 at 09:50, Akihiro Motoki <amot...@gmail.com> wrote:
>
>> +1
>>
>
> Welcome to the team Abhishek!
>
>
>>
>> 2016-12-14 10:22 GMT+09:00 Armando M. <arma...@gmail.com>:
>>
>>> Hi folks,
>>>
>>> Abhishek Raut's recent involvement in OSC and python-neutronclient has
>>> helped moving a few efforts along in the right direction. I would like to
>>> suggest we double down on core firepower for the neutronclient repo
>>> alongside Akihiro [1].
>>>
>>> This not only will help speed up our transition to OSC CLI, but also
>>> improve the number of folks who can effectively liasion with the OSC team,
>>> and look after the needs of neutron's client repo.
>>>
>>> Many thanks,
>>> Armando
>>>
>>> [1] https://review.openstack.org/#/c/410485/
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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:unsubscrib
>> e
>> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

[reedip banerjee]

+1 for both Ryan and Nate :)

On Fri, Dec 16, 2016 at 10:03 AM, Vikram Choudhary <viks...@gmail.com>
wrote:

> +1 for Ryan!
>
> On Dec 16, 2016 7:23 AM, "Sridar Kandaswamy (skandasw)" <
> skand...@cisco.com> wrote:
>
>> +1. From the neutron-fwaas perspective, Nate has been instrumental in
>> driving our integration with neutron on the agent extension framework,
>> neutron-lib as well as on CI.
>>
>> Thanks
>>
>> Sridar
>>
>> From: Kevin Benton <ke...@benton.pub>
>> Reply-To: OpenStack List <openstack-dev@lists.openstack.org>
>> Date: Thursday, December 15, 2016 at 5:00 PM
>> To: OpenStack List <openstack-dev@lists.openstack.org>
>> Subject: Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate
>> Johnston as service LTs
>>
>> +1
>>
>> On Dec 15, 2016 19:03, "Armando M." <arma...@gmail.com> wrote:
>>
>>> Hi neutrinos,
>>>
>>> I would like to propose Ryan and Nate as the go-to fellows for
>>> service-related patches.
>>>
>>> Both are core in their repos of focus, namely neutron-dynamic-routing
>>> and neutron-fwaas, and have a good understanding of the service framework,
>>> the agent framework and other bits and pieces. At this point, entrusting
>>> them with the responsibility is almost a formality.
>>>
>>> Cheers,
>>> Armando
>>>
>>> [1] https://review.openstack.org/#/c/411536/
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.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:unsubscrib
>> e
>> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

[reedip banerjee]

Hey Assaf,
It was great to have you as a core member and we still learn a lot
from.your valuable blog on networking.

All the best of luck for your future endeavors

On Nov 29, 2016 00:35, "Vasudevan, Swaminathan (PNB Roseville)" <
swaminathan.vasude...@hpe.com> wrote:

> Hi Assaf,
> Sorry to hear that you are stepping down. Thanks for your contribution to
> neutron and making the test suite more stable.
> Wish you all success in your current job.
>
> Thanks
> Swami
>
> -Original Message-
> From: Assaf Muller [mailto:as...@redhat.com]
> Sent: Monday, November 28, 2016 10:59 AM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [neutron] Stepping down as testing lieutenant and
> from the core & drivers teams
>
> Hi all,
>
> For the past few months I've been gaining more responsibilities within Red
> Hat. I have less time to dedicate to personal contribution and it's had a
> considerable tole on my ability to perform my duties upstream to the degree
> of effectiveness I am satisfied with. To that end, I've decided that the
> right thing to do is to hand over my testing lieutenant responsibilities to
> Jakub Libosvar, and to step down from the core and drivers team.
>
> This is a bitter sweet moment. I'm enormously proud to see the progress
> Neutron as a platform, community and as a reference implementation have
> made over the last 3 years and I'm thrilled to have taken part in that.
> It's grown from an experiment to a ubiquitous OpenStack project with a
> proven, robust and scalable batteries-included implementation used at the
> largest retail, insurance, banking, web and telco (And more!) companies in
> the world.
> My focus will remain on OpenStack networking but my contributions will be
> indirect through my amazing team members. The people leading Quantum when I
> joined are nearly all gone and luckily we've seen a continuous influx of
> fresh talent ready to take over leadership responsibilities. I'm confident
> the wheel will keep on spinning and the project will continue stepping down
> the right path.
>
> I'll still be on IRC and I'll be working over the upcoming couple of weeks
> to hand off any specific tasks I had going on. Have fun folks.
>
> __
> 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] [neutron] stable/newton 'broken'

[reedip banerjee]

enstack/vmware-nsx/commit/a951f5f92
>> 99ffdce268c54dc427a71706b8e41da
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_vmware-2Dnsx_commit_a951f5f9299ffdce268c54dc427a71706b8e41da=DgMFaQ=uilaK90D4TOVoH58JNXRgQ=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw=9RMdQBJlmqlbq0DHIHP9NTT4ot9qb0nfNG5qMMfoE2o=IjsdHWFgL__ygsTjKpo2YJsfuaX6AIuy4Jn82vkfZQg=>
>>
>>
>>
>>
>> --
>> Thierry Carrez (ttx)
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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:unsubscrib
>> e
>> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron] Stepping down from core

[reedip banerjee]

Hi Carl,
It was great working with you..
Wishing you the best of luck for your future endeavours

On Mon, Nov 21, 2016 at 3:56 PM, John Davidge <john.davi...@rackspace.com>
wrote:

> It’s been a pleasure to work with you these past few years, Carl. I wish
> you all the best in whatever’s next for you. Hopefully we’ll meet again
> soon in the not so distant future.
>
> There will forever be a Carl-shaped hole in our codebase.
>
> John
>
> From: Carl Baldwin <c...@ecbaldwin.net>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, November 17, 2016 at 6:42 PM
> To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org>
> Subject: [openstack-dev] [Neutron] Stepping down from core
>
> Neutron (and Openstack),
>
> It is with regret that I report that my work situation has changed such
> that I'm not able to keep up with my duties as a Neutron core reviewer, L3
> lieutenant, and drivers team member. My participation has dropped off
> considerably since Newton was released and I think it is fair to step down
> and leave an opening for others to fill. There is no shortage of talent in
> Neutron and Openstack and I know I'm leaving it in good hands.
>
> I will be more than happy to come back to full participation in Openstack
> and Neutron in the future if things change again in that direction. This is
> a great community and I've had a great time participating and learning with
> you all.
>
> Well, I don't want to drag this out. I will still be around on IRC and
> will be happy to help out where I am able. Feel free to ping me.
>
> Carl
>
> --
> Rackspace Limited is a company registered in England & Wales (company
> registered number 03897010) whose registered office is at 5 Millington
> Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy
> can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail
> message may contain confidential or privileged information intended for the
> recipient. Any dissemination, distribution or copying of the enclosed
> material is prohibited. If you receive this transmission in error, please
> notify us immediately by e-mail at ab...@rackspace.com and delete the
> original message. Your cooperation is appreciated.
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron] Neutron team social event in Barcelona

[reedip banerjee]

-1, need to cancel, will meet you guys tomorrow :)

On Oct 27, 2016 14:50, "Andreas Scheuring" 
wrote:

> -1 I'm sorry, but I also need to cancel.
>
> Andreas
>
> On 10/26/2016 08:10 PM, John McDowall wrote:
>
> -1
>
>
>
> Unfortunately, a business meeting has come up
>
>
>
> Regards
>
>
>
> John
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://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] [Neutron][networking-sfc] OpenStack Summit Barcelona: networking-sfc project team lunch meetup

[reedip banerjee]

Hi Cathy,
Sorry, we missed the discussion today.
TaaS team would also like to have a discussion for the SFC, and we are
present here in Barcelona.
Can we meet up tomorrow in the AC hotel for Lunch?

On Oct 25, 2016 23:56, "Cathy Zhang"  wrote:

> Hi Stephen,
>
>
>
> Sorry to miss you. It will be a social get together at lunch, no specific
> agenda, open topic. We can update you and others for any technical
> discussion if any in  the next IRC meeting.
>
>
>
> Cathy
>
>
>
> *From:* Stephen Wong [mailto:stephen.kf.w...@gmail.com]
> *Sent:* Tuesday, October 25, 2016 8:49 PM
> *To:* Cathy Zhang
> *Cc:* OpenStack Development Mailing List
> *Subject:* Re: [openstack-dev] [Neutron][networking-sfc] OpenStack Summit
> Barcelona: networking-sfc project team lunch meetup
>
>
>
> Hi Cathy,
>
>
>
> Sorry, I won't be attending the summit. Will there be an etherpad to
> capture what is going to be discussed regarding networking-sfc during the
> summit? If so, please post the link.
>
>
>
> Thanks,
>
> - Stephen
>
>
>
> On Tue, Oct 25, 2016 at 6:38 AM, Cathy Zhang 
> wrote:
>
> Let’s meet for lunch at the AC Buffet lunch room (not the CCIN buffet
> lunch area) at 1pm Wednesday.
>
> Anyone interested in service function chaining solution is welcomed to
> join.
>
>
>
> Thanks,
>
> Cathy
>
>
>
> __
> 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] [Neutron] Neutron team social event in Barcelona

[reedip banerjee]

+1
Great idea Miguel :)

On Oct 15, 2016 15:00, "Janki Chhatbar"  wrote:

> +1
>
> On 15-Oct-2016 2:49 pm, "Ihar Hrachyshka"  wrote:
>
>> Miguel Lavalle  wrote:
>>
>> Dear Neutrinos,
>>>
>>> I am organizing a social event for the team on Thursday 27th at 19:30.
>>> After doing some Google research, I am proposing Raco de la Vila, which is
>>> located in Poblenou: http://www.racodelavila.com/en/index.htm. The menu
>>> is here: http://www.racodelavila.com/en/carta-racodelavila.htm
>>>
>>> It is easy to get there by subway from the Summit venue:
>>> https://goo.gl/maps/HjaTEcBbDUR2. I made a reservation for 25 people
>>> under 'Neutron' or "Miguel Lavalle". Please confirm your attendance so we
>>> can get a final count.
>>>
>>
>> +1. (I wonder if 25 is enough. I remember Tokyo party was especially
>> crowded.)
>>
>> Ihar
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> 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

[openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

[reedip banerjee]

Dear Neutron Core members,

I have a query regarding the procedure for inclusion in the Neutron Stadium.
I wanted to know if a project can apply for Big Tent and Neutron Stadium
together ( means can a project be accepted in the Neutron Stadium and as a
result into the Big Tent )

I was checking out the checklist in  [1], and IMO , I think that we need to
conform to the checklist to be added to the Neutron Stadium ( along with
the other requirements  like keeping in sync with the core neutron concepts)

But IIUC, certain items in the checklist would be completed if a project is
already included in the Big Tent.

So my doubt is ,should a project apply for the Big Tent first, and after
inclusion, apply for Neutron Stadium ? Or can a project be integrated to
Neutron Stadium and Big Tent simultaneously ( I am a bit sceptical about
this though)?


[1]
http://docs.openstack.org/developer/neutron/stadium/governance.html#checklist
-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron][LBaaS v2]Quota Update for LBaaS v2 Members

[reedip banerjee]

Hi All,

Currently OpenstackClient and NeutronClient supports updating the quota for
LBaaS v2 members.
However, the quota API does not seem to support it.[1]

I would just like to get this information cleared whether we actually allow
updating the quotas for LBaaSv2 Members??

[1]: https://bugs.launchpad.net/python-openstackclient/+bug/1624097

-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [openstack][neutron][stable/mitaka] Regarding lb_method required for creating pools

[reedip banerjee]

Hi There,
The bug https://bugs.launchpad.net/heat/+bug/1616094 was created for
Stable/Mitaka stating that lb_method is required for creating a pool.
I just wanted to know, if it is possible to have a patch propagated to
stable/mitaka for fixing this ?




-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] [qos] gathering Friday 9:30

[reedip banerjee]

Yup,+1
On Apr 29, 2016 04:19, "Shaughnessy, David" 
wrote:

> Sounds good, +1.
>
>
>
> *From:* Miguel Angel Ajo Pelayo [mailto:majop...@redhat.com]
> *Sent:* Thursday, April 28, 2016 11:03 PM
> *To:* OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>; Nate Johnston <
> nate_johns...@cable.comcast.com>; Margaret Frances <
> margaret_fran...@cable.comcast.com>; Shaughnessy, David <
> david.shaughne...@intel.com>; irenab@gmail.com; Moshe Levi <
> mosh...@mellanox.com>; reedi...@gmail.com
> *Subject:* [neutron] [qos] gathering Friday 9:30
>
>
>
> Does governors ballroom in Hilton sound ok?
>
> We can move to somewhere else if necessary.
>
> --
> Intel Research and Development Ireland Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
__
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] [neutron] OSC transition

[reedip banerjee]

>From my point of view, I would suggest discussing it once during the
NeutronClient session/OSC sessions on Thursday or once in the design meetup
on Friday. I feel we can see at it once more.
Currently I feel that the definition which is mentioned in the github is
not completely clear.

For the projects which already use clientcommand extension, the
implementation needs to be done in the project repo.
For "CORE" Resources, the implementation needs to be done in python-osc.
However, for the new resources/projects,  the implementation needs to be
clear because IMHO there is currently no clear definition as to which
resources should implement clientcommandextension( which means implement
the client code in the own repo) vs which resources can be added as simple
extensions to NeutronClient(I.e. which can reside in the NeutronClient
repo). However this is IMO, and if you have any guidelines which tells a
developer if a project needs to be a clientcommand extension for
NeutronClient ( or not) , please share the same.
On Apr 26, 2016 21:10, "Vikram Choudhary"  wrote:

+1 for keeping neutron-dynamic-routing CLI's in neutronclient repo like
other *aaS services.

Thanks
Vikram

On Tue, Apr 26, 2016 at 7:47 PM, Richard Theis  wrote:

> Hi,
>
> The latest devref [1] would place it in python-neutronclient as Henry
> noted. But stay tuned for results from the summit session.
>
> [1]
> https://github.com/openstack/python-neutronclient/blob/master/doc/source/devref/transition_to_osc.rst
>
> - Richard
>
>
> "Na Zhu"  wrote on 04/26/2016 08:29:21 AM:
>
> > From: "Na Zhu" 
> > To: hen...@gessau.net
> > Cc: "OpenStack Development Mailing List \(not for usage questions\)"
> > 
> > Date: 04/26/2016 08:34 AM
> > Subject: Re: [openstack-dev] [neutron] OSC transition
> >
> > Hi Henry,
> >
> > Thanks your information, why you think neutron-dynamic-routing CLI
> > should live in python-neutronclient?
> > From this link http://docs.openstack.org/developer/python-
> > neutronclient/devref/transition_to_osc.htmlsection "Where does my CLI
> belong?
> > ", *aas CLI belongs to their own project, not project python-
> > neutronclient. BGP is also service like *aas, so I think BGP CLIs
> > should live in neutron-dynamic-routing, or a separate repo named
> > python-*client. Pls correct me if I am wrong, thanks.
> >
> >
> >
> > Regards,
> > Juno Zhu
> > IBM China Development Labs (CDL) Cloud IaaS Lab
> > Email: na...@cn.ibm.com
> > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong
> > New District, Shanghai, China (201203)
> >
> >
> >
> > From:Henry Gessau 
> > To:"OpenStack Development Mailing List (not for usage
> > questions)" 
> > Date:2016/04/26 21:09
> > Subject:Re: [openstack-dev] [neutron] OSC transition
> >
> >
> >
> > Adding the [neutron] tag.
> >
> > I believe that the OSC extension for neutron-dynamic-routing should live
> in
> > the python-neutronclient repo. Keep in touch with Richard Theis as he is
> the
> > one leading the transition to OSC. He is rtheis on IRC.
> >
> > See:
> >
> http://lists.openstack.org/pipermail/openstack-dev/2016-April/093139.html
>
> > https://review.openstack.org/309587
> >
> >
> > Na Zhu  wrote:
> > > Dear All,
> > >
> > >
> > > I have a question about OSC transition, recently, the community
> approves
> > > moving bgp out of neutron, as a service like other *aas. The BGP
> > CLIs need be
> > > removed from neutronclient. Because of OSC transition, I can not
> > just move the
> > > BGP CLIs code from python-neutronclient repo to neutron-dynamic-
> > routing repo.
> > > I have to refactor the code and do transition to OSC plugin system.
> > >
> > > From the
> > > link _http://docs.openstack.org/developer/python-openstackclient/
> > plugins.html_, the
> > > client has a separate repo, take designate as example, the CLI repo is
> > > python-designateclient, the project repo is designate. So for BGP,
> should I
> > > create a repo for CLI, or leverage project repo
> neutron-dynamic-routing?
> > >
> > >
> > >
> > >
> > > Regards,
> > > Juno Zhu
> > > IBM China Development Labs (CDL) Cloud IaaS Lab
> > > Email: na...@cn.ibm.com
> > > 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech Park, Pudong New
> > > District, Shanghai, China (201203)
> > >
> > >
> > >
> __
> > > 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:
> 

Re: [openstack-dev] [neutron] Social at the summit

[reedip banerjee]

@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
> >
> >
> > __
> >  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
>



-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron] Neutron client and plan to transition to OpenStack client

[reedip banerjee]

Hi Richard,
Thanks for the information :)

Was waiting for it.



On Sat, Apr 23, 2016 at 3:27 AM, Armando M. <arma...@gmail.com> wrote:

>
>
> On 22 April 2016 at 13:58, Richard Theis <rth...@us.ibm.com> wrote:
>
>> FYI: I've pushed a series of WIP patch sets [1], [2] and [3] to enable
>> python-neutronclient OSC plugins. I've used "openstack network agent list"
>> as the initial OSC plugin command example.  Hopefully these will help
>> during the discussions at the summit.
>>
>> [1] https://review.openstack.org/#/c/309515/
>> [2] https://review.openstack.org/#/c/309530/
>> [3] https://review.openstack.org/#/c/309587/
>>
>
> Super! Thanks for your help Richard!
>
> Cheers,
> Armando
>
>
>>
>> "Armando M." <arma...@gmail.com> wrote on 04/22/2016 12:19:45 PM:
>>
>> > From: "Armando M." <arma...@gmail.com>
>> > To: "OpenStack Development Mailing List (not for usage questions)"
>> > <openstack-dev@lists.openstack.org>
>> > Date: 04/22/2016 12:22 PM
>> > Subject: [openstack-dev] [Neutron] Neutron client and plan to
>> > transition to OpenStack client
>> >
>> > Hi Neutrinos,
>> >
>> > During the Mitaka release the team sat together to figure out a plan
>> > to embrace the OpenStack client and supplant the neutron CLI tool.
>> >
>> > Please note that this does not mean we will get rid of the
>> > openstack-neutronclient repo. In fact we still keep python client
>> > bindings and keep the development for features that cannot easily go
>> > in the OSC client (like the high level services).
>> >
>> > We did put together a transition plan in pace [1], but we're
>> > revising it slightly and we'll continue the discussion at the summit.
>> >
>> > If you are interested in this topic, are willing to help with the
>> > transition or have patches currently targeting the client and are
>> > unclear on what to do, please stay tuned. We'll report back after the
>> summit.
>> >
>> > Armando
>> >
>> > [1] http://docs.openstack.org/developer/python-neutronclient/devref/
>> > transition_to_osc.html
>> > [2]
>> https://www.openstack.org/summit/austin-2016/summit-schedule/events/9096
>>
>> >
>> __
>> > 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [osc] Meeting time preferences for OSC team

[reedip banerjee]

E1 and O3 work for me as well ,
Can someone please submit the patch for the timing change. Atleast voting
can then be done directly on the Patch than on the email , would have a
better representation :)
(Or I can take the initiative if everyone passes it :} )

On Fri, Apr 15, 2016 at 7:59 AM, Sheel Rana Insaan <ranasheel2...@gmail.com>
wrote:

> Dear Tang,
>
> Yes, I am ok with it.
>
> Best Regards,
> Sheel Rana
> On Apr 15, 2016 6:59 AM, "Tang Chen" <chen.t...@easystack.cn> wrote:
>
>> Hi all,
>>
>> In yesterday's meeting, Dean, Richard and I have discussed the meeting
>> time issue.
>> The following two options work for us.
>>
>> E.1 Every two weeks (on even weeks) on Thursday at 1300 UTC in
>>
>> O.3 Every two weeks (on odd/even weeks) on Thursday at 1900 UTC in
>>
>>
>> Sheel, are you OK with these two options ?
>>
>> Thanks. :)
>>
>> __
>> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron] Proposing Hirofumi Ichihara to Neutron Core Reviewer Team

[reedip banerjee]

Congratulations Hirofumi :)

On Fri, Apr 15, 2016 at 8:52 AM, Takashi Yamamoto <yamam...@midokura.com>
wrote:

> welcome, hirofumi!
>
> On Fri, Apr 15, 2016 at 11:40 AM, Akihiro Motoki <amot...@gmail.com>
> wrote:
> > It's been over a week.
> > I'd like to welcome Hirofumi to the neutron core reviewer team!
> >
> > Akihiro
> >
> > 2016-04-08 13:34 GMT+09:00 Akihiro Motoki <amot...@gmail.com>:
> >> Hi Neutrinos,
> >>
> >> As the API Lieutenant of Neutron team,
> >> I would like to propose Hirofumi Ichihara (irc: hichihara) as a member
> of
> >> Neutron core reviewer team mainly focuing on the API/DB area.
> >>
> >> Hirofumi has been contributing neutron actively in the recent two
> >> releases constantly.
> >> He was involved in key features in API/DB areas in Mitaka such as
> >> tagging support and network availability zones.
> >> I believe his knowledge and involvement will be great addition to our
> team.
> >> He have been reviewing constantly [1] and I expect he continue to work
> >> for Newton or later.
> >>
> >> Existing API/DB core reviews (and other Neutron core reviewers),
> >> please vote +1/-1 for the addition of Hirofumi to the team.
> >>
> >> Thanks!
> >> Akihiro
> >>
> >>
> >> [1] http://stackalytics.com/report/contribution/neutron/90
> >
> >
> __
> > 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
>



-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

[reedip banerjee]

Speaking on behalf of Tap-as-a-Service members, we would also be very much
interested in the following initiative :)

On Fri, Apr 15, 2016 at 5:14 AM, Ihar Hrachyshka <ihrac...@redhat.com>
wrote:

> Cathy Zhang <cathy.h.zh...@huawei.com> wrote:
>
>
>> I think there is no formal spec or anything, just some emails around
>> there.
>>
>> That said, I don’t follow why it’s a requirement for SFC to switch to l2
>> agent extension mechanism. Even today, with SFC maintaining its own agent,
>> there are no clear guarantees for flow priorities that would avoid all
>> possible conflicts.
>>
>> Cathy> There is no requirement for SFC to switch. My understanding is
>> that current L2 agent extension does not solve the conflicting entry issue
>> if two features inject the same priority table entry. I think this new L2
>> agent effort is try to come up with a mechanism to resolve this issue. Of
>> course if each feature( SFC or Qos) uses its own agent, then there is no
>> coordination and no way to avoid conflicts.
>>
>
> Sorry, I probably used misleading wording. I meant, why do we consider the
> semantic flow management support in l2 agent extension framework a
> *prerequisite* for SFC to switch to l2 agent extensions? The existing
> framework should already allow SFC to achieve what you have in the
> subproject tree implemented as a separate agent (essentially a fork of OVS
> agent). It will also set SFC to use standard extension mechanisms instead
> of hacky inheritance from OVS agent classes. So even without the strict
> semantic flow management, there is benefit for the subproject.
>
> With that in mind, I would split this job into 3 pieces:
> * first, adopt l2 agent extension mechanism for SFC functionality
> (dropping custom agent);
> * then, work on semantic flow management support in OVS agent API class
> [1];
> * once the feature emerges, switch SFC l2 agent extension to the new
> framework to manage SFC flows.
>
> I would at least prioritize the first point and target it to Newton-1.
> Other bullet points may take significant time to bake.
>
> [1]
> https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_agent_extension_api.py
>
>
> Ihar
>
> __
> 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
>



-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [designate][osc] new sub commands - how should they be named?

[reedip banerjee]

Hi Graham,
Service is somewhat a pretty common word and would have been used by
several components. But the distinguishing point between Keystone,
Designate, Nova et.al . would be the component ( in this case , dns) to
which the subcommand belongs to.

Also, the below commands make more sense.
>openstack dns service list
>openstack dns service show


You can continue with these options IMHO.



On Wed, Apr 6, 2016 at 8:23 PM, Morgan Fainberg <morgan.fainb...@gmail.com>
wrote:

>
>
> On Wed, Apr 6, 2016 at 7:44 AM, Sheel Rana Insaan <ranasheel2...@gmail.com
> > wrote:
>
>> Hey Graham,
>>
>> I just added service for block storage, we have named these
>> openstack volume service list/enable/disable.
>>
>> Same protocol is used for nova as well previosly.
>>
>> Hope this will help.
>>
>> Regards,
>> Sheel Rana
>> On Apr 6, 2016 7:54 PM, "Hayes, Graham" <graham.ha...@hpe.com> wrote:
>>
>>> On 06/04/2016 15:20, Qiming Teng wrote:
>>> > On Wed, Apr 06, 2016 at 01:59:29PM +, Hayes, Graham wrote:
>>> >> Designate is adding support for viewing the status of the various
>>> >> services that are running.
>>> >>
>>> >> We have added support to our openstack client plugin, but were looking
>>> >> for guidance / advices on what the actual commands should be.
>>> >>
>>> >> We have implemented it in [1] as "dns service list" and
>>> >> "dns service show" - but this is name-spacing the command.
>>> > do you mean?
>>> >
>>> > openstack dns service list
>>> > openstack dns service show
>>>
>>> sorry, yes - I just included the sub commands.
>>>
>>> >
>>> >> Is there an alternative? "service" is already taken by keystone, and
>>> if
>>> >> we take "service-status" (or other generic term) it will most likely
>>> >> conflict when nova / cinder / heat / others add support of their
>>> service
>>> >> listings to OSC.
>>> >>
>>> >> What is the protocol here? First to grab it wins?
>>> >>
>>> >> Thanks
>>> >>
>>> >> - Graham
>>> >>
>>> >> 1 - https://review.openstack.org/284103
>>> >>
>>>
>>
> I think the offered options make a lot of sense:
>
> openstack dns service list
> openstack dns service show
>
>
> I would encourage continued use of the namespacing like this for future
> subcommands where possible (as it seems cinder and nova are already on
> track to do).
>
> --Morgan
>
>
> __
> 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
>
>


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] Meeting time preferences for OSC team

[reedip banerjee]

Possible options:

A)
1. even week: *E.1*

2. odd week: *O.3*

B)

1. even week: *E.4*

2. odd week: *O.3*

>Dear All,

>This is regarding deciding meeting time for OSC team to facilitate
>appropriate time for APAC guys.
>We are planning to have meeting on alternate weeks for this purpose.

>Some of the suggestions are:

>*E.1* Every two weeks (on even weeks) on Thursday at 1300 UTC in
>#openstack-meeting (IRC webclient)
>*E.2* Every two weeks (on even weeks) on Tuesday at 1500 UTC in
>#openstack-meeting (IRC webclient)
>*E.3* Every two weeks (on even weeks) on Friday at 1500 UTC in
>#openstack-meeting-4 (IRC webclient)
>*E.4* Every two weeks (on even weeks) on Thursday at 1600 UTC in
>#openstack-meeting (IRC webclient)


>*O.1* Every two weeks (on odd weeks) on Tuesday at 1400 UTC in
>#openstack-meeting-4 (IRC webclient)
>*O.2* Every two weeks (on odd weeks) on Wednesday at 1400 UTC in
>#openstack-meeting-3 (IRC webclient)
>*O.3* Every two weeks (on odd/even weeks) on Thursday at 1900 UTC in
>#openstack-meeting (IRC webclient)  -- our regular meeting time

>Kindly share your preffered time(select only one for each even/odd weeks
>and share in your response in below format).

>1. even week: *E.1/E.2/E.3/E.4*/  ?
>2. odd week:  *O.1/O.2/O.3*  ?

>(response sample):
>1. even week: *E.2*
>2. odd week: *O.3*

>Best Regards,
>Sheel Rana


Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron]: Neutron naming legal issues

[reedip banerjee]

Wont that change Neutrinos to Quantum-states /Quantumites.
And not to ponder too much but [1] is just for reference, in case we would
like to avoid any future issues

[1] : http://www.quantum.com/terms/index.aspx


On Fri, Apr 1, 2016 at 11:36 AM, Armando M. <arma...@gmail.com> wrote:

>
>
> On 31 March 2016 at 22:46, Jimmy Akin <jimmya...@rambler.ru> wrote:
>
>>
>> Dear Neutrinos,
>>
>> We've been following the project for quite some time.
>> To our satisfaction the project seems to have done well; the base line of
>> features that were available to the networking component of OpenStack
>> (then nova-network) has grown quite a bit and seem to have gained a
>> successful momentum with the communities, both development and
>> operators.
>>
>> However, Neutron appears to be a trademarked name [1], and after
>> thoroughly discussing the issue with our and Marvel' legal departments
>> both sides have reached the conclusion that a naming scheme is an
>> obligatory amendment and unfortunately is the only viable option.
>>
>> An obvious resolution to this issue is reverting the old "Quantum" name
>> back.
>> However, this is subject to change and review from the PTL and as such,
>> we'll shortly propose a relevant change to the review system.
>> We anticipate the review process to be be swift, to avoid further legal
>> implications.
>>
>
> To be perfectly honest with you, I always liked the 'Quantum' name more.
>
> With the ongoing release cycle called 'Newton', my hatred for the
> 'Neutron' name has increased, since I keep mispronouncing with 'Neutron'
> and vice versa.
>
> Therefore I can't express my gratitude enough for this well timed
> proposal. You got my +2, though you got get behind governance change [1]
> first.
>
> Happy hacking!
> Armando,
> Quantum (formerly known as Newton) PTL
>
> [1] https://review.openstack.org/#/c/300274/
>
>
>> Sincerely,
>> Jimmy J. Akin,
>> CIO,John F. Kennedy Space Center.
>>
>> [1] https://en.wikipedia.org/wiki/Neutron_(Marvel_Comics)
>>
>>
>> __
>> 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
>
> --
Thanks and Regards,
Reedip Banerjee
IRC: reedip
One of the small time contributors in Quantum(?)/Neutron(?)
__
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] [neutron][taas] Asynchronous TaaS APIs

[reedip banerjee]

Hi Anil,

>I think we should adopt an asynchronous model, where we maintain the state for 
>>tap-service and tap-flow objects. Valid states could be "created", 
>"create->pending" and "failed." In addition, we will need a suitable mechanism 
>to have >the plugin extract the current state from the agent/driver and 
>provide it to >the end-user.

I think we may also need Pending-Update, if there is any focus of
updating a tap-flow/tap-service in the future.

But yes, such states should exist as most of the processing should not
be presented to the user ( i.e. User should not wait for a CLI/UI
function to complete), specially if a lot of processing is required.

>For the former case,subsequent queries of the object's state will indicate if 
>the operation has completed, is still pending or has failed.

Instead of polling, a callback can act as an interrupt and inform the
frontend about Success/Failure of a job.


-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Neutron][python-neutronclient] Adding new options to the existing Neutron CLIs

[reedip banerjee]

Dear All Neutron Developers and Reviewers,

I have a query/concern related to the parsing of options in
python-neutronclient.
I would like to bring this up, as it "may" also impact the transition of
the CLIs to the openstack client as well.

NeutronClient is pretty special in its behavior, and has one pretty
powerful feature of parsing extra options. This feature states that, if the
CLI does not support an option but the API does, and the user passes a
value for this option, then the "unsupported" CLI option is parsed , and
forwarded to the Neutron Server for processing.

Example:
Currently "neutron net-create" does not support --router:external. If you
see the output of "neutron net-create -h" you would not find
"--router-external". However, this option is supported in the API since
Juno [2]. So therefore , if a user executes the following CLI
*" neutron net-create TestNetwork --router-external" *

then [1] would be observed as an output.

Now the query/concern comes next
Any option which is not supported by the CLI is open to the above parsing.
Therefore , for net-create and net-update, all the following are possible:


*neutron net-create --router:external=True TESTNetwork --(A)*
*neutron net-create --router:external TESTNetwork  --(B)*
*neutron net-create **TESTNetwork **--router:external **--(C)*
*neutron net-create **TESTNetwork **--router:external=True **--(D)*
*neutron net-create **TESTNetwork **--router:external True **--(E)*

However, user is not aware of the --router:external option because it is
not visible in the HELP section ( this is true for other CLI options as
well).

In order to demonstrate these options to the User, we have to update
add_known_arguments function to display them. And once they are known to
the CLI, the parsing changes, and some of the options from (A) to (E) may
not be supported ( Please see [3] for an ongoing, though now dormant,
discussion ).

Note that this discussion is not limited only to net-create, but possibly
other CLIs as well which do not completely expose the Options which the API
can support.I am , however, taking the* net-create* example as a case-study.

I would like to know how we can move forward in this regards:

-- Should NeutronClient continue to support all options from (A) to (E),
but deprecate some of them in Openstack Client?

-- Should we deprecate them in NeutronClient itself, so that the users are
comfortable with the options when the migration to Openstack Client occurs?

-- Any other suggestions

[1]: http://paste.openstack.org/show/491032/

[2]:
http://docs.openstack.org/juno/install-guide/install/apt/content/neutron_initial-external-network.html
[3]: https://review.openstack.org/#/c/137279/

-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron][TaaS] Possible points to be considered for TaaS Spec

[reedip banerjee]

While reading up the specs in [1] and [2], there are certain things which
we may need to discuss before proceeding forward

a) Reference point for Ingress/Egress traffic:
There may be some confusion related to how we are labelling
Ingress and Egress ( is it with respect to a VM, with a switch ,
or any other entity).
As we are looking from "Inside the VM" and not from "Inside the Network",
that needs to be made clear.

b) How to perceive TaaS:
In the section "Proposed Changes" Taas has been compared with a Core Neutron
Plugin ( L3-Router) and a plugin which has emerged out of Neutron ( Neutron
LBaaS).
This might cause confusion to the reviewers. It would be better that we
decide
how we would like to demonstrate TaaS:
- Is it a plugin which can be integrated with the Neutron Core
- Or is it an extension of the Core Neutron Services which can be used by
selected users

Based on the decision, we can modify the explanation to make the spec a bit
more streamed.

c) Device Owner for TaaS:
- If Tap Service creates a "destination" port, the port would have a device
owner
of the format of "network:tap"
- If the "destination" port is now connected to a VM and the VM is booted
up, nova
changes the owner to "compute:nova"

# Is there any impact of the change of the device_owner
# If there is an impact, should there be a change in nova so that the
device_owner is not modified
# When in the future, TaaS supports user providing an "already created
port" should the device owner
be checked and modified?

d) Outcome of Deleting the VM where TaaS operates
Following might be added to the Spec:

1. Deletion of the VM (and port attched to it) from which we were mirroring
(source of the mirror):
In this case we would do a cascade delete of the 'Tap_Flow' instances that
were associated with the port that was deleted.

2. Deletion of the VM (and port attched to it) to which we were mirroring
(Destination of the mirror):
In this case we would do a cascade delete of the 'Tap_Service' instance
that was associated with the port that was deleted.

e) Making the API independent of OpenVSwitch
As per our last discussion [3], it is better that w esplit our
implementation for TaaS,
so that
 # the focus is not limited to OpenVSwitch, which may be a point of concern
during review
 # allow other vendors to create thier own pluggable implementation

f) Choice of Tapping before/after Sec Groups

Security Groups can filter a lot , and implementing TaaS before or after
the SG
can impact the overall monitoring.
As referenced in [1], we can provide this option as a future course of
work, and
in the meanwhile specify the option which we are working upon  ( Before or
After)
in the spec, to make it clear.




[1]:https://review.openstack.org/#/c/96149/8/specs/juno/tap-as-a-service.rst
[2]:
https://review.openstack.org/#/c/256210/5/specs/mitaka/tap-as-a-service.rst
[3]:
http://eavesdrop.openstack.org/meetings/taas/2016/taas.2016-03-02-06.33.log.txt

-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [neutron][taas] Voting for new core reviewers

[reedip banerjee]

+1 to both Soichi and Yamamoto
--
Date: Tue, 1 Mar 2016 21:26:59 +0100
From: Vinay Yadhav <vinayyad...@gmail.com>
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: [openstack-dev]  [neutron][taas]
Message-ID:
<ca+bcmm3avextk-vb4y0e8dphyb0pjxsutkxfv6_bsshqkf-...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi All,

Its time to induct new members to the TaaS core reviewers, to kick start
the process i nominate the following developers and active contributors to
the TaaS project

1. Yamamoto Takashi
2. Soichi Shigeta


Cheers,
Vinay Yadhav

-- 
Thanks and Regards,
Reedip Banerjee
IRC: reedip
__
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] [Openstack-Dev][neutron][TaaS] Suggestion and review of TaaS Specification

[reedip banerjee]

Dear All Neutron Members,
As you may know, Tap-as-a-service was first demonstrated in the Vancouver
summit[1].
Since then it has progressed with the work currently going on in the
specification, and its induction as an extension of the Neutron project.

Considering the same,we would like to invite you to review and provide your
invaluable comments to the specification at [2].

You are also invited to join the Weekly Meeting [3] to share your thoughts
on the further development of Tap-as-a-service.

Looking forward to seeing you there.

[1]
https://www.openstack.org/summit/vancouver-2015/summit-videos/presentation/tap-as-a-service-taas-port-monitoring-for-neutron-networks
[2] https://review.openstack.org/#/c/256210/ .
[3] http://eavesdrop.openstack.org/#Tap_as_a_Service_Meeting


-- 
Thanks and Regards,
Reedip Banerjee
__
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] [Neutron][TaaS] Query regarding TaaS API

[reedip banerjee]

Dear Members of Neutron-TaaS community,

One of the points discussed in the last meeting , was whether we need to
modify the  API endpoints from
/v2_0/taas/ to /v2_0
Most of the Extensions in Neutron are listed under v2_0, and do not need
any separate Parent ID.

I would like to know if there is any specific reason to keep the End Points
under the parenthood of ´taas´?
If not, then like other extensions, we should move the endpoints to v2_0.

Thanks and Regards,
Reedip Banerjee


On Wed, Nov 25, 2015 at 4:45 PM, reedip banerjee <reedi...@gmail.com> wrote:

> Dear Members of Neutron-TaaS community,
> I have a few queries related to the TaaS API, and would like to know a bit
> more details about them.
>
> a) Currently Tap Service and Tap flow Endpoints are listed under
> /v2_0/taas/
>
> For example:
> http://111.000.222.115:9696/v2.0/taas/tap-services.json
> http://111.000.222.115:9696/v2.0/taas/tap-flows.json
>
> Is it necessary to list the endpoints under /taas/?
> Can we keep them under v2_0 like most of the other Neutron Extensions?
> i.e.
>
> http://111.000.222.115:9696/v2.0/taas/tap-services.json  -->
> http://111.000.222.115:9696/v2.0/tap-services.json
>
> b) Currently TaaS has 2 different ports:
> - Tap Service uses port_id to specify ports
> - Tap Flow uses source_port to specify ports.
> As both of these attributes are under different end points, can we use
> ´port´ instead of port_id and source_port?
> From my understanding, port makes bit of a sense, and it is also an known
> attribute in Neutron.
>
>
>
> --
> Thanks and Regards,
> Reedip Banerjee
> irc:reedip
>
>


-- 
Thanks and Regards,
Reedip Banerjee


The Only One Thing Constant In Life Is CHANGE
__
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] [Neutron][TaaS] Query regarding TaaS API

[reedip banerjee]

Dear Members of Neutron-TaaS community,
I have a few queries related to the TaaS API, and would like to know a bit
more details about them.

a) Currently Tap Service and Tap flow Endpoints are listed under /v2_0/taas/

For example:
http://111.000.222.115:9696/v2.0/taas/tap-services.json
http://111.000.222.115:9696/v2.0/taas/tap-flows.json

Is it necessary to list the endpoints under /taas/?
Can we keep them under v2_0 like most of the other Neutron Extensions?
i.e.

http://111.000.222.115:9696/v2.0/taas/tap-services.json  -->
http://111.000.222.115:9696/v2.0/tap-services.json

b) Currently TaaS has 2 different ports:
- Tap Service uses port_id to specify ports
- Tap Flow uses source_port to specify ports.
As both of these attributes are under different end points, can we use
´port´ instead of port_id and source_port?
>From my understanding, port makes bit of a sense, and it is also an known
attribute in Neutron.



-- 
Thanks and Regards,
Reedip Banerjee
irc:reedip
__
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