Re: [openstack-dev] [Neutron][L2GW] Mitaka release of L2 Gateway now available

> On 11 May 2016, at 22:05, Sukhdev Kapur wrote: > > > Folks, > > I am happy to announce that Mitaka release for L2 Gateway is released and now > available at https://pypi.python.org/pypi/networking-l2gw. > > You can install it by using "pip install networking-l2gw"

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

t;> Might 15:00 UTC work for others ? > > +1 for earlier > >> If not, well, I'll make do with log/emails/pads/gerrit interactions. >> >> -Thomas >> >> >> >> >>> -Original Message- >>> From: Cathy Zhang >>> Sent: Thursday,

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

WAT??? It was never supposed to be core only. Everyone is welcome! Sent from my iPhone > On 25 Apr 2016, at 11:56, Edgar Magana wrote: > > Would you extend it to ex-cores? > > Edgar > > > > >> On 4/25/16, 10:55 AM, "Kyle Mestery" wrote: >>

Re: [openstack-dev] [neutron] use hostname as nameserver when creating subnet

Sun zhengnan wrote: Hi all Can I use hostname as a nameserver when creating or updating a subnet? From API perspective, yes... I noticed that both ip and hostname are checked in neutron/api/attributes.py with _validate_nameservers. But only ip address is allowed in

Re: [openstack-dev] [stable][Openstack-stable-maint] Stable check of openstack/trove failed

Amrith Kumar wrote: The links being referenced in this email for the UNSTABLE outcomes appear to be missing. Also, I notice that a whole bunch of stable jobs failed around the same time. Would someone on stable-maint please confirm whether there was something

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: Hi everyone, We have room 400 at 3:10pm on Thursday available for discussion of the two topics. Another option is to use the common room with roundtables in "Salon C" during Monday or Wednesday lunch time. Room 400 at 3:10pm is a closed room

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

Ian Wells wrote: Right. Note that custom MTU works out of the box only starting from Mitaka. It's been in from at least Kilo (give or take a some bugfixes, it seems, all of which deserve backporting). It never worked as you would expect, though indeed a lot of

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

Akihiro Motoki <amot...@gmail.com> wrote: 2016-04-18 15:58 GMT+09:00 Ihar Hrachyshka <ihrac...@redhat.com>: Sławek Kapłoński <sla...@kaplonski.pl> wrote: Hello, What MTU have You got configured on VMs? I had issue with performance on vxlan network with standard MTU

Re: [openstack-dev] [neutron][kilo] - vxlan's max bandwidth

Sławek Kapłoński wrote: Hello, What MTU have You got configured on VMs? I had issue with performance on vxlan network with standard MTU (1500) but when I configured Jumbo frames on vms and on hosts then it was much better. Right. Note that custom MTU works out of the

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: I think there is no formal spec or anything, just some emails around there. That said, I don’t follow why it’s a requirement for SFC to switch to l2 agent extension mechanism. Even today, with SFC maintaining its own agent, there are no clear

Re: [openstack-dev] [neutron] work on Common Flow Classifier and OVS Agent extension for Newton cycle

Cathy Zhang wrote: Hi everyone, Per Armando’s request, Louis and I are looking into the following features for Newton cycle. · Neutron Common FC used for SFC, QoS, Tap as a service etc., · OVS Agent extension Some of you might know that we already

Re: [openstack-dev] [all] [devstack] command tox with error in mitaka

zhaolihuisky wrote: Hi everyone Install devstack by http://docs.openstack.org/developer/devstack/ Install tox by docs.openstack.org/project-team-guide/project-setup/python.html command 'tox', the error log: pip-missing-reqs runtests: PYTHONHASHSEED='952003835'

Re: [openstack-dev] [all] create periodic-ci-reports mailing-list

Matthew Treinish wrote: On Wed, Apr 13, 2016 at 10:59:10AM -0400, Emilien Macchi wrote: Hi, Current OpenStack Infra Periodic jobs do not send e-mails (only periodic-stable do), so I propose to create periodic-ci-reports mailing list [1] and to use it when our periodic

