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

> On 16 Oct 2015, at 17:36, Salvatore Orlando wrote: > > This sounds like a pretty decent idea to me. Considering Neutron's patch > merge rate this activity should hopefully not take a consistent chunk of your > Friday. Actually, it does, if you consider other stable

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

> On 16 Oct 2015, at 13:02, Victor Stinner wrote: > > Le 15/10/2015 17:54, Joshua Harlow a écrit : >> I had this problem with deprecation versioning (the debtcollector >> library functions take a version="XYZ", removal_version="ABC" params, >> see >>

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

> On 16 Oct 2015, at 10:50, Takashi Yamamoto wrote: > > if i move fwaas tests from neutron to neutron-fwaas, [1] > is there easy way to run them together with the rest of neutron api tests > for gate-neutron-dsvm-api job? Before we jump in to reflect current gating

Re: [openstack-dev] [all][stable][release] 2015.1.2

> On 13 Oct 2015, at 21:56, Matt Riedemann wrote: > > > > On 10/13/2015 1:57 PM, Chuck Short wrote: >> Hi >> >> Im just in the last stages of release 2015.1.2. I dont think anything is >> stopping us from opening it up agian. The tabrlls have been created. So >> go

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hi Artur, thanks a lot for caring about upgrades! There are a lot of good points below. As you noted, surprisingly, we seem to have rolling upgrades working for RPC layer. Before we go into complicating database workflow by doing oslo.versionedobjects transition heavy-lifting, I would like us

[openstack-dev] [neutron][testing][all] fixtures 1.4.0 breaking py34 jobs

Hi all, just a heads up that today fixtures 1.4.0 broke neutron py34 gate [1] and we needed to patch some logging code to overcome it [2]. The failures were triggered by a patch that started to raise logging exceptions for incorrect format strings (which is fine), but it also started to raise

Re: [openstack-dev] We should move strutils.mask_password back into oslo-incubator

> On 08 Oct 2015, at 16:51, Matt Riedemann wrote: > > > > On 10/8/2015 9:25 AM, Jeremy Stanley wrote: >> On 2015-10-08 08:58:06 -0500 (-0500), Matt Riedemann wrote: >> [...] >>> I don't know how many operators are tracking patch releases of >>> dependencies on

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

Hi all, I’d like to introduce a new initiative around stable branches for neutron official projects (neutron, neutron-*aas, python-neutronclient) that is intended to straighten our backporting process and make us more proactive in fixing bugs in stable branches. ‘Proactive' meaning: don’t wait

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

> On 21 Oct 2015, at 05:14, Armando M. wrote: > > Hi folks, > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and I bow in awe. > > Jokes aside, I would like to announce HenryG as a new member of the Neutron >

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

-neutron-unplugged-track See you in Tokyo, Ihar > On 19 Oct 2015, at 11:03, Miguel Angel Ajo <mangel...@redhat.com> wrote: > > Rossella Sblendido wrote: >> Hello Artur, >> >> thanks for staring this thread. See inline please. >> >> On 10/15/2015

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

> On 14 Oct 2015, at 02:08, Zaro wrote: > > Hello All, > > The openstack-infra team would like to upgrade from our Gerrit 2.8 to > Gerrit 2.11. We are proposing to do the upgrade shortly after the > Mitaka summit. The main motivation behind the upgrade is to allow us > to

Re: [openstack-dev] [Neutron] Prepare for expiration bugs without activity

> On 06 Oct 2015, at 19:26, ZZelle wrote: > > Hi everyone, > > > As decided during last neutron meeting[1], we try to let Launchpad expire > outdated bugs. > > The status of every bug without activity in last year has been set to > Incomplete and their assignee/milestone

Re: [openstack-dev] The state of systemd _sd_notify & oslo.service in OpenStack

For neutron-server, we use notify type since very long time, ~ RDO Icehouse. https://github.com/openstack-packages/neutron/blob/rpm-master/neutron-server.service#L6 > On 13 Oct 2015, at 09:01, Thomas Goirand wrote: > > Hi, > > As oslo.service implements _sd_notify, I am

Re: [openstack-dev] Metadata via dhcp namespace not working for icehouse release

> On 09 Oct 2015, at 09:00, Pradeep kumar wrote: > > > Hii Guys, > I am trying to run Metadata via the DHCP namespace by following blog post > mentioned below: > > http://techbackground.blogspot.in/2013/06/metadata-via-dhcp-namespace.html > > Commands mentioned

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

> On 09 Oct 2015, at 11:42, Thierry Carrez wrote: > > Hello everyone, > > OpenStack has become quite big, and it's easier than ever to feel lost, > to feel like nothing is really happening. It's more difficult than ever > to feel part of a single community, and to

Re: [openstack-dev] [stable][horizon] adding stable reviewer

> On 09 Oct 2015, at 12:44, Matthias Runge wrote: > > Hello, > > who would be the person to talk to, to add a new reviewer to > horizon-stable-maint > > I would like Doug Fish aka drfish (on launchpad) added. > > Unfortunately, the fields on >

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

> On 09 Oct 2015, at 15:46, Jeremy Stanley <fu...@yuggoth.org> wrote: > > On 2015-10-09 13:51:39 +0200 (+0200), Ihar Hrachyshka wrote: > [...] >> Another IRC service that I find useful to encourage collaboration >> in teams is a karma bot. Something that would calcu

Re: [openstack-dev] [Neutron] Returning of HEAD files?

> On 09 Oct 2015, at 15:28, Anna Kamyshnikova > wrote: > > Some time ago we merged change [1] that removes HEADS file. Validation of > migration revisions using HEADS file was replaced with pep8. This allows us > to avoid merge conflicts that appeared every time a

[openstack-dev] [neutron][qos] how we get back into master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, as you probably know, QoS feature is on horizon for Liberty and uses a separate feature/qos branch. It's expected that after it's complete, the branch is merged back into master. Note that it will probably be the first (or the second, if

Re: [openstack-dev] [tox/pep8] different result between running tox and pep8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/10/2015 05:15 AM, Gareth wrote: Hi guys My problem looks simple: Running tox -e pep8, the result says ok, not pep8 mistakes. Running pep8 ., a lot of pep8 mistkes come out. But in your project's tox.ini, there isn't such a long

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Oh yes! It was a bit weird that Miguel, while owning a feature branch, did not have a say in what is merged there. Now it should be more in line with his actual position in the project. Good work, Miguel! On 07/06/2015 01:02 PM, Kevin Benton

Re: [openstack-dev] [packaging] how to deal with the rename of config files in neutron on upgrade?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/02/2015 06:35 PM, Matt Riedemann wrote: This change in neutron [1] renames the linuxbridge and openvswitch plugin config files. I'm familiar with the %config(noreplace) directive in rpm but I'm not sure if there is a special trick with

Re: [openstack-dev] [all][tests] Fix it friday! [mock failure in CI]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OK, we got 1.1.1 released today, and now gate is broken in some other wa y: ImportError: No module named funcsigs Apparently there is a missing dependency, or it fails to apply, in the package. I see jobs failing with it, as well as my local tox

[openstack-dev] [stable][neutron] How we handle Kilo backports

Hi all, as per [1] I imply that all projects under stable-maint-core team supervision must abide the stable policy [2] which limits the types of backports for N-2 branches (now it’s stable/kilo) to "Only critical bugfixes and security patches”. With that, I remind all stable core members

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

Sean Dague <s...@dague.net> wrote: On 11/13/2015 04:08 AM, Ihar Hrachyshka wrote: Armando M. <arma...@gmail.com> wrote: On 12 November 2015 at 20:24, Sean M. Collins <s...@coreitpro.com> wrote: On Thu, Nov 12, 2015 at 05:55:51PM EST, Ihar Hrachyshka wrote: I also believe t

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

Thierry Carrez wrote: Carl Baldwin wrote: - StableBranch page though requires that we don’t merge non-critical bug fixes there: "Only critical bugfixes and security patches are acceptable” Seems a little premature for Kilo. It is little more than 6 months old. Some

[openstack-dev] [stable][neutron] upper constraints for stable/liberty

Hi Sachi and all, I was recently looking into how stable/liberty branches are set for neutron in terms of requirements caps, and I realized that we don’t have neither version caps nor upper constraints applied to unit test jobs in stable/liberty gate. We have -constraints targets defined

Re: [openstack-dev] [neutron][upgrade] new 'all things upgrade' subteam

Artur wrote: Mon 15 UTC works for me too. Was there the first meeting on past Monday? Or are we starting on Monday 23rd November? We start next Monday (Nov 23th). Ihar __ OpenStack

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

Tony Breeds <t...@bakeyournoodle.com> wrote: On Wed, Nov 18, 2015 at 05:44:38PM +0100, Ihar Hrachyshka wrote: Hi all, as per [1] I imply that all projects under stable-maint-core team supervision must abide the stable policy [2] which limits the types of backports for N-2 branches (no

Re: [openstack-dev] [oslo] About logging-flexibility

On 28 Aug 2015, at 14:16, Fujita, Daisuke fuzita.dais...@jp.fujitsu.com wrote: Hi, Ihar and Dims Thank you for your reply. I uploaded new a patch-set which is a single patch for oslo.log I'd like you to do a code review. https://review.openstack.org/#/c/218139/ After this email,

Re: [openstack-dev] [neutron][sfc] Neutron stadium distribution and/or packaging

On 28 Aug 2015, at 14:08, Paul Carver pcar...@paulcarver.us wrote: Has anyone written anything up about expectations for how Big Tent or Neutron Stadium projects are expected to be installed/distributed/packaged? Seems like your questions below are more about extendability than e.g.

Re: [openstack-dev] mock 1.3 breaking all of Kilo in Sid (and other cases of this kind)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/26/2015 03:34 PM, Thomas Goirand wrote: On 08/25/2015 08:59 PM, Matt Riedemann wrote: On 8/25/2015 10:04 AM, Thomas Goirand wrote: On 08/25/2015 03:42 PM, Thomas Goirand wrote: Hi, [...] Anyway, the result is that mock 1.3 broke 9

Re: [openstack-dev] [oslo] About logging-flexibility

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/27/2015 11:56 AM, Davanum Srinivas wrote: Daisuke, It's very late for merging these patches for Liberty. Sorry, they will have to wait till M. We can talk more about it on next Monday's Oslo meeting. Please let us know and i'll add a

Re: [openstack-dev] [Neutron] How to add vendor specific db tables in neutron

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/27/2015 12:05 PM, bharath wrote: Hi, Liberty code freeze is September 1st. But i have to add a vendor specific table for liberty release . As Vendor specific alembic support in neutron is seems to be still under progress. Can i

Re: [openstack-dev] [Neutron] How to add vendor specific db tables in neutron

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/27/2015 10:36 AM, bharath wrote: Hi , I need to add a vendor specific db tables in neutron but vendor specific are no more allowed in the neutron. Tables need to be added to vendor repo itself. So i created alembic versioning in

Re: [openstack-dev] [Neutron] [horizon] Netaddr 0.7.16 and gate breakage

and we can explore the fix later. > > Regarding the stable releases, Horizon may also need the similar version cap > for what we did for Neutron. > I will check it. > > Akihiro > > 2015-08-31 20:54 GMT+09:00 Sean Dague <s...@dague.net>: > On 08/31/2015 06:48 AM,

Re: [openstack-dev] [neutron][gate] please stop approving patches until netaddr issue is solved

> On 31 Aug 2015, at 17:20, Kevin Benton wrote: > > Why would they reset the gate? Shouldn't they just fail the check test? I think if it has an old +1 vote it may consider the vote good enough to push the patch in the gate directly. Ihar signature.asc Description:

Re: [openstack-dev] [Neutron] Netaddr 0.7.16 and gate breakage

> On 31 Aug 2015, at 08:19, Kevin Benton wrote: > > Even if this version is fixed for valid_mac, it appears the netaddr authors > made the decision to make a backwards incompatible change WRT to the > 'broadcast' attribute on IPNetwork objects that have CIDRs of /31 and /32.

[openstack-dev] [neutron][gate] please stop approving patches until netaddr issue is solved

Hi all, I see neutron folks pushing more neutron patches into the gate. They are all doomed to fail until [1] is resolved. So please stop approving patches, we only make harm by resetting the gate, with no chance to pass it. PS: it is the same for all neutron stadium projects, so *aas and

Re: [openstack-dev] [neutron][sfc] Neutron stadium distribution and/or packaging

> On 31 Aug 2015, at 13:36, Neil Jerram wrote: > > Hi Kevin, > > I currently have an example of this kind of thing that I'm working on, and > I'd appreciate hearing your view on what is the best solution. > > My requirement was to change some of the command line

[openstack-dev] [neutron][db] reviewers: please mind the branch a script belongs to

Hi reviewers, several days ago, a semantically expand-only migration script was merged into contract branch [1]. This is not a disaster, though it would be a tiny one if a contract-only migration script would be merged into expand branch. Please make sure you know the new migration strategy

Re: [openstack-dev] How to run fw testcases which are recently moved from tempest to neutron.

> On 02 Sep 2015, at 17:37, bharath wrote: > > Hi , > > How to run FW testcases which are under neutron using tempest? > > If i am trying to list cases from tempest(sudo -u stack -H testr list-tests > neutron.api > ), its resulting to empty list > You would need to set

Re: [openstack-dev] [ptl][release] flushing unreleased client library changes

> On 04 Sep 2015, at 18:39, Doug Hellmann wrote: > > > PTLs, > > We have quite a few unreleased client changes pending, and it would > be good to go ahead and publish them so they can be tested as part > of the release candidate process. I have the full list of changes

Re: [openstack-dev] [Openstack-operators] [Neutron] Allowing DNS suffix to be set per subnet (at least per tenant)

> On 04 Sep 2015, at 08:14, Daniel Comnea wrote: > > Kevin, > > am i right in saying that the merge above was packaged into Liberty ? > > Any chance to be ported to Juno? > There is no chance a new feature will be backported to any stable branch, even Kilo. At least

Re: [openstack-dev] [neutron] PTL Non-Candidacy

> On 11 Sep 2015, at 23:12, Kyle Mestery wrote: > > I'm writing to let everyone know that I do not plan to run for Neutron PTL > for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan > recently put it in his non-candidacy email [1]. But it goes

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

> On 25 Sep 2015, at 16:44, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > Hi all, > > releases are approaching, so it’s the right time to start some bike shedding > on the mailing list. > > Recently I got pointed out several times [1][2] that I violate our co

Re: [openstack-dev] [all][stable][release][horizon] 2015.1.2

> On 28 Sep 2015, at 12:23, Matthias Runge <mru...@redhat.com> wrote: > > On 25/09/15 15:39, Ihar Hrachyshka wrote: > >> I see you have three people in the horizon-stable-maint team only. >> Have you considered expanding the team with more folks? In >> neutro

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

> On 30 Sep 2015, at 12:53, Miguel Angel Ajo <mangel...@redhat.com> wrote: > > > > Ihar Hrachyshka wrote: >>> On 30 Sep 2015, at 12:08, thomas.mo...@orange.com wrote: >>> >>> Hi Ihar, >>> >>> Ihar Hrachyshka : >>>&

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

> On 30 Sep 2015, at 12:08, thomas.mo...@orange.com wrote: > > Hi Ihar, > > Ihar Hrachyshka : >>> Miguel Angel Ajo : >>>> Do you have a rough idea of what operations you may need to do? >>> Right now, what bagpipe driver for networking-bgpvpn

Re: [openstack-dev] [all] Liberty release - what is the correct version - 2015.2.0, 8.0.0 or 12.0.0?

> On 01 Oct 2015, at 14:21, Thierry Carrez wrote: > > Jeremy Stanley wrote: >> On 2015-10-01 10:54:20 +1000 (+1000), Richard Jones wrote: >> [...] >>> I believe that if we are moving to semver, then 12.0.0 is >>> appropriate. >> >> Each project participating in the

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

> On 01 Oct 2015, at 15:45, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > Hi all, > > I talked recently with several contributors about what each of us plans for > the next cycle, and found it’s quite useful to share thoughts with others, > because you have

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

Hi all, I talked recently with several contributors about what each of us plans for the next cycle, and found it’s quite useful to share thoughts with others, because you have immediate yay/nay feedback, and maybe find companions for next adventures, and what not. So I’ve decided to ask

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

> On 01 Oct 2015, at 17:05, Kyle Mestery <mest...@mestery.com> wrote: > > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins <s...@coreitpro.com> wrote: > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > - more changes with less infra tinkering

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

> On 01 Oct 2015, at 17:42, Sean M. Collins <s...@coreitpro.com> wrote: > > On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote: >> On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins <s...@coreitpro.com> wrote: >> >>> On Thu, Oct 01, 2015 at 10:02:24

[openstack-dev] [all] -1 due to line length violation in commit messages

Hi all, releases are approaching, so it’s the right time to start some bike shedding on the mailing list. Recently I got pointed out several times [1][2] that I violate our commit message requirement [3] for the message lines that says: "Subsequent lines should be wrapped at 72 characters.”

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

> On 25 Sep 2015, at 14:37, thomas.mo...@orange.com wrote: > > Kevin, Miguel, > > I agree that (4) is what makes most sense. > (more below) > > Miguel Angel Ajo : >> Do you have a rough idea of what operations you may need to do? > > Right now, what bagpipe driver for networking-bgpvpn needs

Re: [openstack-dev] [all][stable][release] 2015.1.2

> On 25 Sep 2015, at 09:02, Matthias Runge wrote: > > On 25/09/15 00:17, Alan Pevec wrote: >>> For Horizon, it would make sense to move this a week back. We discovered >>> a few issues in Liberty, which are present in current kilo, too. I'd >>> love to cherry-pick a few of

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Yes, looks like option 4 is the best. We need an abstraction layer between extensions and agents, to make sure API makes sense for all AMQP based agents. Common agent framework that I think Sean side looks at [1] could partially define that agent interface for us. [1]:

Re: [openstack-dev] [Neutron] Defect management

> > On 05 Oct 2015, at 17:27, Armando M. <arma...@gmail.com> wrote: > > > > On 5 October 2015 at 03:14, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > On 02 Oct 2015, at 02:37, Armando M. <arma...@gmail.com> wrote: > > > > Hi neutrinos,

Re: [openstack-dev] [Neutron] Defect management

> On 06 Oct 2015, at 10:36, Miguel Angel Ajo wrote: > > Hi, I was trying to help a bit, for now, but I don't have access in launchpad > to update importance, > etc. > > I will add comments on the bugs themselves, and set a ? in the > spreadsheet. I believe you need to

Re: [openstack-dev] [Neutron] Defect management

> On 02 Oct 2015, at 02:37, Armando M. wrote: > > Hi neutrinos, > > Whilst we go down the path of revising the way we manage/process bugs in > Neutron, and transition to the proposed model [1], I was wondering if I can > solicit some volunteers to screen the bugs outlined

Re: [openstack-dev] [Neutron] AZ Support

> On 04 Oct 2015, at 19:21, Gary Kotton wrote: > > Sorry, it is not a result of the AZ support (humble apologies) > > It is a result of https://review.openstack.org/#/c/226362/ So you use DHCP agent with non-ml2 plugin, and it broke you. Do you think it’s ok for you to

Re: [openstack-dev] [Neutron] AZ Support

> On 05 Oct 2015, at 15:32, Gary Kotton <gkot...@vmware.com> wrote: > > > > On 10/5/15, 3:21 AM, "Ihar Hrachyshka" <ihrac...@redhat.com> wrote: > >>> On 04 Oct 2015, at 19:21, Gary Kotton <gkot...@vmware.com> wrote: >>> &

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

> On 06 Oct 2015, at 19:10, Thomas Goirand <z...@debian.org> wrote: > > On 10/01/2015 03:45 PM, Ihar Hrachyshka wrote: >> Hi all, >> >> I talked recently with several contributors about what each of us plans for >> the next cycle, and found it’s qui

Re: [openstack-dev] [neutron] Release Notes for *aaS projects

Kyle Mestery wrote: We're hoping to cut Neutron M-1 this week [1]. We have implemented release notes in the main Neutron repository [2] , but not in the *aaS repositories. At the time, I thought this was a good approach and we could collect all releasenotes there. But I

Re: [openstack-dev] [neutron][all] when can we drop XML support in neutronclient? Now?

Akihiro Motoki wrote: Hi, python-neutronclient still has XML support of Neutron API. I would like to discuss when we drop XML support in neutronclient. Neutron API XML suppoort was marked as deprecated in Icehouse and Juno and was dropped in Kilo. Juno is now EOL and we

Re: [openstack-dev] [Neutron] Bug deputy process

Armando M. wrote: Hi neutrinos, It's been a couple of months that the Bug deputy process has been in place [1,2]. Since the beginning of Mitaka we have collected the following statistics (for neutron and neutronclient): Total bug reports: 373 • Fix committed:

Re: [openstack-dev] [Neutron] Scaling our testing needs

Armando M. wrote: Hi Neutrinos, I would like to share a proposal with you on how we could scale our ever-growing testing needs, and at the same time, provide guidance to the developers who care about the quality of the work they produce, and how they can protect it

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

to see the design bashed hard before I start to put it into spec format. Especially if it’s not sane. :) Ihar Mathieu Rohon <mathieu.ro...@gmail.com> wrote: Thanks ihar! On Thu, Nov 19, 2015 at 2:32 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: UPD: now that we have some u

Re: [openstack-dev] [neutron] Purpose and documentation of the API

Sean M. Collins wrote: On Tue, Dec 01, 2015 at 07:16:00AM EST, Neil Jerram wrote: _What is important: the API, or documented use cases?_ Both are important - however I think I understand what you are trying to tease out. Being theoretically inclined, I tend to assume

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Kyle Mestery wrote: >> o) Workaround: >> >> After a vm is deployed on a (re)started compute node, restart taas >> agent before creating a tap-service or tap-flow. >> That is, create taas flows after cleanup has been done. >> >> Note that cleanup will

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Assaf Muller wrote: SFC are going to hit this issue as well. Really any out of tree Neutron project that extends the OVS agent and expects things to work :) Yes. SFC project is considered for l2 agent extensions mechanism, though we need to deliver in core first. AFAIK

