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

Anita Kuno 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 that as a name of a third party gerrit > account in my list[0], Edgar. > > Do you happen to have a link to a

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

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 wi

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

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

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

Ihar Hrachyshka 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 not involved much

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] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Dinner plans Anita tricked me into volunteering to be responsible for dinner arrangements during the sprint. :) My suggestion is to get away from our keyboards in the evenings and eat at a restaurant together. I look forward to socializing with fellow Openstack developers in a less code-centric e

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

Today's meeting is still at 1700UTC. Kyle agreed next week the meeting should be at an Asia-friendly time, and 2200UTC was voted for that. On Thu, Dec 12, at 5:36 am, Akihiro Motoki wrote: > Is the meeting time today 1700UTC? > I think this week meeting should be held at the original time to avoi

Re: [openstack-dev] [neutron] ML2 vlan type driver does not honor network_vlan_ranges

network_vlan_ranges is a 'pool' of vlans from which to pick a vlans for tenant networks. Provider networks are not confined to this pool. In fact, I believe it is a more common use-case that provider vlans are outside the pool so that they do not conflict with tenant vlan allocation. -- Henry On

Re: [openstack-dev] [oslo] memoizer aka cache

Top posting to point out that: In Python3 there is a generic memoizer in functools called lru_cache. And here is a backport to Python 2.7: https://pypi.python.org/pypi/functools32 That leaves Python 2.6. Maybe some clever wrapping in Oslo can make it available to all versions? On Thu, Jan 23,

Re: [openstack-dev] [neutron][ml2] Port binding information, transactions, and concurrency

Bob, this is fantastic, I really appreciate all the detail. A couple of questions ... On Wed, Feb 05, at 2:16 am, Robert Kukura wrote: > A couple of interrelated issues with the ML2 plugin's port binding have > been discussed over the past several months in the weekly ML2 meetings. > These effec

Re: [openstack-dev] [ceilometer] Unable to run unit test cases

On Sat, Feb 15, at 4:41 am, Akhil Sadashiv Hingane wrote: > > When I try to run the test cases for ceilometer, it fails with > > > > Traceback (most recent call last): > File "/usr/local/bin/tox",

Re: [openstack-dev] [Neutron][IPv6]

On Sat, Mar 01, at 0:46 am, Shixiong Shang wrote: > What should I do to fix these “tempest” failures? Any suggestions or > pointers are highly appreciated! Your patch depends on review 52983, which needs to rebase and update its migration script with the latest down revision. Then you need to up

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

On Thu, Dec 11, 2014, Mark McClain wrote: > >> On Dec 11, 2014, at 8:43 AM, Jay Pipes > > 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 consider the >> name to be

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

On Thu, Jan 15, 2015, Kyle Mestery 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 services split i

Re: [openstack-dev] [Neutron][FYI] Bookmarklet for neutron gerrit review

Have any of you javascript gurus respun this for the new gerrit version? Or can this now be done on the backend somehow? On Tue, Mar 04, at 4:00 pm, Carl Baldwin wrote: > Nachi, > > Great! I'd been meaning to do something like this. I took yours and > tweaked it a bit to highlight failed Jenk

[openstack-dev] [Neutron] Database migrations meeting at summit

Several developers are working on different aspects of Neutron DB migration. I thought it would be good to have a meeting at the summit where we can discuss the issues and come closer to converging on a solution. I was thinking maybe a time on Tuesday or Thursday afternoon would work. I have creat

Re: [openstack-dev] [Neutron] Database migrations meeting at summit

ssages to my test change requests for unconditional > migrations topic. It will help to understand what options I tried to > research in them. > > Regards, > Ann > > > On Thu, May 8, 2014 at 11:57 PM, Henry Gessau <mailto:ges...@cisco.com>> wrote: > > Several dev

[openstack-dev] [Neutron][DB] Weekly Meeting for DB migration sub-team

For Juno one of the most critical items in Neutron is the issue of broken DB migrations. Over the past few months some ad-hoc discussions have taken place. At the Atlanta summit some core team members and interested developers met at the Neutron pod and discussed the issue and what should be done a

Re: [openstack-dev] [Neutron][DB] Weekly Meeting for DB migration sub-team

