[openstack-dev] [neutron] stepping down from infra liaison

[Das, Anindita]

Hi All,

Some of you already know about the recent changes in OSIC. Unfortunately, I am 
impacted by these changes.

So I will not be able to contribute to neutron and fulfill my responsibilities 
as infra liaison. It was a very rewarding experience working with everybody in 
the neutron community. Thank you to everyone who helped me to contribute to 
neutron in the past few releases.

Hopefully, I will get an opportunity in the future to return to OpenStack 
development. Till then will be cheering you on from the sidelines.

Thanks,
Anindita (irc:dasanind)

P.S. Will still be available in IRC on and off. Please don’t hesitate to ping 
me if in case I can be of any help.
__
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] bug deputy report (Mar 6- Mar 13)

[Das, Anindita]

Hi All,

I was serving as bug deputy for the last week. There were 25 bugs and few RFE’s 
that were raised last week.

Of the 25 bugs 2 are still uncategorized, so help with them will be highly 
appreciated.


1.   https://bugs.launchpad.net/neutron/+bug/1672345 -- Loadbalancer V2 
ports are not serviced by DVR

2.   https://bugs.launchpad.net/neutron/+bug/1672433 -- dhcp-agent should 
send a grace ARP after assigning IP address in dhcp namespace

Thanks,
Anindita (irc: dasanind)
__
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

[Das, Anindita]

+1

From: Kevin Benton 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 17, 2017 at 5:08 PM
To: "openstack-dev@lists.openstack.org" 
Subject: [openstack-dev] [neutron] - Team photo

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

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Das, Anindita]

+1

--Anindita Das (irc: dasanind)

From: "Vasudevan, Swaminathan (PNB Roseville)" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, February 17, 2017 at 2:30 PM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on 
Thursday

Count me in.

From: Kevin Benton [mailto: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

Re: [openstack-dev] [tricircle] python-tricircleclient repo officially created

[Das, Anindita]

Awesome Victor!! Congratulations. ☺

Anindita

From: "Morales, Victor" 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Wednesday, February 15, 2017 at 10:19 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [tricircle] python-tricircleclient repo officially 
created

Howdy,

I’m happy to announce that after OpenStack Governance has approved[1] and infra 
them processed the request[2],  the python-tricircleclient repository  has been 
created[3].  This client pretends to make things simpler for users who require 
multi region solutions which can be addressed by Tricircle.  Hopefully this 
project helps for the adoption and visibility of this solution.  Lastly,  this 
client is still under developing and requires all your expertise to improve it 
so feel free to add new capabilities and features that you consider necessary.

Regards,
Victor Morales
irc: electrocucaracha

[1] https://review.openstack.org/#/c/426419/
[2] https://review.openstack.org/#/c/426859/
[3] http://git.openstack.org/cgit/openstack/python-tricircleclient/
__
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] [All] IRC Mishaps

[Das, Anindita]

One of my embarrassing moments ... Sent a partial message accidentally in IRC 
meeting by hitting “Enter” instead of “Backspace” ☹

Anindita Das
irc: dasanind

On 2/8/17, 5:04 PM, "Jay Pipes"  wrote:

On 02/08/2017 03:36 PM, Kendall Nelson wrote:
> Hello All!
>
> So I am sure we've all seen it: people writing terminal commands into
> our project channels, misusing '/' commands, etc. But have any of you
> actually done it?
>
> If any of you cores, ptls or other upstanding members of our wonderful
> community have had one of these embarrassing experiences please reply! I
> am writing an article for the SuperUser trying to make us all seem a
> little more human to people new to the community and new to using IRC.
> It can be scary asking questions to such a large group of smart people
> and its even more off putting when we make mistakes in front of them.
>
> So please share your stories!

Hi!

I can't tell you the number of times I've typed or pasted one of these:

:wq

or

1407gg

or

ggVG

or

:find nova/compute/resource_tracker.py

or

Vgq

or

tox -py27 -- --failing

Such is the life of a keyboard-driven contributor I guess! :)

-jay

__
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] [ovo] unhashable type error

[Das, Anindita]

On 1/25/17, 1:59 PM, "Ihar Hrachyshka" <ihrac...@redhat.com> wrote:

  > Looking at the code, I don't see a clear case to even use set() type
  > there. A list would seem to work just fine. Should we try to convert
  > to using lists there?
   