Re: [openstack-dev] [neutron] How could an L2 agent extension access agent methods ?

Rossella Sblendido <rsblend...@suse.com> wrote: Hi Ihar, wow, good job!! Sorry for the very slow reply. I really like your proposal...some comments inline. On 12/03/2015 04:46 PM, Ihar Hrachyshka wrote: Hi, Small update on the RFE. It was approved for Mitaka, assuming we c

Re: [openstack-dev] [Sender Auth Failure] Re: [neutron] How could an L2 agent extension access agent methods ?

Margaret wrote: Hello Ihar, I have some comments and questions about your proposal. My apologies if any of what I say here results from misunderstandings on my part. Thanks a lot for the reply. I will try to clear up below. 1. I believe there are two

Re: [openstack-dev] [neutron][grenade] l3.filters fail to update at test server

Zong Kai YL Li wrote: >> Hi, all. >> I met a problem when I submitted a neutron l3 related patch, I updated >> l3.filters to add a rootwrap for command arp, but on test server, grenade >> seems doesn't update l3.filters, that cause gate-grenade-dsvm-neutron >> failed. >>

Re: [openstack-dev] [neutron]how to import neutron module file for other official project ?

P. Ramanjaneya Reddy wrote: Hi All, how to import neutron module file for other official project ? Consider import neutron-lib to be use.. https://github.com/openstack/neutron-lib/blob/master/neutron_lib/exceptions.py What needs to be modify in official project to

