[openstack-dev] [neutron] Release liaison needed

[Dariusz Śmigiel]

Hey folks,
Unfortunately, I'm not able to fulfill release liaison role anymore.
The same applies to being infra liaison. It means, that this very
important role needs YOU!


If you'll decide to join the army of release liaisons, you will be
responsible for:
* releases!
* communication with release team!
* glory!
* your name will be placed here [1]

If you're not convinced yet, you can read about liaison responsibilities [2].

Join now! Neutron needs YOU!


[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons
[2] 
https://docs.openstack.org/project-team-guide/release-management.html#liaison-responsibilities

PS I should be around for some time. So, if any help is needed, I can
try to help.

Thanks,
Dariusz

__
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][networking-bagpipe][networking-bgpvpn][networking-midonet][networking-odl][networking-ovn][networking-sfc][neutron-dynamic-routing][neutron-fwaas] Pike-1 release

[Dariusz Śmigiel]

Hey neutrinos,
It is the time. We need to show something to others. That's why, it's
called [1] Milestone.
I've prepared release [2] for all neutron deliverables. This time,
thanks to synchronized release schedule, and gathering most of
networking projects under neutron umbrella, we have pretty huge scope
of changes.
I've applied pike-1 tag to latest changes from git. If there are any
concerns or discrepancies for release, feel free to review mentioned
change.

[1] https://releases.openstack.org/pike/schedule.html#p-1
[2] https://review.openstack.org/#/c/455844/

Thanks,
dasm, Dariusz Śmigiel

__
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] [keystone] rejoining our IRC channel

[Dariusz Śmigiel]

2017-04-06 17:16 GMT-05:00 Jeremy Stanley :
> On 2017-04-06 16:04:14 -0500 (-0500), Lance Bragstad wrote:
>> If you chill in #openstack-keystone, we had a little mishap today that
>> resulted in people getting accidentally kicked from the channel. Everything
>> is back to normal and if you haven't already done so, feel free to hop back
>> in.
>
> Sad to say it was all thanks to my butterfingers. Sorry about the
> disruption... :/

Jeremy, that [1] was brutal :)

[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2017-04-06.log.html#t2017-04-06T20:46:40

> --
> Jeremy Stanley
>

--
Dariusz Smigiel

__
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] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

[Dariusz Śmigiel]

Hey Saverio,

2017-03-17 8:20 GMT-05:00 Saverio Proto :
> Client version: openstack 3.9.0
>
> I cant find any lbaas commands. I have to use the 'neutron' client.

It's highly possible, that LBaaS commands are not in OSC.

>
> Everycommand I get:
> neutron CLI is deprecated and will be removed in the future. Use
> openstack CLI instead.

For now, nothing's changed. Neutron CLI emits this information to
encourage users to use OSC. Although, it still supports existing
commands, but won't add new features.
If CLI will be changed, in backward incompatible way, new major
version will be released. Until then, you can use it.

>
> Is LBaaS even going to be implemented in the unified openstack client ?

Yes, Ankur Gupta is working on that [1].
It's initial version, so it can take some time to achieve feature
parity between Neutron CLI and OSC, but the work is happening.
Please remember, that even, when abovementioned change will be merged,
it still needs to be released in new OpenStack Client. So it won't be
immediately available.

[1] https://review.openstack.org/#/c/428414/

BR,
Dariusz

__
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][astara-neutron]

[Dariusz Śmigiel]

> Looks like their IRC channel [0] died off awhile ago as well.
>
> [0] http://eavesdrop.openstack.org/irclogs/%23openstack-astara/
>

Sean thanks,
didn't think about checking their IRC channel. But based on that [0]
it seems like there won't be any more involvement.

[0] 
http://eavesdrop.openstack.org/irclogs/%23openstack-astara/%23openstack-astara.2016-10-07.log.html#t2016-10-07T16:53:17

__
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][astara-neutron]

[Dariusz Śmigiel]

Hey,
astara-neutron repo seems to be broken for a long time [1].
Last merged patches are dated on July 2016 [2]. After that, there is a
queue with jenkins -1s. It doesn't look like to be maintained anymore.

