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

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

Re: [openstack-dev] [neutron] NeutronLibImpact: Adoption of db *_FIELD_SIZE constants from neutron-lib

ZES are done, then we will be in a position to remove attributes.py from core neutron. That is the aim of this little dance. > Thanks > Gary > > > > > On 11/26/16, 9:03 AM, "Henry Gessau" <hen...@gessau.net> wrote: > > The following _MAX_LEN constants

[openstack-dev] [neutron] NeutronLibImpact: Removing deprecated model_base mixins from core

The deprecated model_base mixins are be being removed from neutron/db/model_base.py and neutron/db/models_v2.py in [1]. The mixins from neutron_lib.db.model_base should be used instead. All subproject maintainers should update their code to use the model_base mixins from neutron-lib. I have

[openstack-dev] [neutron] NeutronLibImpact: Adoption of db *_FIELD_SIZE constants from neutron-lib

The following _MAX_LEN constants are being removed from neutron/api/v2/attributes.py in [1]. The corresponding DB field size constants from neutron_lib.db.constants should be used instead. All subproject maintainers should update their code to use the the db *_FIELD_SIZE constants from

[openstack-dev] [neutron] NeutronLibImpact: Adoption of ExtensionDescriptor from neutron-lib

The ExtensionDescriptor class has been rehomed to neutron-lib and is being removed from neutron core, see [1]. All subproject maintainers should update their code to use the ExtensionDescriptor class from neutron-lib. I have submitted patches [2] for most subprojects. This will be highlighted

[openstack-dev] [neutron] NeutronLibImpact: Removal of PLURALS

The PLURALS dict in neutron.api.v2.attributes is written to but never used. Before rehoming neutron.api.v2.attributes to neutron-lib I am removing all references to PLURALS [1]. All subproject maintainers should remove the use of PLURALS from their code. I have submitted patches [2] for most

[openstack-dev] [neutron] Reviews needed in neutron-lib

During the meeting today I promised to provide a list of reviews in neutron-lib that need review attention. The following are patches that "rehome" code from neutron core into neutron-lib and are therefore important to keep up the velocity of neutron-lib adoption:

[openstack-dev] [neutron] Weekly neutron-lib meeting canceled

See https://review.openstack.org/395034 We now have a slot in the main neutron project meeting. If we do need extra meeting time for neutron-lib we can set up something based on who wants to attend and when. __ OpenStack

[openstack-dev] [neutron] Barcelona summit neutron-lib session recap

Ocata neutron-lib session recap --- tl;dr: - Speed up moving common code into neutron-lib - Sub-project maintainers must keep up and should contribute The session consisted of announcing the goals around speeding up the neutron-lib work so that consuming projects

Re: [openstack-dev] [neutron] neutron-lib

Gary Kotton wrote: > Would it be possible to cut a new version of neutron-lib. This will enable us > to proceed with the integration into the various projects? https://review.openstack.org/392009 __

[openstack-dev] [Neutron] Next neutron-lib meeting is November 9

Due to the summit. __ 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] Database field sizes and attribute "MAX_LEN" constants

values. Yes, we could have some tests, although a patch changing a constant would probably also have a change to the test. :) We might need to also have a prominent "Warning! Do not change this test!" comment for each test. > > > On Sat, Oct 15, 2016 at 10:41 PM Henry Ges

Re: [openstack-dev] [Neutron] Database field sizes and attribute "MAX_LEN" constants

Ihar Hrachyshka <ihrac...@redhat.com> wrote: > Henry Gessau <hen...@gessau.net> wrote: > >> Hi neutrinos, >> >> In Neutron many attributes are stored in database fields. The size of these >> fields therefore determines the maximum length of the attrib

[openstack-dev] [Neutron] Database field sizes and attribute "MAX_LEN" constants

Hi neutrinos, In Neutron many attributes are stored in database fields. The size of these fields therefore determines the maximum length of the attribute values. I would like to get some consistency in place around how we define the constants and where they are used. Here are my thoughts... 1.

Re: [openstack-dev] [Neutron] Neutron team social event in Barcelona