[openstack-dev] [neutron] Re: [gate] any project using olso.db test_migrations is currently blocked

Adding [neutron] tag since the subthread now discusses specifically neutron stuff. Ihar Hrachyshka <ihrac...@redhat.com> wrote: Carl Baldwin <c...@ecbaldwin.net> wrote: On Thu, Dec 17, 2015 at 5:29 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: I will update on Neut

Re: [openstack-dev] [gate] any project using olso.db test_migrations is currently blocked

Carl Baldwin <c...@ecbaldwin.net> wrote: On Thu, Dec 17, 2015 at 5:29 AM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: I will update on Neutron side of things since it seems I have some knowledge from the fields. So first, on resources: we have Sachi and lifeless from infra

Re: [openstack-dev] [Neutron][Tricircle]The process for adding networking-tricircle

Zhipeng Huang wrote: Hi Neutrinos, We the Tricircle team want to have a neutron-ovn like agent in Neutron for our networking management. Before we go into discussing tech details on how new subprojects are introduced, let me ask one question: have you actually

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

Soichi Shigeta wrote: Hi, We find a problem that neutron ovs-agent deletes taas flows. o) Problem description: Background: At Liberty, a bug fix to drop only old flows was merged to Neutron. When ovs-agent is restarted, the cleanup

Re: [openstack-dev] [Neutron][Tricircle]The process for adding networking-tricircle