Is there an interest in the Community to fix that?

BR,
dasm

[1] https://review.openstack.org/#/q/project:openstack/astara-neutron
[2] https://review.openstack.org/#/c/340033/

__
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][sfc] stable/ocata version

[Dariusz Śmigiel]

2017-03-06 11:27 GMT-06:00 Henry Fourie :
> Gary,
>
>Awaiting approval:
>
> https://review.openstack.org/#/c/439200
>
> -Louis
>
It's merged. Stable branch is created.

__
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] [networking-sfc] Stable/Ocata Version

[Dariusz Śmigiel]

2017-03-06 11:25 GMT-06:00 Henry Fourie :
> Jeffrey,
>
>The branch pull is awaiting approval:
>
> https://review.openstack.org/#/c/439200

Just got merged.

__
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] Some findings while profiling instances boot

[Dariusz Śmigiel]

We're planning to come up with some solution regarding neutron profiling.
For this purpose etherpad [1] got created.

If anyone wants to join efforts, feel free to contribute.

[1] https://etherpad.openstack.org/p/neutron-profiling

__
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

[Dariusz Śmigiel]

You're the boss

2017-02-19 8:52 GMT-05:00 reedip banerjee :
> +1
>
> On Sat, Feb 18, 2017 at 4:38 AM, Kevin Benton  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
>



-- 
Darek "dasm" Śmigiel


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

__
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

[Dariusz Śmigiel]

+2

sent from phone
Darek

On Feb 17, 2017 15:33, "Ihar Hrachyshka"  wrote:

> +1.
>
> On Fri, Feb 17, 2017 at 11:18 AM, Kevin Benton  wrote:
> > 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
>
__
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] Ocata Feature Freeze

[Dariusz Śmigiel]

Dear Neutrinos,
Feature Freeze day arrived! Ocata-3 has been released, so it means
that no new features will be allowed to current release... The only
patches approved to be merged should be: release critical or gate
blocker.
All outstanding features, that would need to be landed into Ocata,
will need to receive "Feature Freeze Exception" status.

>From now on, we have one week till RC1.
Please double check release notes and make sure everything is in order.

Thanks,
Dariusz
your Release Liaison

__
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] [vpnaas] vpnaas no longer part of the neutron governance

[Dariusz Śmigiel]

2017-01-13 11:17 GMT-06:00 Doug Hellmann :
> Excerpts from Dariusz Śmigiel's message of 2017-01-13 09:11:01 -0600:
>> 2017-01-12 21:43 GMT-06:00 Takashi Yamamoto :
>> > hi,
>> >
>> > On Wed, Nov 16, 2016 at 11:02 AM, Armando M.  wrote:
>> >> Hi
>> >>
>> >> As of today, the project neutron-vpnaas is no longer part of the neutron
>> >> governance. This was a decision reached after the project saw a dramatic
>> >> drop in active development over a prolonged period of time.
>> >>
>> >> What does this mean in practice?
>> >>
>> >> From a visibility point of view, release notes and documentation will no
>> >> longer appear on openstack.org as of Ocata going forward.
>> >> No more releases will be published by the neutron release team.
>> >> The neutron team will stop proposing fixes for the upstream CI, if not
>> >> solely on a voluntary basis (e.g. I still felt like proposing [2]).
>> >>
>> >> How does it affect you, the user or the deployer?
>> >>
>> >> You can continue to use vpnaas and its CLI via the python-neutronclient 
>> >> and
>> >> expect it to work with neutron up until the newton
>> >> release/python-neutronclient 6.0.0. After this point, if you want a 
>> >> release
>> >> that works for Ocata or newer, you need to proactively request a release
>> >> [5], and reach out to a member of the neutron release team [3] for 
>> >> approval.
>> >
>> > i want to make an ocata release. (and more importantly the stable branch,
>> > for the benefit of consuming subprojects)
>> > for the purpose, the next step would be ocata-3, right?
>>
>> Hey Takashi,
>> If you want to release new version of neutron-vpnaas, please look at [1].
>> This is the place, which you need to update and based on provided
>> details, tags and branches will be cut.
>>
>> [1] 
>> https://github.com/openstack/releases/blob/master/deliverables/ocata/neutron-vpnaas.yaml
>
> Unfortunately, since vpnaas is no longer part of an official project,
> we won't be using the releases repository to manage and publish
> information about the releases. It'll need to be done by hand.
>
> Doug
>
Thanks Doug for clarification,