Thanks for organizing this Miguel! I plan to attend. 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:

Re: [openstack-dev] [oslo.db] [release] opportunistic tests breaking randomly

Sean Dague wrote: > On 09/15/2016 09:20 AM, Roman Podoliaka wrote: >> Sean, >> >> So currently we have a default timeout of 160s in Nova. And >> specifically for migration tests we set a scaling factor of 2. Let's >> maybe give 2.5 or 3 a try (

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

+1000! Armando M. wrote: > 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

Re: [openstack-dev] [neutron] neutronclient check queue is broken

Akihiro Motoki wrote: > In the neutronclient check queue, > gate-neutronclient-test-dsvm-functional is broken now [1]. > Please avoid issuing 'recheck'. > > [1] https://bugs.launchpad.net/python-neutronclient/+bug/1616749 The fix [2] has merged. Carry on. [2]

Re: [openstack-dev] [OpenStack-docs] [neutron] [api] [doc] API reference for neutron stadium projects (re: API status report)

Akihiro Motoki wrote: > this mail focuses on neutron-specific topics. I dropped cinder and ironic > tags. > > 2016-08-11 23:52 GMT+09:00 Anne Gentle : >> >> >> On Wed, Aug 10, 2016 at 2:49 PM, Anne Gentle >>

Re: [openstack-dev] [Neutron] Team and Driver meetings for the week of Aug 15th