Re: [openstack-dev] [neutron] [API]Make API errors conform to the common error message without microversion

Xianshan wrote: Hi, Duncan & michael, Thanks a lot for your replies. Definitely I agree with you that the microversion is the best approach to solve the backwards compat, and the neutron is also going to adopt it [1]. But it will take a long time to totally introduce

Re: [openstack-dev] Does Neutron itself add VM ports to ovs?

张晨 wrote: Thx for the answer, i finally locate the implementation in nova.network.linux_net.create_ovs_vif_port but how could nova execute the ovs-vsctl for the compute-node hypervisor just in the control-node? Nova still runs nova-compute service on your

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

ending on I2a10a8f15cdd5a144b172ee44fc3efd9b95d5b7e I tried. Let's wait for the result. On Thu, Apr 7, 2016 at 8:02 PM, Hongbin Lu <hongbin...@huawei.com> wrote: > -Original Message----- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: April-07-16 12:04 PM > T

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

Kevin Benton wrote: I don't know if my vote counts in this area, but +1! What the gentleman said ^, +1. Ihar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [magnum][neutron] AttributeError: 'str' object has no attribute 'strftime'

Hongbin Lu wrote: Hi all, Magnum gate recently broke with error: “AttributeError: 'str' object has no attribute 'strftime'” (here is a full log [1]). I would like to confirm if there is a recent commit in Neutron that causes the breakage. If yes, a quick fix is

Re: [openstack-dev] [neutron][api] advanced search criteria

Hirofumi Ichihara <ichihara.hirof...@lab.ntt.co.jp> wrote: Hi Ihar, On 2016/04/05 7:57, Ihar Hrachyshka wrote: Hi all, in neutron, we have a bunch of configuration options to control advanced filtering features for API, f.e. allow_sorting, allow_pagination, allow_bulk, etc. Those o

Re: [openstack-dev] [neutron][api] advanced search criteria

Armando M. <arma...@gmail.com> wrote: On 4 April 2016 at 17:08, Jay Pipes <jaypi...@gmail.com> wrote: On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: - why do we even need to control those features with configuration options? can we deprecate and remove them? This would

[openstack-dev] [neutron][api] advanced search criteria

Hi all, in neutron, we have a bunch of configuration options to control advanced filtering features for API, f.e. allow_sorting, allow_pagination, allow_bulk, etc. Those options have default False values. In the base API controller class, we have support for both native

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Doug Wiegley <doug...@parksidesoftware.com> wrote: On Apr 4, 2016, at 10:22 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Armando M. <arma...@gmail.com> wrote: On 4 April 2016 at 09:01, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Hi all, I noticed that ofte

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Graham <graham.ha...@hpe.com> wrote: On 04/04/2016 17:11, Ihar Hrachyshka wrote: Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done to make sure that nothing known to be broke

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Armando M. <arma...@gmail.com> wrote: On 4 April 2016 at 09:01, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done

[openstack-dev] [neutron] -2'ing all patches on every gate breakage

Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done to make sure that nothing known to be broken land in merge gate until we fix the breakage on our side. While I share the goal of not

[openstack-dev] [neutron][stable] RDO needs stable/mitaka branches for subprojects WAS: Re: [Rdo-list] RDO Mitaka RC1 current status - testers requested

Haïkel <hgue...@fedoraproject.org> wrote: 2016-04-01 16:17 GMT+02:00 Ihar Hrachyshka <ihrac...@redhat.com>: Haïkel <hgue...@fedoraproject.org> wrote: Do we want to raise those issues to networking vendors? Do we have a list of what’s required from them for RDO? I

Re: [openstack-dev] [neutron]: Neutron naming legal issues

Alexander Kostrikov wrote: What about Netrone? That could be a good one but it may also be a violation: http://www.infomoby.et/en/profile/netrone_networks_plc/64213 One idea I had in my mind for a while is using some alternative alphabet for project naming.

Re: [openstack-dev] [All][Neutron] Improving development and review velocity - Is it time for a drastic change?