Dariusz

__
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] [infra][Neutron] Running out of memory on gate for linux bridge job

[Dariusz Śmigiel]

2017-01-13 11:13 GMT-06:00 Kevin Benton :
> Sounds like we must have a memory leak in the Linux bridge agent if that's
> the only difference between the Linux bridge job and the ovs ones. Is there
> a bug tracking this?

Just created one [1]. For now, this issue was observed in two cases
(mentioned in bug description).

[1] https://bugs.launchpad.net/neutron/+bug/1656386

__
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] [vpnaas] vpnaas no longer part of the neutron governance

[Dariusz Śmigiel]

2017-01-12 21:43 GMT-06:00 Takashi Yamamoto :
> hi,
>
> On Wed, Nov 16, 2016 at 11:02 AM, Armando M.  wrote:
>> Hi
>>
>> As of today, the project neutron-vpnaas is no longer part of the neutron
>> governance. This was a decision reached after the project saw a dramatic
>> drop in active development over a prolonged period of time.
>>
>> What does this mean in practice?
>>
>> From a visibility point of view, release notes and documentation will no
>> longer appear on openstack.org as of Ocata going forward.
>> No more releases will be published by the neutron release team.
>> The neutron team will stop proposing fixes for the upstream CI, if not
>> solely on a voluntary basis (e.g. I still felt like proposing [2]).
>>
>> How does it affect you, the user or the deployer?
>>
>> You can continue to use vpnaas and its CLI via the python-neutronclient and
>> expect it to work with neutron up until the newton
>> release/python-neutronclient 6.0.0. After this point, if you want a release
>> that works for Ocata or newer, you need to proactively request a release
>> [5], and reach out to a member of the neutron release team [3] for approval.
>
> i want to make an ocata release. (and more importantly the stable branch,
> for the benefit of consuming subprojects)
> for the purpose, the next step would be ocata-3, right?

Hey Takashi,
If you want to release new version of neutron-vpnaas, please look at [1].
This is the place, which you need to update and based on provided
details, tags and branches will be cut.

[1] 
https://github.com/openstack/releases/blob/master/deliverables/ocata/neutron-vpnaas.yaml

BR, Dariusz

__
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] PTL nominations deadline and non-candidacy

[Dariusz Śmigiel]

2017-01-09 8:11 GMT-06:00 Armando M. :
> Hi neutrinos,
>
> The PTL nomination week is fast approaching [0], and as you might have
> guessed by the subject of this email, I am not planning to run for Pike. If
> I look back at [1], I would like to think that I was able to exercise the
> influence on the goals I set out with my first self-nomination [2].
>
> That said, when it comes to a dynamic project like neutron one can't never
> claim to be *done done* and for this reason, I will continue to be part of
> the neutron core team, and help the future PTL drive the next stage of the
> project's journey.
>
> I must admit, I don't write this email lightly, however I feel that it is
> now the right moment for me to step down, and give someone else the
> opportunity to grow in the amazing role of neutron PTL! I have certainly
> loved every minute of it!
>
> Cheers,
> Armando
>
> [0] https://releases.openstack.org/ocata/schedule.html
> [1]
> https://review.openstack.org/#/q/project:openstack/election+owner:armando-migliaccio
> [2] https://review.openstack.org/#/c/223764/
>

Armando,
Sad to see you're stepping down. Thanks for your time and guidance as
neutron PTL.

Dariusz

__
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] Creating a new IRC meeting room ?

[Dariusz Śmigiel]