Armando M. wrote: > Hi Neutrinos, > > The meetings will be cancelled due to the mid-cycle. The neutron-lib meeting will also skip next week. __ OpenStack Development Mailing List (not for usage

[openstack-dev] [Neutron] Be prepared for bumps in the road -- tenant_id columns have been renamed to project_id

Hello neutrinos and especially maintainers of consuming projects. The patch [1] to rename all tenant_id columns to project_id in the Neutron DB has merged. Although we have tried our best to check for dependencies and side effects, this is a very fundamental change and there may be consequences

Re: [openstack-dev] {neutron][db][models]

Ihar Hrachyshka wrote: > Manjeet S wrote: > >> Hello Team, >> >> I have a question regarding centralizing all db models in neutron. As you >> all know >> Oslo versioned object work is under progress and I also had a ticket >> opened for

[openstack-dev] [Neutron] no neutron-lib meeting today

Myself and dougwig will be unable to attend today. We'll resume as usual next week. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [neutron] how to create initial db migration script to sub-project

d by Alembic. > revision = 'cbb661581082' > down_revision = '65b6db113427b9_initial_contract' > > > def upgrade(): > pass > > -Original Message- > From: Henry Gessau [mailto:hen...@gessau.net] > Sent: Sunday, July 24, 2016 9:21 PM > To: OpenStack Developme

Re: [openstack-dev] [neutron] how to create initial db migration script to sub-project

Hi Moshe, It has been a while since a neutron sub-project initialized new alembic migrations, so the devref is out of date, sorry. Let me help you get this sorted out and then I can update the devref with the latest info. First you need to create the initial migration for each branch (expand and

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing core

Big +1 from me. Assaf Muller wrote: > As Neutron's so called testing lieutenant I would like to propose > Jakub Libosvar to be a core in the testing area. > > Jakub has demonstrated his inherent interest in the testing area over > the last few years, his reviews are

Re: [openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

Henry Gessau <hen...@gessau.net> wrote: > In accordance with the Blueprint [1] and the spec [2], we are in the process > of deprecating the use of the term 'tenant' in favor of 'project'. > > The code change [3] with the biggest impact on Neutron developers is currentl

[openstack-dev] [neutron] Keystone V3 alignment: renaming tenant_id columns to project_id

In accordance with the Blueprint [1] and the spec [2], we are in the process of deprecating the use of the term 'tenant' in favor of 'project'. The code change [3] with the biggest impact on Neutron developers is currently out for review and will merge quite soon (shortly after N-2). This change

Re: [openstack-dev] New Python35 Jobs coming

Clark Boylan wrote: > The infra team is working on taking advantage of the new Ubuntu Xenial > release including running unittests on python35. The current plan is to > get https://review.openstack.org/#/c/336272/ merged next Tuesday (July > 5, 2016). This will add non

Re: [openstack-dev] [Neutron] neutron-lib and dependencies in neutron reference implementation

o separate _constants.py modules. But then I could argue that would proliferate the number of imports required for many repos. Gal Sagie <gal.sa...@gmail.com> wrote: > For example references to the various different agents which are an > implementation details to me > > On Wed, J

Re: [openstack-dev] [Neutron] neutron-lib and dependencies in neutron reference implementation

Gal Sagie wrote: > Hello all, > > I have recently came across some missing constants in neutron-lib and sent > a patch but i wanted to try and understand the scope of the lib. > > I see that the Neutron lib consist of many definitions which are actually > part of the

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Carl Baldwin <c...@ecbaldwin.net> wrote: > On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau <hen...@gessau.net> wrote: >> Darek Smigiel <smigiel.dari...@gmail.com> wrote: >>> strange, that owner is not able to just get rid of *his* network and >>> s

Re: [openstack-dev] [Neutron] Elevating context to remove subnets created by admin

Darek Smigiel wrote: > strange, that owner is not able to just get rid of *his* network and subnets. But not all the subnets are his, and consequently the network is partially not his. Why did the admin create a subnet on the user's network in [1]? IMO the admin

Re: [openstack-dev] [Neutron] Mid-cycle development sprint (NOTE: DATE CHANGE!)

Thierry Carrez <thie...@openstack.org> wrote: > Rossella Sblendido wrote: >> On 05/26/2016 10:47 PM, Henry Gessau wrote: >>> I am happy to announce that the location logistics for the Neutron mid-cycle >>> have been finalized. The mid-cycle will take place in Cork,

[openstack-dev] [Neutron] Mid-cycle development sprint

I am happy to announce that the location logistics for the Neutron mid-cycle have been finalized. The mid-cycle will take place in Cork, Ireland on August 15-17. I have updated the wiki [1] where you will find a link to an etherpad with all the details. There you can add yourself if you plan to

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 for Brian. (And retroactive +1 for Cedric.) Ihar Hrachyshka wrote: > Hi stable-maint-core and all, > > I would like to propose Brian for neutron specific stable team. > > His stats for neutron stable branches are (last 120 days): > > mitaka: 19 reviews; liberty: 68

Re: [openstack-dev] Easing contributions to central documentation

Matt Kassawara wrote: > At each summit, I speak with a variety of developers from different projects > about the apparent lack of contributions to the central documentation. At > previous summits, the most common complaint involved using DocBook. After > converting most of

[openstack-dev] [Neutron] neutron-lib report from the summit

At the Newton summit in Austin we held a session on the next steps for neutron-lib. Here is a report on what was discussed at the session. Etherpad: https://etherpad.openstack.org/p/newton-neutron-lib-next-steps Progress so far --- The package is on PyPI and sub-projects should be

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:

Re: [openstack-dev] [Neutron] Neutron lib hack has broken all decomposed projects

This was a learning experience and we found out the hard way about an extra dependency we had not anticipated. Thanks Gary for spotting it early and hopefully the revert will merge soon. Doug Wiegley wrote: > That revert is https://review.openstack.org/#/c/309776 ,

Re: [openstack-dev] [Neutron] Proposing Hirofumi Ichihara to Neutron Core Reviewer Team

+1, Hirofumi will make a great addition. Akihiro Motoki wrote: > 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

Re: [openstack-dev] [neutron] unit test failures due to new release of Routes package (v2.3)

https://launchpad.net/bugs/1563028 https://review.openstack.org/298855 Aditya Vaja wrote: > Hi, > > I'm seeing unit test failures when I test locally after a fresh git clone of > neutron master. > > $ ./run_tests.sh -V -f > > log excerpt:

Re: [openstack-dev] [Neutron] Plan for changes affecting DB schema

na...@vn.fujitsu.com <na...@vn.fujitsu.com> wrote: > Two weeks ago, I received an information about changing affecting DB schema > [1] from Henry Gessau just a day before the deadline. I was so surprised about > this and could not change my plan for my patch sets. Do yo

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau <hen...@gessau.net> wrote: >> Takashi Yamamoto <yamam...@midokura.com> wrote: >>> Henry, >>> >>> i think it's better to fix model vs

Re: [openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

passes so I don't see any issues, and the patch is independent of the milestone tagging. Please let me know if I am missing the issue(s). > > [1] https://review.openstack.org/#/c/287016/ > > On Tue, Mar 8, 2016 at 11:52 PM, Henry Gessau <hen...@gessau.net> wrote: >>

[openstack-dev] [neutron] Last chance to finish changes affecting DB schema for Mitaka

By tomorrow we intend to tag the heads of all the neutron alembic branches with the MITAKA label [1][2][3][4]. If you have a patch that adds an alembic migration and you want to get it in Mitaka you must be associated with a targeted BP/RFE/bug [5] and get your code merged by tomorrow (Wednesday,

Re: [openstack-dev] [all][infra] eventlet 0.18.1 not on PyPi anymore

ed, Feb 17, 2016 at 5:55 AM, Sean Dague <s...@dague.net> wrote: >>>> >>>>> On 02/17/2016 08:42 AM, Doug Hellmann wrote: >>>>>> Excerpts from Victor Stinner's message of 2016-02-17 14:14:18 +0100: >>>>>>> Le 17/02/2016 13:43, Henry Gessa

Re: [openstack-dev] [all][infra] eventlet 0.18.1 not on PyPi anymore

rpts from Victor Stinner's message of 2016-02-17 14:14:18 +0100: >>>>> Le 17/02/2016 13:43, Henry Gessau a écrit : >>>>>> And it looks like eventlet 0.18.3 breaks neutron: >>>>>> https://bugs.launchpad.net/neutron/+bug/1546506 >>>>> &

Re: [openstack-dev] [all][infra] eventlet 0.18.1 not on PyPi anymore

And it looks like eventlet 0.18.3 breaks neutron: https://bugs.launchpad.net/neutron/+bug/1546506 Victor Stinner wrote: > Hi, > > I asked eventlet dev to *not* remove a release from PyPI before they did > it, but they ignored me and removed 0.18.0 and 0.18.1 releases from

Re: [openstack-dev] [neutron] questions about uni test

Gareth wrote: > It creates and cleans the tables in memory? Creates and deletes actually. Line 69 creates all the tables when a test starts. Line 78 uses the unittest framework to add the function clear_tables() to the post-test operations that are run after every

Re: [openstack-dev] [NEUTRON] Need you help.THANKS!!

hao li wrote: > Hi,everybody. > I am a new hand.At first,I don't know whether the neutron's contributors can > receive this letter. > If not,could you tell me how to contact with them? > We are a neutron team.we add a ''AC-L2 Mech Driver'' to the ML2 Plug-in to > support our

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

Doug Wiegley wrote: > > >> On Jan 11, 2016, at 2:42 AM, Ihar Hrachyshka wrote: >> >> Sean M. Collins wrote: >> On Fri, Jan 08, 2016 at 07:50:47AM PST, Chris Dent wrote: > On Fri, 8 Jan 2016, Gary Kotton wrote:

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

Gary Kotton wrote: > commit > https://github.com/openstack/neutron/commit/5d53dfb8d64186b5b1d2f356fbff8f222e15d1b2 > may > break the decomposed plugins that make use of the method > _get_tenant_id_for_create Note that this is a private method. Plugins should avoid using

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

Sean M. Collins wrote: > I've noticed that a lot of features are now being documented as RSTs > inside of devref. Like the following: > > https://review.openstack.org/#/c/251859/ > > But there are lots already present. Can someone point out to me what the > criteria is for

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Kevin Benton wrote: > So obviously the stuff in the client can be updated since most of that is > user-facing. However, on the server side maybe we can start out by keeping all > of the internal code and DB tables the same. Then all we need to worry about > is the API

Re: [openstack-dev] [Neutron][db][migration] Neutron db migrationby python scripts

Your installed neutron is not current. When developing new db migrations you should be working with the master branch. Fast forward your repo and re-run devstack to get the latest neutron-db-manage. On Tue, Nov 03, 2015, Zhi Chang wrote: > Thanks for your reply. >

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

Thanks Ihar. Here is what I plan to work on, or hope to help out with: Continue working on alembic to support online migrations. The alembic migrations seem to be a mysterious thing to many developers. I plan to improve the devref documentation around this. The --autogenerate of revisions, in

[openstack-dev] [neutron][horizon] Nice new Network Topology panel in Horizon

It has been about three years in the making but now it is finally here. A screenshot doesn't do it justice, so here is a short video overview: https://youtu.be/PxFd-lJV0e4 Isn't that neat? I am sure you can see that it is a great improvement, especially for larger topologies. This new view will

Re: [openstack-dev] [neutron][horizon] Nice new Network Topology panel in Horizon

On Fri, Sep 25, 2015, Daniel Comnea <comnea.d...@gmail.com> wrote: > Great job Henry ! I had nothing to do with it! (See below.) > On Fri, Sep 25, 2015 at 6:47 PM, Henry Gessau <ges...@cisco.com > <mailto:ges...@cisco.com>> wrote: > > It has been about

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Some thought has been given to this. See https://bugs.launchpad.net/neutron/+bug/1460177 I like the third option, a well-known name using DNS. On Thu, Sep 03, 2015, Kevin Benton wrote: > I think that's different than what is being asked here. That patch appears to > just add

Re: [openstack-dev] [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!

+1 to both! On Wed, Aug 12, 2015, Kyle Mestery mest...@mestery.com wrote: It gives me great pleasure to propose Russell Bryant and Brandon Logan as core reviewers in the API/DB/RPC area of Neutron. Russell and Brandon have both been incredible contributors to Neutron for a while now. Their

Re: [openstack-dev] [Neutron] Proposing Cedric Brandily to Neutron Core Reviewer Team

+1! On Wed, Jul 15, 2015, Carl Baldwin c...@ecbaldwin.net wrote: As the Neutron L3 Lieutenant along with Kevin Benton for control plane, and Assaf Muller for testing, I would like to propose Cedric Brandily as a member of the Neutron core reviewer team under these areas of focus. Cedric

Re: [openstack-dev] [neutron] Plethora of dbase migration questions...

On Tue, Jul 07, 2015, Salvatore Orlando sorla...@nicira.com wrote: On 7 July 2015 at 14:00, Paul Michali p...@michali.net mailto:p...@michali.net wrote: Thanks Salvatore for the responses. See @PCM in-line... On Tue, Jul 7, 2015 at 6:14 AM Salvatore Orlando sorla...@nicira.com

Re: [openstack-dev] [neutron] Plethora of dbase migration questions...

On Tue, Jul 07, 2015, Paul Michali p...@michali.net wrote: Thanks Salvatore for the responses. See @PCM in-line... On Tue, Jul 7, 2015 at 6:14 AM Salvatore Orlando sorla...@nicira.com mailto:sorla...@nicira.com wrote: Some comments inline. Salvatore On 6 July 2015 at 20:00,

Re: [openstack-dev] [neutron] - Proposing Miguel Angel Ajo for the Control Plane core team

+1! On Mon, Jul 06, 2015, Kevin Benton blak...@gmail.com wrote: Hello! As the Lieutenant of the built-in control plane[1], I am proposing to add Miguel Angel Ajo to the control plane core reviewer team. His review stats are inline with the other core reviewers[2], and his work on

Re: [openstack-dev] [neutron] How to handle security issues in external repos?

(+0200), Henry Gessau wrote: [...] The question now arises about what to do when a security issue is found in such an external repository that integrates with Neutron. - How should such security issues be managed? The OpenStack Vulnerability Management Team (VMT) follows a documented process

[openstack-dev] [neutron] How to handle security issues in external repos?

In the Liberty cycle Neutron is mandating the splitting out of third-party plugins and drivers into separate repositories, see [1]. These external repositories will be managed by the maintainers of the code, who are independent from the neutron core maintainers. The question now arises about what

Re: [openstack-dev] [neutron] db migration for vendor extensions

On Thu, Jul 02, 2015, Fawad Khaliq fa...@plumgrid.com wrote: After Neutron core and vendor code decomposition [1], it was decided to keep db migration scripts in Neutron repo. I was wondering if any of the networking-* project owners figured out an alternative to this approach where DB

Re: [openstack-dev] [Neutron] Proposing Ann Kamyshnikova for the API DB core reviewer team

It has been a week and feedback has been positive and supportive of Ann's nomination. Welcome to the Neutron DB core reviewer team, Ann. -- Henry On Thu, Jun 11, 2015, Henry Gessau ges...@cisco.com wrote: As one of the Lieutenants [1] for the API and DB areas under the PTL, I would like

Re: [openstack-dev] [Neutron] Proposing Rossella Sblendido for the Control Plane core team

A big +1 from me. Rossella is also a great community influence with her Land your first patch for Neutron talk at the Paris summit. On Fri, Jun 12, 2015, Kevin Benton blak...@gmail.com wrote: Hello! As the Lieutenant of the built-in control plane[1], I would like Rossella Sblendido to be a

Re: [openstack-dev] [Neutron] Proposing YAMAMOTO Takashi for the Control Plane core team

Although I am not on your list I would like to add my +1! Yamamoto shows great attention to detail in code reviews and frequently finds real issues that were not spotted by others. On Thu, Jun 11, 2015, Kevin Benton blak...@gmail.com wrote: Hello all! As the Lieutenant of the built-in control

Re: [openstack-dev] [neutron] Microversioning work questions and kick-start

On Thu, Jun 11, 2015, Salvatore Orlando sorla...@nicira.com wrote: Finally, I received queries from several community members that would be keen on helping supporting this microversioning effort. I wonder if the PTL and the API lieutenants would ok with agreeing to have a team of developers

[openstack-dev] [Neutron] Proposing Ann Kamyshnikova for the API DB core reviewer team

As one of the Lieutenants [1] for the API and DB areas under the PTL, I would like to propose Ann Kamyshnikova as a member of the Neutron API and DB core reviewer team. Ann has been a long time contributor in Neutron showing expertise particularly in database matters. She has also worked with and

Re: [openstack-dev] Proposing Brian Haley to Neutron L3 Core Reviewer Team

+1 Brian will be a great addition for L3 On Wed, Jun 10, 2015, Carl Baldwin c...@ecbaldwin.net wrote: Folks, As the Neutron L3 Lieutenant [1] under the PTL, Kyle, I'd like to propose Brian Haley as a member of the Neutron L3 core reviewer team. Brian has been a long time contributor in

Re: [openstack-dev] [neutron] Proposing Assaf Muller for the Neutron Core Reviewer Team

+1 On Thu, May 28, 2015, Kyle Mestery mest...@mestery.com wrote: Folks, I'd like to propose Assaf Muller to be a member of the Neutron core reviewer team. Assaf has been a long time contributor in Neutron, and he's also recently become my testing Lieutenant. His influence and knowledge in

Re: [openstack-dev] [Neutron][DB] neutron DB migration scripts

On Mon, May 25, 2015, Zang, Rui rui.z...@intel.com wrote: Greetings, Forgive my alembic ignorance. I am writing some vender specific code that wants to create new DB tables for neutron. I have read the neutron/db/migration/README file, but still have something unclear. My current

Re: [openstack-dev] [Neutron][DB] neutron DB migration scripts

On Mon, May 25, 2015, Mike Bayer mba...@redhat.com wrote: On 5/25/15 10:24 AM, Henry Gessau wrote: Yes, unfortunately the autogenerate currently generates commands to drop all the FWaaS, LBaaS and VPNaaS tables since their models are not in the neutron tree. You can and should delete all

Re: [openstack-dev] [nova][heat] sqlalchemy-migrate tool to alembic

On Fri, May 15, 2015, Mike Bayer mba...@redhat.com wrote: On 5/15/15 9:31 AM, Doug Hellmann wrote: This seems more complicated than needed. If we just stop writing the sqlalchemy-migrate scripts and don't change them, then for 1 cycle we have to run both sets of migrations and after that

Re: [openstack-dev] [Neutron] Extending database schema from 3rd-party plugin

Note: I missed this email because Neutron was misspelled in the subject. I have corrected it for this message. On Tue, May 12, 2015, Alexey I. Froloff ra...@raorn.name wrote: I am developing ML2 type/mech plugin for some very special environment. Because this environment is very special (using

Re: [openstack-dev] [neutron] [doc] what's happened to api documents?

On Mon, Apr 13, 2015, henry hly henry4...@gmail.com wrote: http://developer.openstack.org/api-ref-networking-v2.html The above api document seems lost most of the content, leaving only port, network, subnet? In the navigation bar on the left there is a link to the rest of the Neutron API,

Re: [openstack-dev] [neutron] Proposal to add Ihar Hrachyshka as a Neutron Core Reviewer

+1 !!! On Wed, Mar 04, 2015, Kyle Mestery mest...@mestery.com wrote: I'd like to propose that we add Ihar Hrachyshka to the Neutron core reviewer team. Ihar has been doing a great job reviewing in Neutron as evidence by his stats [1]. Ihar is the Oslo liaison for Neutron, he's been doing a

Re: [openstack-dev] [neutron] New version of python-neutronclient release: 2.3.11

The fix: https://review.openstack.org/157606 On Thu, Feb 19, 2015, Joe Gordon joe.gord...@gmail.com wrote: neutronclient is requiring a keystone client that is way too new for icehouse. 2.3.11 was released (And breaks with semver), but icehouse has a limit of 2.4. So global-requirements for

Re: [openstack-dev] [neutron] Changes to the core team

On Thu, Jan 15, 2015, Kyle Mestery mest...@mestery.com wrote: As part of the change, I'd like to propose Doug Wiegley as a new Neutron core reviewer. Doug has been actively reviewing code across not only all the Neutron projects, but also other projects such as infra. His help and work in the

Re: [openstack-dev] [Neutron] UniqueConstraint for name and tenant_id in security group

On Thu, Dec 11, 2014, Mark McClain m...@mcclain.xyz wrote: On Dec 11, 2014, at 8:43 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: I'm generally in favor of making name attributes opaque, utf-8 strings that are entirely user-defined and have no constraints on them. I

Re: [openstack-dev] [Neutron] IPv6 team summit meetup

Count me in. On 11/6/2014 4:18 PM, Xuhan Peng wrote: Hey, Since we don't have any slot for ipv6 in summit to meet up, can we have a lunch meetup together tomorrow (11/7 Friday)? We can meet at 12:30 at the meet up place Neuilly lobby of Le Meridien and go to lunch together after that.

[openstack-dev] [Neutron] Proposing to disallow updates of IPv6 attributes on subnets

A number of bugs[1][2][3] have been filed which are related to updating the IPv6 attributes after a subnet has been created. In the reviews[4][5] for the fixes for [1] and [2] some shortcomings and questions have been raised, which were discussed in today's IPv6 IRC meeting[6]. Summary: In Juno

Re: [openstack-dev] [Group-based Policy] Database migration chain

Clint Byrum cl...@fewbar.com wrote: Excerpts from Mike Bayer's message of 2014-10-04 08:10:38 -0700: On Oct 4, 2014, at 1:10 AM, Kevin Benton blak...@gmail.com wrote: Does sqlalchemy have good support for cross-database foreign keys? I was under the impression that they cannot be

[openstack-dev] [Neutron] IPv6 bug fixes that would be nice to have in Juno

There are some fixes for IPv6 bugs that unfortunately missed the RC1 cut. These bugs are quite important for IPv6 users and therefore I would like to lobby for getting them into a possible RC2 of Neutron Juno. These are low-risk fixes that would not jeopardize the stability of Neutron. 1.

Re: [openstack-dev] [Neutron][LBaaS] Migrations in feature branch

Eugene Nikanorov enikano...@mirantis.com wrote: Hi neutron and lbaas folks. Recently I briefly looked at one of lbaas proposed into feature branch. I see migration IDs there are lined into a general migration sequence. I think something is definitely wrong with this approach as

[openstack-dev] [Neutron][db] End of meetings for neutron-db

https://wiki.openstack.org/wiki/Meetings/NeutronDB The work on healing and reorganizing Neutron DB migrations is complete, and so we will no longer hold meetings. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] [all] Design Summit reloaded

On 8/27/2014 8:51 AM, Thierry Carrez wrote: better use of our 4 days Will the design space be available on the fifth day too? No need to schedule anything on that day (Day 0), but having the space available would be nice for ad hoc gatherings. ___

Re: [openstack-dev] [neutron][cisco] Cisco Nexus requires patched ncclient

Ihar Hrachyshka ihrac...@redhat.com wrote: Now, maybe putting the module into requirements.txt is an overkill (though I doubt it). In that case, we could be interested in getting the info in some other centralized way. Maru is of the opinion that it is overkill. I feel the same way, but I am

Re: [openstack-dev] [neutron][cisco] Cisco Nexus requires patched ncclient

On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote: as per [1], Cisco Nexus ML2 plugin requires a patched version of ncclient from github. I wonder: - - whether this information is still current; Please see: https://review.openstack.org/112175 But we need to do backports before updating the wiki.

Re: [openstack-dev] [neutron][cisco] Cisco Nexus requires patched ncclient

On 8/12/2014 1:53 PM, Ihar Hrachyshka wrote: On 12/08/14 17:12, Henry Gessau wrote: On 8/12/2014 10:27 AM, Ihar Hrachyshka wrote: as per [1], Cisco Nexus ML2 plugin requires a patched version of ncclient from github. I wonder: - - whether this information is still current; Please see

Re: [openstack-dev] [neutron] [third-party] Cisco NXOS is not tested anymore

On 8/12/2014 2:04 PM, Jeremy Stanley wrote: On 2014-08-12 16:35:18 + (+), Edgar Magana wrote: If this plugin will be deprecated in Juno it means that the code will be there for this release, I will expect to have the CI still running for until the code is completely removed from the

Re: [openstack-dev] [neutron] [third-party] Cisco NXOS is not tested anymore

On 8/11/2014 7:56 PM, Anita Kuno wrote: On 08/11/2014 05:46 PM, Henry Gessau wrote: Anita Kuno ante...@anteaya.info wrote: On 08/11/2014 05:05 PM, Edgar Magana wrote: Cisco Folks, I don't see the CI for Cisco NX-OS anymore. Is this being deprecated? I don't ever recall seeing

[openstack-dev] [Neutron] Addressing unit tests broken by random PYTHONHASHSEED

Please see this bug: https://launchpad.net/bugs/1348818 I innocently assigned myself to this bug for Neutron. However, there are a very large number of Neutron unit tests that are broken by random hash seeds. I think multiple people should work on fixing the tests. We don't want to have

Re: [openstack-dev] [Neutron] Addressing unit tests broken by random PYTHONHASHSEED

://review.openstack.org/#/c/109729/ This masks the errors by brute-forcing the hash to zero, which preserves current behaviour. If we want to (and we do, eventually) remove this work-around, then we need to fix all the broken test cases. The etherpad has all the details. On 4 August 2014 20:42, Henry

Re: [openstack-dev] [Neutron] [IPv6] Hide ipv6 subnet API attributes

Nir Yechiel nyech...@redhat.com wrote: Now with the Juno efforts to provide IPv6 support and some features (provider networks SLAAC, RADVD) already merged, is there any plan/patch to revert this Icehouse change [1] and make the 'ra_mode' and 'ipv6_address_mode' consumable? Thanks, Nir

[openstack-dev] [Neutron] [Spec freeze exception] Cisco Nexus ML2 driver feature work

I would like to request Juno spec freeze exceptions for the following, all of which add features to the ML2 driver for the Cisco Nexus family of switches. https://review.openstack.org/95834 - Provider Segment Support https://review.openstack.org/95910 - Layer 3 Service plugin The above two

  1   2   >