I will convert it into a list and check how it works.

   > Nevertheless, we can look into extending the object base class for
   > hashing. I wonder though if it's something to tackle in Neutron scope.
   > Sounds more like an oslo.versionedobjects library feature request.

Currently, I have added the hashing in the specific object but as you mentioned 
it
should be in object base class. I will try implementing that.

As the hashing for the OVO’s is based on the primary keys
I am not sure whether we can implement this in oslo.versionedobjects library.

Thanks,
Anindita (irc: dasanind)

On Wed, Jan 25, 2017 at 11:53 AM, Das, Anindita <anindita@intel.com> 
wrote:
> Hi Ihar,
>
>
>
> While doing the integration for vlanallocation [1] I found that OVO
> associated with VlanAllocation throws “unhashable type” error with py35.
>
> The associated stack trace is here [2].
>
>
>
> To resolve this issue I added an equality and hash method in the
> vlanallocation OVO [3].
>
> My understanding is we will face the same problem with other OVO objects 
as
> well when we do similar operations on the object as in [1].
>
> Should we make all the OVO objects hashable or deal it case by case?
> Thoughts?
>
>
>
>
>
> [1]
> 
https://review.openstack.org/#/c/367810/28/neutron/plugins/ml2/drivers/type_vlan.py@77
>
> [2] http://paste.openstack.org/show/596281/
>
> [3]
> 
https://review.openstack.org/#/c/367810/28/neutron/objects/plugins/ml2/vlanallocation.py@38-55
>
>
>
> Thanks,
>
> Anindita (irc: dasanind)


__
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] [ovo] unhashable type error

[Das, Anindita]

Hi Ihar,

While doing the integration for vlanallocation [1] I found that OVO associated 
with VlanAllocation throws “unhashable type” error with py35.
The associated stack trace is here [2].

To resolve this issue I added an equality and hash method in the vlanallocation 
OVO [3].
My understanding is we will face the same problem with other OVO objects as 
well when we do similar operations on the object as in [1].
Should we make all the OVO objects hashable or deal it case by case? Thoughts?


[1] 
https://review.openstack.org/#/c/367810/28/neutron/plugins/ml2/drivers/type_vlan.py@77
[2] http://paste.openstack.org/show/596281/
[3] 
https://review.openstack.org/#/c/367810/28/neutron/objects/plugins/ml2/vlanallocation.py@38-55

Thanks,
Anindita (irc: dasanind)
__
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

[Das, Anindita]

Sad to see you go, Carl. Thank you for your guidance and support.

All the best for your future endeavors.

--Anindita

From: Carl Baldwin >
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
>
Date: Thursday, November 17, 2016 at 6:42 PM
To: OpenStack Development Mailing List 
>
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

[openstack-dev] [neutron] bug deputy report

[Das, Anindita]

Hi All,

I was serving as a bug deputy for the last week. There were 31 bugs and few 
RFE’s that were raised last week.

Of the 31 bugs 3 are still uncategorized, so help with them will be highly 
appreciated.


1.   https://bugs.launchpad.net/neutron/+bug/1635554 - Delete Router / race 
condition

2.   https://bugs.launchpad.net/neutron/+bug/1635593 - DBReferenceError 
while removing router (Cisco plugin case)

3.   https://bugs.launchpad.net/neutron/+bug/1635765 - UDP checksum 
incorrectly generated on Fragmented UDP packets

Thanks to everybody who helped me during last week through the bug deputy 
process and triaging the bugs. It was a very exciting experience. Without your 
help so many of the bugs would not have been triaged.

Cheers,
Anindita



__
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] Adding ihrachys to the neutron-drivers team

[Das, Anindita]

Congratulations Ihar !!

From: "Armando M." 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Saturday, September 17, 2016 at 11:40 AM
To: "OpenStack Development Mailing List (not for usage questions)" 

Subject: [openstack-dev] [Neutron] Adding ihrachys to the neutron-drivers team

Hi folks,

I would like to propose Ihar to become a member of the Neutron drivers team [1].

Ihar wide knowledge of the Neutron codebase, and his longstanding duties as 
stable core, downstream package whisperer, release and oslo liaison (I am sure 
I am forgetting some other capacity he is in) is going to put him at great 
comfort in the newly appointed role, and help him grow and become wise even 
further.

Even though we have not been meeting regularly lately we will resume our 
Thursday meetings soon [2], and having Ihar onboard by then will be highly 
beneficial.

Please, join me in welcome Ihar to the team.

Cheers,
Armando

[1] 
http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team
[2] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
__
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