2016-12-05 12:51 GMT-06:00 Paul Belanger :
> On Mon, Dec 05, 2016 at 09:47:15AM +0100, Luigi Toscano wrote:
>> On Friday, 2 December 2016 14:42:31 CET Matt Riedemann wrote:
>> > But like we recently talked about the stable team meetings, we don't
>> > really need to be in a separate -alt room for those when we have the
>> > channel and anyone that cares about stable enough to be in the meeting
>> > is already in that channel, but sometimes the people in that channel
>> > forget about the meeting or which of the 20 alt rooms it's being held
>> > in, so they miss it (or Tony is biking down a volcano and we just don't
>> > have a meeting).
>>
>> This is just part of the problem, but couldn't the bot remind about the
>> meeting before its start on the main channel of a project? It would help with
>> people forgetting about the meetings.
>>
> I'm glad I am not the only one who has wanted this. Always thought it would 
> be a
> nice feature to have one of our bot remind me, PM would work, about coming
> events.
>
> This could be fixed if I could figure out have to run a calendar notifications
> via console.
>

Oslo community has working tool for that purpose [1]. Probably it
could be used during other meetings.

Although, if someone is interested in particular Meeting, probably
will be able to have some kind of reminder: calendar, console one
(sent by fungi in other thread[2]).

I've seen couple flash meetings in different #openstack-{project}
channels, so I think, instead of creating new separated channel,
better would be just to have meeting activity in the {project} one.


[1] https://github.com/openstack/oslo.tools/blob/master/ping_me.py
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-December/108470.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Stepping down from core

[Dariusz Śmigiel]

Henry,
it's very sad to see you stepping down.
Thank you for all the time and help in Keystone v3 development.

I hope you will have a lot of new, even better, experiences in your
further journey.

Thank you

2016-12-01 16:51 GMT-06:00 Henry Gessau :
> I've already communicated this in the neutron meeting and in some neutron
> policy patches, but yesterday the PTL actually updated the gerrit ACLs so I
> thought I'd drop a note here too.
>
> My work situation has changed and leaves me little time to keep up with my
> duties as core reviewer, DB lieutenant, and drivers team member.
>
> Working with the diverse and very talented contributors to Neutron has been
> the best experience of my career (which started before many of you were born).
> Thank you all for making the team such a great community. Because of you the
> project is thriving and will continue to be successful!
>
> I will still be around on IRC, contribute some small patches here and there,
> and generally try to keep abreast of Neutron's progress. Don't hesitate to
> ping me.
>
> __
> 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



-- 
Darek "dasm" Śmigiel


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

__
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] Deprecation warnings

[Dariusz Śmigiel]

Hey Neutrinos & Co.
Lately, there were couple patches merged which removed deprecated
functions from neutron code [1][2][3][4][5]. It seems that at least
[1] caused [6].

If you see any problems, errors, disruptions, it could be caused by
one of these.
Please verify if all places with deprecation warnings have mitigations applied.

Hopefully, there won't be any other problems, but either way, possible
breakages will be announced during Team Meeting [7]

Thank you for your cooperation.
Darek


[1] https://review.openstack.org/#/c/379645/
[2] https://review.openstack.org/#/c/379767/
[3] https://review.openstack.org/#/c/379809/
[4] https://review.openstack.org/#/c/379651/
[5] https://review.openstack.org/#/c/379641/
[6] https://bugs.launchpad.net/vmware-nsx/+bug/1640319
[7] 
https://wiki.openstack.org/wiki/Network/Meetings#Neutron-lib_and_planned_neutron_refactoring

__
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 meeting this Monday at 2100 UTC + forthcoming schedule

[Dariusz Śmigiel]

It means that next Team Meeting will have a place on November 8, Tuesday.

Any cancellations for other Neutron Meetings?

2016-10-17 13:28 GMT-05:00 Armando M. :
> Hi neutrinos,
>
> A kind reminder for this week's meeting. More on the agenda [1]. Also, due
> to the summit, the next occurrences will be cancelled.
>
> - Oct 25, Tuesday
> - Oct 31, Monday
>
> Cheers,
> Armando
>
> [1] https://wiki.openstack.org/wiki/Network/Meetings
>
> __
> 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
>



-- 
Darek "dasm" Śmigiel


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

__
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

[Dariusz Śmigiel]

Congrats Ihar. You deserve this!

2016-09-17 18:40 GMT+02:00 Armando M. :
> 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
>



-- 
Darek "dasm" Śmigiel


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

__
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