joehuang wrote: Hi, Ihar, Is there any sub-project under Neutron stadium dealing with cross Neutron L2/L3 networking? If there is no one, why not introduce a new one. I believe I was misled by the suggestion of having a 'neutron-ovn like agent’. If you merely

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Akihiro Motoki wrote: [Packaging perspective] I am not sure how it affects. There is one concern as a package consumer. Getting additional packages through distro channels can be surprisingly difficult for new packages. :/ How neutron team can answer to this? I think

Re: [openstack-dev] The command "neutron-db-manage" of 8.0.0~b1 fails

Martinx - ジェームズ wrote: Guys, I'm trying to experiment Mitaka on Ubuntu Xenial, which already have beta version on its repositories, however, "neutron-db-manage" fails. Here is the output of it: http://paste.openstack.org/show/482920/ Any clue? I'm using the

Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

Matthias Runge wrote: Hello, did we had a recent change in stable tests for Kilo? Horizon tests for kilo are now failing due to a missing dependency to testrepository. Horizon never used testrepository (until recently, where I added testr support, but only in mitaka

Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

Matthias Runge <mru...@redhat.com> wrote: On Mon, Jan 04, 2016 at 12:29:27PM +0100, Ihar Hrachyshka wrote: Matthias Runge <mru...@redhat.com> wrote: testrepository Any suggestions here? Seems like pbr importing testrepository, hence the dependency belongs to pbr,

Re: [openstack-dev] The command "neutron-db-manage" of 8.0.0~b1 fails

Mike Bayer <mba...@redhat.com> wrote: On 01/04/2016 06:59 AM, Ihar Hrachyshka wrote: Martinx - ジェームズ <thiagocmarti...@gmail.com> wrote: Guys, I'm trying to experiment Mitaka on Ubuntu Xenial, which already have beta version on its repositories, however, "neutron-db-mana

Re: [openstack-dev] [Horizon][stable][tempest] Horizon|tempest kilo gate fails due to testrepository dependency

Matthias Runge <mru...@redhat.com> wrote: On Mon, Jan 04, 2016 at 01:32:53PM +0100, Ihar Hrachyshka wrote: Note that it’s keystone installation that fails, not horizon, and it seems that it’s for grenade (I see /opt/stack/new/keystone in the logs). I would expect keystone gate to be brok

Re: [openstack-dev] [Horizon][stable] Horizon kilo gate fails due to testrepository dependency

UPD: Turns out it breaks Liberty gate too, f.e. for Neutron. It’s interesting that it did not break the thing for e.g. Neutron master. Matthias Runge wrote: Hello, did we had a recent change in stable tests for Kilo? Horizon tests for kilo are now failing due to a

Re: [openstack-dev] in which function does neutronv2 assign IP address for instance?

张晨 wrote: hi everyone, i have a question for the neutron code in liberty: how does neutron assign IP address for instance? in nova.network, it seems that neutron sever gets a feasible ip from the DB pool, which looks like this:

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

e list, or flag it with some sort of specific flag, so, we humans could verify it does make sense to backport such bug, and if it actually meets the "backportable" guidelines. Kuvaja, Erno wrote: -Original Message- From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] Sent: Fr

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