Shinobu Kinjo wrote: https://review.openstack.org/300271 This change would make sense. But will we have core reviewers election? Obviously no, since you won’t have a ‘core reviewer’ term now. But what we really want is having a separate offensive name for those

Re: [openstack-dev] [neutron]: Neutron naming legal issues

Akihiro Motoki wrote: IIRC 'Quantum' was renamed to 'Neutron' due to the trademark issue. I don't think reverting it to 'Quantum' resolves the issue. When we chose a new name, the foundation checked the legal/trademark issue, so I think it is better to contact the OpenStack

Re: [openstack-dev] [all] Austin Design Summit track layout

Thierry Carrez <thie...@openstack.org> wrote: Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself before the

Re: [openstack-dev] [all] Austin Design Summit track layout

Sylvain Bauza wrote: Le 29/03/2016 09:48, Thierry Carrez a écrit : Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's

Re: [openstack-dev] [neutron][nova][stable][sr-iov] Status of physical_device_mappings

Seems like the explanation below indeed suggests that’s a regression for Mitaka. We’ll track the bug for a backport. I don’t think that we can block the initial Mitaka release for that though. So let’s work on the master fix right now, and target the fix for Mitaka for one of the first minor

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

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 Honestly, you should avoid using the script, and instead rely on tox. With tox, requirements are properly constrained, so

Re: [openstack-dev] [neutron][stable] proactive backporting

Rossella Sblendido <rsblend...@suse.com> wrote: On 03/23/2016 05:52 PM, Ihar Hrachyshka wrote: Hey folks, some update on proactive backporting for neutron, and a call for action from subteam leaders. As you probably know, lately we started to backport a lot of bug fixes in latest

Re: [openstack-dev] [release] [pbr] semver on master branches after RC WAS Re: How do I calculate the semantic version prior to a release?

Doug Hellmann wrote: Excerpts from Alan Pevec's message of 2016-03-22 20:19:44 +0100: The release team discussed this at the summit and agreed that it didn't really matter. The only folks seeing the auto-generated versions are those doing CD from git, and they should

Re: [openstack-dev] [neutron][stable] proactive backporting

a matter of calling inside openstack/releases repo: ./tools/new_release.sh liberty neutron bugfix FYI I just posted a new Liberty release patch at: https://review.openstack.org/296608 Thanks for attention, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Ihar Hrachyshka <ihrac...@r

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

na...@vn.fujitsu.com wrote: Hi everyone, 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 you know any plan for this ? In the

Re: [openstack-dev] [neutron] CI jobs take pretty long, can we improve that?

Sean M. Collins wrote: Rossella Sblendido wrote: 2) multi-node jobs run for every patch set. Is that really what we want? They take pretty long. We could move them to a periodic job. I would rather remove all the single-node jobs. Nova has been moving to multinode jobs

Re: [openstack-dev] [neutron] report from Brno code sprint, Mar 14-16

Doug Wiegley wrote: Is our live upgrade strategy going to be labeled “reference only”? Not really. But since a typical neutron setup contains of components that belong to different subprojects and repos, the assumption would be that you will need every

Re: [openstack-dev] [neutron] report from Brno code sprint, Mar 14-16

Doug Wiegley wrote: What is the plan for out of tree objects derived from neutron, and out of tree projects that are using the current neutron objects? Specifically, the ones which *can’t* use the REST API, because they’re for something loaded directly into

Re: [openstack-dev] [neutron] report from Brno code sprint, Mar 14-16