On 5/21/2014 11:40 AM, Kyle Mestery wrote: > On Wed, May 21, 2014 at 10:12 AM, Henry Gessau wrote: >> For Juno one of the most critical items in Neutron is the issue of >> broken DB migrations. Over the past few months some ad-hoc discussions >> have taken place. At the Atl

Re: [openstack-dev] [all] Hide CI comments in Gerrit

On 5/26/2014 8:31 PM, Monty Taylor wrote: > On 05/25/2014 05:23 AM, Radoslav Gerganov wrote: >> Hi, >> >> I created a small userscript that allows you to hide CI comments in Gerrit. >> That way you can read only comments written by humans and hide everything >> else. I’ve been struggling for a lo

Re: [openstack-dev] [Neutron]net-create fail without definite segmentation_id

On 5/29/2014 4:41 AM, Xurong Yang wrote: > Hi, stackers > if i define provider when creating network, but no segmentation_id, > net-create fail. why not allocate segmentation_id automatically? > ~$ neutron net-create test --provider:network_type=vlan > --provider:physical_network=default > Invali

[openstack-dev] [Neutron][DB] DB migration weekly meeting today (Monday) at 1300 UTC

The Neutron DB migration refactor weekly meeting[1] has moved to 1300 UTC on Mondays. (I should have sent out this reminder earlier, sorry.) Please review the spec[2] to see the changes in the design since last week. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDB [2] https://review.openst

Re: [openstack-dev] [Neutron] Debugging Devstack Neutron with Pycharm