Rossella Sblendido <rsblend...@suse.com> wrote: Hi, thanks Ihar for the etherpad and for raising this point. . On 12/18/2015 06:18 PM, Ihar Hrachyshka wrote: Hi all, just wanted to note that the etherpad page [1] with backport candidates has a lot of work for those who have

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

Ihar Hrachyshka <ihrac...@redhat.com> wrote: Rossella Sblendido <rsblend...@suse.com> wrote: Hi, thanks Ihar for the etherpad and for raising this point. . On 12/18/2015 06:18 PM, Ihar Hrachyshka wrote: Hi all, just wanted to note that the etherpad page [1] with backport ca

[openstack-dev] [neutron][upgrade] next meeting Jan 11th

Hi all, as per latest meeting discussion, we will have the next one Jan 11th. See you all next year! Ihar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [neutron][grenade] l3.filters fail to update at test server

Zong Kai YL Li wrote: Hi, all. I met a problem when I submitted a neutron l3 related patch, I updated l3.filters to add a rootwrap for command arp, but on test server, grenade seems doesn't update l3.filters, that cause gate-grenade-dsvm-neutron failed. Does anyone

Re: [openstack-dev] [gate] any project using olso.db test_migrations is currently blocked

Jeremy Stanley wrote: On 2015-12-16 13:59:55 -0700 (-0700), Carl Baldwin wrote: Is someone from Neutron actively helping out here? Need more? [...] I believe all of the jobs currently voting on changes proposed to the master branch of the openstack/neutron repo are using