Sean M. Collins <s...@coreitpro.com> wrote: Ihar Hrachyshka wrote: One thing that we discussed on the event is updating networking-guide with detailed description of the upgrade process for neutron. We already have some pieces scattered there [f.e. we have some coverage for neutron-db-

Re: [openstack-dev] [stable] Proposing Tony Breeds for stable-maint-core

Matt Riedemann wrote: I'd like to propose tonyb for stable-maint-core. Tony is pretty much my day to day guy on stable, he's generally in every stable team meeting (which is not attended well so I appreciate it), and he's as proactive as ever on staying on top

Re: [openstack-dev] [neutron] Upgrading from Kilo to Liberty, missing database entries

Nolan Brubaker wrote: Hello, Recently when testing neutron upgrades for openstack-ansible, I ran into an existing bug [1] where the networksecuritybindings and portsecuritybindings tables were not populated after an upgrade from Kilo to Liberty. Updating

[openstack-dev] [neutron] report from Brno code sprint, Mar 14-16

Hi all, Just giving my fellows an update from the event where we gathered our upgrades subteam to plan for Newton and do some coding. == We had folks from multiple companies participating in the event (Red Hat, SuSE, Intel, IBM). We also had some folks joining us online. Thanks everyone

Re: [openstack-dev] [Neutron] Ironing out outstanding issues in time for RC1

Armando M. wrote: Neutrinos, We have about ~20 outstanding bugs marked Medium/High/Critical, and we have only one or two days left to have a chance to get them in the gate queue [1]. Can I trouble you to go and make sure patches are up to date and well reviewed?

Re: [openstack-dev] [Neutron] Ihar as *-aas core reviewer

Sean M. Collins wrote: I probably speak for all FwaaS cores when I say - "Welcome!” …back! Thanks. Frankly I had just assumed he had core privileges for our repo anyway via an inherited ACL. Full disclosure: I had all -*aas core privileges before [not thru inherited

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

Henry Gessau wrote: 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

Re: [openstack-dev] [neutron][oslo]neutron agent not receiving callback

Vikash Kumar wrote: On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar wrote: I have written a sample neutron agent which subscribe for the AFTER_CREATE event of router. I have defined a sample method as callback, but the

[openstack-dev] [neutron] no upgrades meeting on March 14

Hi all, a lot of subteam folks will take part in the code sprint in Brno next Mon-Wed, so we’ll cancel the next meeting. Next meeting will occur March 21. Ihar __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron] constrained tox targets

Armando M. <arma...@gmail.com> wrote: On 4 March 2016 at 08:50, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Hi all, currently we have both py27 and py27-constraints tox targets in neutron repos. For some repos (neutron) they are even executed in both master and stable/liber

[openstack-dev] [neutron] constrained tox targets

Hi all, currently we have both py27 and py27-constraints tox targets in neutron repos. For some repos (neutron) they are even executed in both master and stable/liberty gates. TC lately decided that instead of having separate targets for constrained requirements, we want to have

Re: [openstack-dev] [all][i18n] Liaisons for I18n

Tony Breeds wrote: On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote: If you are interested to be a liaison and help translators, input your information here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n . So

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

Salvatore Orlando <salv.orla...@gmail.com> wrote: On 3 March 2016 at 10:38, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Kevin Benton <ke...@benton.pub> wrote: Hi, I know this has come up in the past, but some folks in the infra channel brought up the topic of ch

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

Kevin Benton wrote: * Neutron cannot be trusted to do what it says it's doing with the security groups API so users want to orchestrate firewalls directly on their instances. If that’s really a reason for someone, then they should just use ’noop' firewall_driver. Or

Re: [openstack-dev] [neutron] - Changing the Neutron default security group rules

Kevin Benton wrote: Hi, I know this has come up in the past, but some folks in the infra channel brought up the topic of changing the default security groups to allow all traffic. They had a few reasons for this that I will try to summarize here: * Ports 'just work'

Re: [openstack-dev] [Openstack-operators] [neutron] network issue with separate subnets under single public-network

Rahul Sharma wrote: Hi All, I am trying to fix a network-issue in our environment and would like to know some suggestions on how I can achieve it. Here is the issue:- I have two subnets(10.10.10.0/25 and 10.10.10.128/26) with separate gateways for each subnet

[openstack-dev] [Neutron] Team meeting this Tue at 1400 UTC

Hi neutrinos, A kind reminder for this week's meeting. More on the agenda [1]. Cheers, Ihar [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development

Re: [openstack-dev] [Neutron][ml2][Manila] API to query segments used during port binding