Gal Sagie wrote: > I am trying to debug devstack Neutron with Pycharm, i have found here > (https://wiki.openstack.org/wiki/NeutronDevelopment#How_to_debug_Neutron_.28and_other_OpenStack_projects_probably_.29) > > That i need to change the neutron server code to > this=>*eventlet.monkey_patch()* To

[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 http://lists.openstack.or

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

Eugene Nikanorov 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 feature-branch > components a

[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. Network

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

Clint Byrum 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 wrote: >> >>> Does sqlalchemy have good support for cross-database foreign keys? I was >>> under the impression that they cannot be implemented with the normal

[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 w

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 tha

[openstack-dev] [Neutron] Gap 0 (database migrations) closed!

I am happy to announce that the first (zero'th?) item in the Neutron Gap Coverage[1] has merged[2]. The Neutron database now contains all tables for all plugins, and database migrations are no longer conditional on the configuration. In the short term, Neutron developers who write migration script

Re: [openstack-dev] [Neutron] Gap 0 (database migrations) closed!

d in /neutron/db/migration/models/head.py. >> >> The second point in important for testing which I hope will be merged soon: >> https://review.openstack.org/76520. >> >> Regards, >> Ann >> >> >> >> On Wed, Jul 16, 2014 at 5:54 AM, Kyle Mester

[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 fea

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

Nir Yechiel 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 > > [1] https://

[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 multiple

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

ttps://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. > > >

Re: [openstack-dev] why is change not visible in git?

On Sat, Sep 14, at 11:34 am, Avi L wrote: > I did a git clone of python-novaclient but I do not see the changes > mentioned in https://review.openstack.org/#/c/13036/ . Jenkins says changes > have been merged to git repository and build successful. Yet I do not see > these changes when I look at

Re: [openstack-dev] [neutron] [ml2] devstack now defaults to the ML2 plugin

Richard, Please look at https://wiki.openstack.org/wiki/Neutron/ML2 If anything is unclear or doesn't work please follow up so we can tweak the wiki. -- Henry On Tue, Oct 01, at 9:33 pm Richard Woo (richardwoo2...@gmail.com) wrote: > Kyle, what is the proper way to configure ML2 plugin (I plan

Re: [openstack-dev] Distributed Virtual Router Discussion

On Wed, Oct 23, at 7:35 am, Sylvain Afchain wrote: > I'm interested as well. On our side we are working on this BP > https://blueprints.launchpad.net/neutron/+spec/l3-high-availability And might be good to revisit the Multi-host DHCP and L3 blueprint https://blueprints.launchpad.net/neutron/+spe

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

Lots of great info and discussion going on here. One additional thing I would like to mention is regarding PF and VF usage. Normally VFs will be assigned to instances, and the PF will either not be used at all, or maybe some agent in the host of the compute node might have access to the PF for so

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

; Thanks > --jyh > >> -Original Message- >> From: Henry Gessau [mailto:ges...@cisco.com] >> Sent: Tuesday, October 29, 2013 8:10 AM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [nova] [neutron] PCI pass-t

Re: [openstack-dev] [nova] [neutron] PCI pass-through network support

On Tue, Oct 29, at 5:52 pm, Jiang, Yunhong wrote: >> -Original Message- >> From: Henry Gessau [mailto:ges...@cisco.com] >> Sent: Tuesday, October 29, 2013 2:23 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-

Re: [openstack-dev] [nova] [neutron] #openstack IRC meeting UTC 1300 Friday on PCI pass-through network support

On Fri, Nov 01, at 8:45 am, Robert Li (baoli) wrote: > Let's have a meeting with the #openstack IRC channel at UTC 1300 Friday. Thanks for holding this meeting Robert, I think everyone found it useful. Minutes and log: http://eavesdrop.openstack.org/meetings/pci_passthrough_network/2013/pci_pa

Re: [openstack-dev] The future of run_tests.sh

On Mon, Jun 17, at 7:01 pm, Joe Gordon wrote: > Hi All, > > A patch to move the run_tests.sh script into oslo-incubator > (https://review.openstack.org/#/c/32736/), has brought up the bigger > question of what is the future of './run_tests.sh.' > > This seems like a topic that directly affects all

Re: [openstack-dev] "list=true" issue with the python client.- help

I have commented on the review with what I think the error is. On Mon, Jun 17, at 6:16 pm Vasudevan, Swaminathan (PNB Roseville) (swaminathan.vasude...@hp.com) wrote: > > Hi Folks, > > I need some help to resolve the issue high lighted below. > > I have configured for an attribute to accept a "lis

[openstack-dev] [Neutron] Help with database migration error

I have not worked with databases much and this is my first attempt at a database migration. I am trying to follow this Howto: https://wiki.openstack.org/wiki/Neutron/DatabaseMigration I get the following error at step 3: /opt/stack/quantum[master] $ quantum-db-manage --config-file /etc/quantum/q

Re: [openstack-dev] [Neutron] Help with database migration error

05 Hwy 52 N > Rochester, MN 55901-1407 > United States > > > > > > > From:Henry Gessau > To:OpenStack Development Mailing List > , > Date:07/02/2013 09:05 PM > Subject:[openstack-dev] [Neutron] Help with database migration erro

Re: [openstack-dev] Problem with how python-neutronclient deals with Neutron exceptions

I think approach #2 makes sense. I can take a stab at it, but I am not guaranteeing any delivery dates. Do you have a specific api/exception that you would like to test to see if the concept works for nova-api? The one bug you mention singles out associating a floating IP to a port. That might be

Re: [openstack-dev] [Neutron] - python-neutronclient build failing for latest code reviews

I asked on #openstack-infra and clarkb immediately identified it as a problem with cliff, and saw that the cliff folks have apparently already fixed it in cliff 1.4.3, which is now on the openstack.org pypi mirror so new gate jobs should start passing now. On Fri, Aug 16, at 7:34 pm, Ronak Shah w

Re: [openstack-dev] [Neutron] - python-neutronclient build failing for latest code reviews

On Fri, Aug 16, at 10:34 pm, Dean Troyer wrote: > On Fri, Aug 16, 2013 at 8:26 PM, Henry Gessau wrote: > > I asked on #openstack-infra and clarkb immediately identified it as a > problem with cliff, and saw that the cliff folks have apparently already > fixed it

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

-- Henry On Tue, Sep 10, at 5:38 pm, David Kang wrote: > > > - Original Message - >> From: "Russell Bryant" >> To: "David Kang" >> Cc: "OpenStack Development Mailing List" >> Sent: Tuesday, September 10, 2013 5:17:15 PM >> Subject: Re: [openstack-dev] [nova] [pci device passthroug

Re: [openstack-dev] [nova] [pci device passthrough] fails with "NameError: global name '_' is not defined"

For the "TypeError: expected string or buffer" I have filed Bug #1223874. On Wed, Sep 11, at 7:41 am, yongli he wrote: > 于 2013年09月11日 05:38, David Kang 写道: >> >> - Original Message - >>> From: "Russell Bryant" >>> To: "David Kang" >>> Cc: "OpenStack Development Mailing List" >>> Se

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. > There is an error when I run mi

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 these documents? I am

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 translation code to start. >

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 reviews (3rd place in the

[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 att

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

Thierry Carrez 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, Ireland on >>>

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 messed things up for the user.

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

Carl Baldwin wrote: > On Fri, Jun 3, 2016 at 2:26 PM, Henry Gessau wrote: >> 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

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 reference implementation and

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

p into separate _constants.py modules. But then I could argue that would proliferate the number of imports required for many repos. Gal Sagie wrote: > For example references to the various different agents which are an > implementation details to me > > On Wed, Jun 8, 2016 at 8:51 PM

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 voting python35 tests restri

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: http://paste.openstack.org/show/492384/ > > I update t

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 has been contributin

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 , and is working its > way throug

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

[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 usi

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 the documentation to RST

Re: [openstack-dev] [all] summit session recap - getting API Docs off WADL and into RST

Sean Dague wrote: > Part of the cross project session track - > https://etherpad.openstack.org/p/newton-api-docs-rst > > The first half of the session was spent going over the background issues > and the work so far. The TL;DR > > * We need to get off WADL, it's a dead spec, and it's use is inhi

Re: [openstack-dev] [Neutron] Gate failure

Armando M. wrote: > Hi folks, > > Due to [1], Neutron related jobs (api, and lbaas) are failing. Please hold > your +A button until the issue is resolved. > > Thanks, > Armando > > [1] https://review.openstack.org/#/c/256164/ That fix has merged, but now we have a new issue [2] in the api job

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 private methods. Unfort

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: > > The commit https://github.com/openstack/neutron/commit/5d53dfb8

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 company controllers.We

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 test. So after a test finishes

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

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

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

On Tue, Jul 07, 2015, Salvatore Orlando wrote: > > > On 7 July 2015 at 14:00, Paul Michali > wrote: > > Thanks Salvatore for the responses. See @PCM in-line... > > > > On Tue, Jul 7, 2015 at 6:14 AM Salvatore Orlando > wrote: > >

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

+1! On Wed, Jul 15, 2015, Carl Baldwin 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 has been a long

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 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 expertise has bee

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 IPv6 interface infor

[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 b

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

On Fri, Sep 25, 2015, Daniel Comnea wrote: > Great job Henry ! I had nothing to do with it! (See below.) > On Fri, Sep 25, 2015 at 6:47 PM, Henry Gessau <mailto:ges...@cisco.com>> wrote: > > It has been about three years in the making but now it is finally here. >

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 par

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

On Fri, May 15, 2015, Mike Bayer 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 we can jus

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

On Mon, May 25, 2015, Zang, Rui 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 understanding is that

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

On Mon, May 25, 2015, Mike Bayer 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 sh

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

+1 On Thu, May 28, 2015, Kyle Mestery 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 > testing will be cri

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 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 Neutron showing ex

[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] [neutron] Microversioning work questions and kick-start

On Thu, Jun 11, 2015, Salvatore Orlando 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 meeting > regularly,

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 wrote: > Hello all! > > As the Lieutenant of the built-in control plane[1], I wo

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 wrote: > Hello! > > As the Lieutenant of the built-in control plane[1], I would like Rossella > Sblendido to be a member of the

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 wrote: > As one of the Lieutenants [1] for the API and DB areas under the PTL, I would > like to

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

On Thu, Jul 02, 2015, Fawad Khaliq 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 migration can reside i

[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 wha

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

+1! On Mon, Jul 06, 2015, Kevin Benton 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 > improving the stab

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

Jeremy, a huge thanks for this fantastic reply! I have taken the liberty of copying your responses directly into Neutron's "contributing" guide: https://review.openstack.org/187267 I hope you don't mind. On Fri, Jul 03, 2015, Jeremy Stanley wrote: > On 2015-07-03 22:01:

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 PyPI :-( > > 0.18.0 f

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

6-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 >>>>> >>>>> 2 releases, 2 regr

  1   2   >