Re: [openstack-dev] [stable] meeting time proposal

Matt Riedemann wrote: On 12/16/2015 2:45 PM, Mark McClain wrote: On Dec 16, 2015, at 2:12 PM, Matt Riedemann wrote: I'm not entirely sure what the geo distribution is for everyone that works on stable, but I know we have people

Re: [openstack-dev] [all] Time to increase our IRC Meetings infrastructure?

Thanks Tony for leading the effort. As you know, neutron-upgrades team (well, me) actually confused -alt/-2 thing, and I registered a meeting for -2. I am generally for adding more channels assuming they are used wisely (like: organizers check in advance they don’t overlap with related

Re: [openstack-dev] [Neutron][vpnaas] "SKIPPED: Neutron support is required" while running tox

bharath wrote: Hi, when running tox "sudo -u stack -H tox -e api neutron.tests.api.test_vpnaas_extensions" test cases are failing with Error " setUpClass (neutron.tests.api.test_vpnaas_extensions.VPNaaSTestJSON) ... SKIPPED: Neutron support is required" I even

Re: [openstack-dev] [stable][neutron] upper constraints for stable/liberty

Robert Collins <robe...@robertcollins.net> wrote: On 14 November 2015 at 02:53, Ihar Hrachyshka <ihrac...@redhat.com> wrote: Hi Sachi and all, I was recently looking into how stable/liberty branches are set for neutron in terms of requirements caps, and I realized that w

Re: [openstack-dev] [neutron][sfc] How could an L2 agent extension access agent methods ?

Andreas Scheuring wrote: Hi all, I wonder if this is somehow in conflict with the modular l2 agent approach I'm currently following up for linuxbridge, macvtap and sriov? - RFE: [1] - Frist patchset [2] I don't think so, but to be sure I wanted to raise it up. I

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