Fixed neutron tag in the subject. Marc wrote: Hi Neutron team, I am currently working on a feature for hierarchical port binding support in Manila [1] [2]. Just to give some context: In the current implementation Manila creates a neutron port but let it unbound (state

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

Armando M. <arma...@gmail.com> wrote: On 22 February 2016 at 04:56, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Sean M. Collins <s...@coreitpro.com> wrote: Armando M. wrote: Now that the blocking issue has been identified, I filed project-config change [1] to enable us t

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

Sean M. Collins wrote: Also, what do we do with non-partial flavour of the job? Is it staying? Is it useful? I think operators are more likely to upgrade components of a cluster incrementally - so the partial jobs are going to reflect the reality on the ground better.

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade - Nova metadata failure

Sean M. Collins wrote: Armando M. wrote: Now that the blocking issue has been identified, I filed project-config change [1] to enable us to test the Neutron Grenade multinode more thoroughly. [1] https://review.openstack.org/#/c/282428/ Indeed - I want to profusely

Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

Jian Wen wrote: I don't think it's enough for a large scale cloud. When the neutron server is not available and the flow rules are gone, we need the backup to restore the flow rules. Flows should not be reset when neutron-server is down. If that’s the case,

Re: [openstack-dev] [QA][Tempest]Run only multinode tests in multinode jobs

Assaf Muller wrote: On Tue, Feb 16, 2016 at 2:52 PM, Matthew Treinish wrote: On Tue, Feb 16, 2016 at 10:07:19AM +0100, Jordan Pittier wrote: Hi list, I understood we need to limit the number of tests and jobs that are run for each Tempest patch

Re: [openstack-dev] [stable][i18n] What is the backport policy on i18n changes?

Thierry Carrez wrote: Matt Riedemann wrote: I don't think we have an official policy for stable backports with respect to translatable string changes. I'm looking at a release request for ironic-inspector on stable/liberty [1] and one of the changes in that has

Re: [openstack-dev] [neutron] Backup port info to restore the flow rules

Jian Wen wrote: Hello, If we restart OvS/ovs-agent when one or more of Neutron, MySQL and RabbitMQ is not available, the flow rules in OvS will be gone. If Neutron/MySQL/RabbitMQ doesn't become available in time, the VMs will lose their network connections. It's not easy

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

Salvatore Orlando wrote: On 11 February 2016 at 20:17, John Belamaric wrote: On Feb 11, 2016, at 12:04 PM, Armando M. wrote: On 11 February 2016 at 07:01, John Belamaric wrote: It is

Re: [openstack-dev] [all] tenant vs. project

Sean Dague wrote: Ok... this is going to be one of those threads, but I wanted to try to get resolution here. OpenStack is wildly inconsistent in it's use of tenant vs. project. As someone that wasn't here at the beginning, I'm not even sure which one we are supposed to be

Re: [openstack-dev] [all][tc] Proposal: Separate design summits from OpenStack conferences

Eoghan Glynn wrote: [...] * much of the problem with the lavish parties is IMO related to the *exclusivity* of certain shindigs, as opposed to devs socializing at summit being inappropriate per se. In that vein, I think the cores party sends the wrong

Re: [openstack-dev] [Openstack][Neutron][Monasca]

Rubab Syed wrote: Hi, I'm doing a university project in OpenStack. The aim is to monitor virtual routers per tenant with Monasca(which according to my knowledge hasn't been implemented yet). The initial features would include monitoring of in/out traffic per

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

Salvatore Orlando wrote: The difference lies in the process in my opinion. If the switch is added into the migration path then we will tell operators when to switch. I was suggesting doing it manual because we just don't know if every operator is happy about doing

Re: [openstack-dev] [neutron][tempest] No metadata route in test_dualnet* family

Evgeny Antyshev <eantys...@virtuozzo.com> wrote: On 02/11/2016 01:48 PM, Ihar Hrachyshka wrote: Evgeny Antyshev <eantys...@virtuozzo.com> wrote: Hello! I need an advice from someone familiar with how Neutron configures Metadata routes for created subnets. Below, I presume

Re: [openstack-dev] [neutron][tempest] No metadata route in test_dualnet* family

Evgeny Antyshev wrote: Hello! I need an advice from someone familiar with how Neutron configures Metadata routes for created subnets. Below, I presume you enabled isolated metadata in DHCP agent. We run tempest in such an environment that all ssh keys,

Re: [openstack-dev] [gate] RFC dropping largeops tests

Sean Dague wrote: The largeops tests at this point are mostly finding out that some of our new cloud providers are slow - http://tinyurl.com/j5u4nf5 This is fundamentally a performance test, with timings having been tuned to pass 98% of the time on two clouds that were very

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Sean M. Collins <s...@coreitpro.com> wrote: Ihar Hrachyshka wrote: UPD: seems like enforcing instance mtu to 1400 indeed makes us pass forward into tempest: http://logs.openstack.org/59/265759/3/experimental/gate-grenade-dsvm-neutron-multinode/a167a59/console.html And there are only

Re: [openstack-dev] [neutron][stable] Request to do stable point releases more often if there are going to be a lot of backports

Matt Riedemann wrote: While reviewing the neutron 7.0.2 stable/liberty point release, I noticed there were a lot of changes since 7.0.1. [1] There are 48 non-merge commits by my count. While there is no rule about how many backports should land before we cut a

Re: [openstack-dev] [neutron] documenting configuration option segregation between services and agents

Kevin Benton wrote: Propose it as a devref patch! +1. Has it happened already? On Wed, Jan 27, 2016 at 12:30 PM, Dustin Lundquist wrote: We should expand services_and_agents devref to describe how and why configuration options should be

Re: [openstack-dev] [neutron][neutron-*] Notice! pylint breakage

Gareth wrote: Thanks for all! However I'm developing on stable/liberty and it failed with running "tox -e pep8" because of this issue. And I found it is pylint==1.4.5 on master branch. Could we cherry-pick this test-requirements update back to stable/liberty? Try

[openstack-dev] [neutron] upgrades/objects code sprint in Brno

Hi neutrinos, as per latest Neutron upgrades subteam discussion, we start to plan for a code sprint to push forward remaining M/early N bits for upgrades story. The main topic of the sprint will be the objectification of the core codebase (ports, networks, subnets…) though other upgrade

Re: [openstack-dev] [Neutron][L3] Orphaned process cleanup

Sean M. Collins wrote: Hi, I started poking a bit at https://bugs.launchpad.net/devstack/+bug/1535661 We have radvd processes that the l3 agent launches, and if the l3 agent is terminated these radvd processes continue to run. I think we should probably terminate them

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Armando M. wrote: On 20 January 2016 at 08:20, Edgar Magana wrote: Just providing support for Kyle’s proposal! It is working very well for other teams such as nova, docs between others. At risk of stating the obvious, not every project is equal,

Re: [openstack-dev] [nova][neutron] Update on Neutron's rolling upgrade support?

Jay Pipes wrote: Hey Sean, Tomorrow morning UTC, we'll be discussing Neutron topics at the Nova mid-cycle. Wondering if you might give us a quick status update on where we are with the Neutron devstack grenade jobs and what your work has uncovered on the Neutron side

Re: [openstack-dev] [Neutron] Removing ml2_type_vxlan.vxlan_group parameter?

Andreas Scheuring wrote: There was some discussion if the ml2_type_vxlan.vxlan_group of the ml2 config file (Neutron Server) can be removed [1], as it is not being used by in-tree drivers (ovs, lb, sriov). OVS: does not support vxlan mcast LB: uses it's own agent

Re: [openstack-dev] [Neutron] [Docs] Definition of a provider Network

Andreas Scheuring wrote: Hi everybody, I stumbled over a definition that explains the difference between a Provider network and a self service network. [1] To summarize it says: - Provider Network: primarily uses layer2 services and vlan segmentation and cannot

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Rossella Sblendido wrote: On 01/19/2016 04:36 PM, Miguel Angel Ajo Pelayo wrote: Thinking of this, I had another idea, a bit raw yet. But how does it sound to have two meetings a week, one in a EU/ASIA friendlier timezone, and another for USA/AU (current one), with

Re: [openstack-dev] [nova][neutron][upgrade][devstack] Grenade multinode partial upgrade

Sean M. Collins wrote: Nice find. I actually pushed a patch recently that we should be advertising the MTU by default. I think this really shows that it should be enabled by default. https://review.openstack.org/263486l -- Sent from my Android device with K-9 Mail.

Re: [openstack-dev] [stable] kilo 2015.1.3 freeze exception request for cve fixes

+1. CVE fixes obviously should be granted an exception. Matt Riedemann wrote: We should get this series in for nova in the kilo 2015.1.3 release: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/kilo+topic:bug/1524274 -- Thanks,

Re: [openstack-dev] [nova][stable] Proposal to add Tony Breeds to nova-stable-maint

Matt Riedemann wrote: I'm formally proposing that the nova-stable-maint team [1] adds Tony Breeds to the core team. I don't have a way to track review status on stable branches, but there are review numbers from gerrit for stable/liberty [2] and stable/kilo

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

UPD both fixes merged, should now be safe to recheck neutron patches. Doug Wiegley wrote: This fix failed to merge, due to a new regression in how another job is using dib. Here's a non voting patch for that, until it gets debugged:

Re: [openstack-dev] [neutron] Testing Neutron with latest OVS

Sean M. Collins wrote: On Wed, Jan 13, 2016 at 03:57:37PM CST, Mooney, Sean K wrote: One of the ideas that I have been thinking about over the last month or two is do we Want to create a dedicated library file in devstack to support compilation and installation Of ovs.

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Tony Breeds <t...@bakeyournoodle.com> wrote: On Tue, Jan 12, 2016 at 01:27:30PM +0100, Ihar Hrachyshka wrote: Agreed with Gary on behalf of my European compatriots. (Note that I *personally* +1’d the patch because I don’t mind, doing late hours anyway; but it’s sad it was ninja merged w

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Kevin Benton wrote: The issue with this data is that who says something is not a good metric. For example, this shows that I attended more than twice as many afternoon meetings as the morning meetings when I know I actually only missed a couple of morning ones. I just

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

anyone else wants to crunch it. Thanks, doug On Jan 12, 2016, at 4:32 PM, Tony Breeds <t...@bakeyournoodle.com> wrote: On Tue, Jan 12, 2016 at 01:27:30PM +0100, Ihar Hrachyshka wrote: Agreed with Gary on behalf of my European compatriots. (Note that I *personally* +1’d the patch because

Re: [openstack-dev] [trove][neutron][cinder][swift][ceilometer][nova][keystone][sahara][glance][neutron-lbaas][imm] stylistic changes to code, how do we handle them?

Amrith Kumar wrote: I've tagged this message with the projects impacted by a series of change sets: [trove] https://review.openstack.org/#/c/266220/ [neutron] https://review.openstack.org/#/c/266156/1 [cinder]

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

cadence was: > > 12-15-2015: Tuesday > 12-21-2015: Monday > 12-29-2015: Tuesday (skipped) > 01-04-2016: Monday (skipped) > 01-12-2016 Tuesday > > The meeting is tomorrow. > > [1] http://eavesdrop.openstack.org/meetings/networking/2015/ >> >>

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Clark Boylan wrote: On Mon, Jan 11, 2016, at 12:35 PM, Sean M. Collins wrote: Nice find. I actually pushed a patch recently that we should be advertising the MTU by default. I think this really shows that it should be enabled by default.

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Ihar Hrachyshka <ihrac...@redhat.com> wrote: Sean M. Collins <s...@coreitpro.com> wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion is showing that we are actually connecting to

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

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/5d53dfb8d64186- b5b1d2f356fbff8f222e15d1b2 may break the decomposed plugins that make use of the

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Sean M. Collins wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion is showing that we are actually connecting to the instance successfully. We get the dropbear SSH banner, but

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Ihar Hrachyshka <ihrac...@redhat.com> wrote: Ihar Hrachyshka <ihrac...@redhat.com> wrote: Sean M. Collins <s...@coreitpro.com> wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Armando M. wrote: Hi neutrinos, A kind reminder for tomorrow's meeting at 1400UTC. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for

<    1   2   3   4   5   6   7   8   9   10   >