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 on above link for debugging o/p

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 celebrate little successes > an

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 > https://review.openstack.org/#/admin/groups/537,me

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 stable branches unless there is a

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

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 unset in order to le

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

> On 06 Oct 2015, at 19:10, Thomas Goirand 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 quite useful to share thoughts

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 be a member of one of th

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

> > On 05 Oct 2015, at 17:27, Armando M. wrote: > > > > On 5 October 2015 at 03:14, Ihar Hrachyshka wrote: > > On 02 Oct 2015, at 02:37, Armando M. wrote: > > > > Hi neutrinos, > > > > Whilst we go down the path of revising the way we manage

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

> On 05 Oct 2015, at 15:32, Gary Kotton wrote: > > > > On 10/5/15, 3:21 AM, "Ihar Hrachyshka" wrote: > >>> On 04 Oct 2015, at 19:21, Gary Kotton wrote: >>> >>> Sorry, it is not a result of the AZ support (humble apologies) >>>

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 change the RPC topic 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 in [2]. It's only 24

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

> On 01 Oct 2015, at 17:42, Sean M. Collins 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 wrote: >> >>> On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: >>>>

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

> On 01 Oct 2015, at 17:05, Kyle Mestery wrote: > > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins wrote: > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > - more changes with less infra tinkering! neutron devs should not need to > > go to infra proj

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

> On 01 Oct 2015, at 15:45, 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 quite useful to share thoughts with others, > because you have immediate yay/nay feedback, and

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

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 release is following semver >

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

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

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][stable][release][horizon] 2015.1.2

> On 28 Sep 2015, at 12:23, Matthias Runge 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 >> neutron, we have five pe

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

> On 25 Sep 2015, at 16:44, Ihar Hrachyshka 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 commit > message requiremen

[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.” I

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 them to kilo. >> >> Wh

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 t

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]: https://review.openstack

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 further than that > for me.

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 for > each project below,

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 in upstream. Ihar sign

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 OS_TEST_PATH too for t

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

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: Message signed with OpenPG

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

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 : > On 08/31/2015 06:48 AM, Ihar Hrachyshka wrote: > >> On 31 Aug 20

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

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 options with which the > DHCP

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. > This means that

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

> On 28 Aug 2015, at 14:08, Paul Carver 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. packaging. > In

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

> On 28 Aug 2015, at 14:16, Fujita, Daisuke > 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, I'd like to add you

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

Re: [openstack-dev] [neutron] How to make deb and rpm packages for a networking-* project?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/24/2015 05:13 PM, Neil Jerram wrote: > Can anyone recommend how best to make deb and rpm packages for a > networking-* project? For RPMs, I encourage you to join RDO community and start from sending a package for Delorean. The docs for the st

Re: [openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/14/2015 05:25 PM, Russell Bryant wrote: > While this includes me, I'm really not taking this personally. > I'm thinking about it in the general sense. Thanks, and sorry for the thread, but I felt that we should clarify the matter asap if the n

Re: [openstack-dev] [neutron] extension implemented by multiple plugins

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/19/2015 10:54 AM, Bence Romsics wrote: > Hi, > > I'm not sure I need it. :-) > > My first idea was, that if two plugins implement an extension > together (neither the new first class resource, nor the new port > attributes is a usable feature

Re: [openstack-dev] [neutron] extension implemented by multiple plugins

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/18/2015 03:11 PM, Bence Romsics wrote: > Hi Ihar, > > Thank you. Just rebased my patch and following the example of the > qos feature now I can start neutron-server with both the service > plugin and the ml2 extension driver loaded. However I

Re: [openstack-dev] [neutron][qos] request to merge feature/qos back into master

wait until Fri and then merge. We had a git conflict on Fri though, so today I respin the patch again, hoping that it will either get more reviews or it's merged before we hit another conflict that can be inflicted by any new db migration. Ihar On 08/12/2015 09:55 PM, Ihar Hrachyshka

Re: [openstack-dev] [neutron] extension implemented by multiple plugins

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/17/2015 04:35 PM, Bence Romsics wrote: > Hi All, > > How do I implement one extension by two plugins? > > If I extend the API by: * a first class resource, and * attributes > to an already existing resource (the port resource in my case). >

[openstack-dev] [neutron][vmware][stable] vmware-nsx has no releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi VmWare folks, I wonder whether we can get some actual release tags for stable/kilo branch of the repo. Lack of any consumable tarballs does not help packagers that want to just get the tarball from pypi and use it as a base. I tried to follow th

[openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thanks a lot for the reply! I think it raises some good points here that I would like to clarify with other team members. I don't think those should interface with the current nomination run, so I spin it into a separate thread. Some comments inline

Re: [openstack-dev] [qa][devstack][keystone] Updating devstack to Identity V3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/14/2015 08:15 AM, Jamie Lennox wrote: > Hi all, > > I've been pushing for a while now to convert devstack to completely > use the identity v3 API as we try to deprecate the v2.0 API. > Currently all the functions in functions-common consume th

Re: [openstack-dev] [neutron] Liberty-3 BPs and gerrit topics

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/11/2015 03:44 PM, Kyle Mestery wrote: > Folks: > > To make reviewing all approved work for Liberty-3 in Neutron > easier, I've created a handy dandy gerrit dashboard [1]. What will > make this even more useful is if everyone makes sure to set

Re: [openstack-dev] [neutron][qos] request to merge feature/qos back into master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/13/2015 06:54 AM, Andreas Jaeger wrote: > On 08/12/2015 09:55 PM, Ihar Hrachyshka wrote: >> Hi all, >> >> with great pleasure, I want to request a coordinated review for >> merging feature/qos branch b

[openstack-dev] [neutron][qos] request to merge feature/qos back into master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, with great pleasure, I want to request a coordinated review for merging feature/qos branch back to master: https://review.openstack.org/#/c/212170/ Since it's a merge patch, gerrit fails to show the whole diff that it introduces into maste

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/12/2015 03:45 PM, 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

Re: [openstack-dev] [neutron][qos][ml2] extensions swallow exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/04/2015 08:41 PM, Robert Kukura wrote: > The process_[create|update]_() extension driver methods > are intended to validate user input. Exceptions raised by these > need to be returned to users so they know what they did wrong. I am not sure t

Re: [openstack-dev] [Stable][Nova] VMware NSXv Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I think Erno made a valid point here. If that would touch only vmware code, that could be an option to consider. But it looks like both patches are very invasive, and they are not just enabling features that are already in the tree, but introduc

[openstack-dev] [neutron][qos][ml2] extensions swallow exceptions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, in feature/qos, we use ml2 extension drivers to handle additional qos_policy_id field that can be provided thru API: http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2 /extensions/qos.py?h=feature/qos What we do in qo

[openstack-dev] [stable][neutron] dvr job for kilo?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, I noticed that dvr job is now voting for all stable branches, and failing, because the branch misses some important fixes from master. Initially, I tried to just disable votes for stable branches for the job: https://review.openstack.org/#/

Re: [openstack-dev] [Infra][CI] gate-{name}-requirements job fails on stable/juno

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/24/2015 12:37 PM, Roman Podoliaka wrote: > Hi all, > > In oslo.db we recently hit a requirements checking job failure > [0]. It's caused by the fact the job tries to import a module from > openstack_requirements package, which is missing in s

Re: [openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/23/2015 05:52 PM, Armando M. wrote: > > On 23 July 2015 at 05:25, Ihar Hrachyshka <mailto:ihrac...@redhat.com>> wrote: > > Hi all, > > I've stumbled on this one. It turns out we gate neutron against > o

[openstack-dev] [neutron] why do we gate tempest using q-vpn not q-l3?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, I've stumbled on this one. It turns out we gate neutron against openstack installation that runs vpn-agent instead of l3-agent [1]. Is it really what we want to do? I would expect that gate validates l3 agent as is, as is usually found on us

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/16/2015 05:08 PM, Thomas Goirand wrote: > On 07/16/2015 03:29 PM, Ihar Hrachyshka wrote: >> Working on upstream gate stability obviously does not invalidate >> any effort to introduce distribution CI votes in gerrit, and I >&

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/16/2015 03:06 PM, Thomas Goirand wrote: > What we discussed was that distributions would run their own CI > and validate patches away from upstream CI, then we would agree on > a patch and share it. > That's fine. I think a good start would b

Re: [openstack-dev] [neutron][db] online-schema-migrations patch landed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/15/2015 04:03 PM, Salvatore Orlando wrote: > Do you reckon that the process that led to creating a migration > like [1] should also be documented in devref? https://review.openstack.org/202534 -BEGIN PGP SIGNATURE- Version: GnuPG v2 i

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 While I'm an obsolete™ core reviewer and not an official member of any of those subteams, I will nevertheless say that Cedric will be a very valuable addition to the team. His reviews are usually insightful and touch the root of the problem, not mere

Re: [openstack-dev] [neutron] questions on neutron-db-migrations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/15/2015 07:17 PM, Madhusudhan Kandadai wrote: > Hello, > > I have noticed that neutron project got rid of > neutron/db/migration/alembic_migrations/versions/HEAD file and > renamed it to > neutron/db/migration/alembic_migrations/versions/HEAD

Re: [openstack-dev] [neutron][db] online-schema-migrations patch landed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/15/2015 04:03 PM, Salvatore Orlando wrote: > Do you reckon that the process that led to creating a migration > like [1] should also be documented in devref? That might be > helplful for developers, unless that process is already documented > el

[openstack-dev] [neutron][db] online-schema-migrations patch landed

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, since it's a high impact change in the migration tree, I wanted to drop an email to everyone affected (basically, anyone who wants to introduce a new migration from now on). So there was a proposal to split migration rules into independent

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2015 09:14 PM, Thomas Goirand wrote: > On 07/14/2015 10:29 AM, Ihar Hrachyshka wrote: >> On 07/14/2015 12:33 AM, Thomas Goirand wrote: >>> I missed this announce... >> >>> On 07/02/2015 05:32 AM, Jeremy Sta

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2015 01:46 AM, Perry, Sean wrote: >> -Original Message- From: Doug Hellmann >> [mailto:d...@doughellmann.com] Sent: Monday, July 13, 2015 3:41 >> PM To: openstack-dev Subject: Re: [openstack-dev] [all] Time to >> remove Python2.6 job

Re: [openstack-dev] [openstack-announce] End of life for managed stable/icehouse branches

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/14/2015 12:33 AM, Thomas Goirand wrote: > I missed this announce... > > On 07/02/2015 05:32 AM, Jeremy Stanley wrote: >> Per the Icehouse EOL discussion[1] last month, now that the >> final 2014.1.5 release[2] is behind us I have followed our

Re: [openstack-dev] [all] Time to remove Python2.6 jobs from master

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/13/2015 03:29 AM, Robert Collins wrote: > So, we've got constraints support for tox coming together nicely. > > The rollout for that will be per project (because tox.ini needs to > change). > > However, we're not compiling, nor are we easily

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

process on renames. Ihar On 07/07/2015 03:09 PM, Ihar Hrachyshka wrote: > 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

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] [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 fe

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

Re: [openstack-dev] [Neutron] New Neutron subproject for a Neutron backed Docker remote networking driver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/09/2015 10:55 AM, Antoni Segura Puimedon wrote: > Names: Kuryr - Czech name for Courier since it is delivering > networking to containers. v: apuimedo+1 :) If you stick to it, make sure you provide info on how it's pronounced . Ihar -BEGI

Re: [openstack-dev] [neutron][upgrades] Potential issues when performing Neutron upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/09/2015 09:01 AM, Artur Korzen wrote: > Hi all, > > I've been researching the Neutron project as a part of work on > Openstack rolling upgrades, my primary assignments included testing > if there is no VM access downtime when performing upgrad

[openstack-dev] [stable] dashboard for stable integrated releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi stables, I've sent a gerrit dashboard template for stable-maint team: https://review.openstack.org/200069 Please review, use and provide feedback. Ihar -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVnnWkAAoJEC5aWaUY1u57elAIAJx

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] [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 wrote

Re: [openstack-dev] [Neutron] - breaking changes for plugins/drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/01/2015 04:09 PM, Kyle Mestery wrote: > On Wed, Jul 1, 2015 at 5:49 AM, Kevin Benton > wrote: > >> For the second one, I think we made it clear before that no > plugins must rely on neutron.openstack.* contents. > >

Re: [openstack-dev] [Neutron] - breaking changes for plugins/drivers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/01/2015 08:22 AM, Kevin Benton wrote: > Hi, > > We have had at least two breaking changes merge this week for > out-of-tree drivers/plugins. These are just the two I noticed that > broke the Big Switch CI (the one I keep an eye on since I had

Re: [openstack-dev] [all] Any other downstream developers having problems with pbr?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/26/2015 01:01 PM, Matthew Booth wrote: > I wrote this: > > https://review.openstack.org/#/c/195983/1/tools/de-pbr.py,cm > > Ideally we'd fix PBR, but this seems to be expected behaviour. > Thoughts? > > Matt > You either use an older pbr v

Re: [openstack-dev] [Nova] The unbearable lightness of specs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/24/2015 03:23 PM, Sahid Orentino Ferdjaoui wrote: > I do not consider specs don't work, personnaly I refer myself to > this relatively good documentation [1] instead of to dig in code > to remember how work a feature early introduced. > I thi

Re: [openstack-dev] [neutron] dns-nameservers order not honored

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/23/2015 08:48 PM, Paul Ward wrote: > I haven't dug into the code yet, but from testing via CLI and REST > API, it appears neutron does not honor the order in which users > specify their dns-nameservers. For example, no matter what order I > sp

[openstack-dev] [neutron][stable] Kevin Benton added to neutron-stable-maint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi all, Just a heads-up that Kevin Benton is added to neutron-stable-maint team so now he has all the powers to +2/+A (and -2) backports. Kevin is very active at voting for neutron backports (well, where is he NOT active?), so here you go. Thanks

Re: [openstack-dev] [infra][neutron] Requirements validations

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/23/2015 11:16 AM, Gary Kotton wrote: > Hi, In the vmware_nsx project we have done the following: > > 1. In the test_requirements file we have a link to the neutron > master [1]. The purpose for this is that the master branch needs to > be in s

Re: [openstack-dev] Debian already using Python 3.5: please gate on that

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/18/2015 09:48 PM, Doug Hellmann wrote: > Excerpts from Brian Curtin's message of 2015-06-18 13:17:52 -0500: >> On Thursday, June 18, 2015, Doug Hellmann >> wrote: >> >>> Excerpts from Thomas Goirand's message of 2015-06-18 15:44:17 >>> +0200:

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Re: How do your end users use networking?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/17/2015 05:55 PM, Fox, Kevin M wrote: > The biggest issue we have run into with multiple public networks is > restricting which users can use which networks. We have the same > issue, where we may have an internal public network for the > datac

Re: [openstack-dev] [neutron][db] online schema upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/16/2015 05:58 PM, Mike Bayer wrote: > > > On 6/16/15 11:41 AM, Ihar Hrachyshka wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> - - instead of migrating data with alembic rules, migrate it in &g

Re: [openstack-dev] [neutron][db] online schema upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/17/2015 11:27 AM, Anna Kamyshnikova wrote: > Ihar, thanks for bringing this up! > > This is very interesting and I think it worth trying. I'm +1 on > that and want to participate in this work. > Awesome. > In fact a lot *not strict* migrati

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/17/2015 05:40 PM, Douglas Mendizábal wrote: > I tend to agree with Thomas that plan D is not ideal. For one, it > prevents changes to the stable branch that span multiple CRs, since > a two patch change would generate two tags and there would

[openstack-dev] [neutron][db] online schema upgrades

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi neutron folks, I'd like to discuss a plan on getting support for online db schema upgrades in neutron. *What is it even about?* Currently, any major version upgrade, or master-to-master upgrade, requires neutron-server shutdown. After shutdown,

Re: [openstack-dev] [all][release] summit session summary: Release Versioning for Server Applications

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/16/2015 09:44 AM, Thierry Carrez wrote: > Doug Hellmann wrote: >> [...] I still need to chat with Kyle about some of the neutron >> spin-out projects, since their repositories have the old neutron >> tags but I don't think it's appropriate to u

Re: [openstack-dev] [all] [stable] No longer doing stable point releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/15/2015 11:24 PM, Thomas Goirand wrote: > On 06/15/2015 05:19 PM, Ian Cordasco wrote: >> On 6/15/15, 09:24, "Thomas Goirand" wrote: >> >>> On 06/08/2015 01:55 PM, Kuvaja, Erno wrote: One thing I like about plan D is that it would give al

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Not on the list either, but I want to +1 what Henry said. Yamamoto's reviews expand to the whole code base and are pretty always *very* usefu l. On 06/12/2015 11:39 PM, Henry Gessau wrote: > Although I am not on your list I would like to add my +1!

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 No doubt +1. On 06/12/2015 09:44 PM, 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 control plane core > reviewer team. > > Her review stats are in line

Re: [openstack-dev] [neutron] Missing openvswitch filter rules

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/13/2015 04:38 PM, Jeff Feng wrote: > *I'm using OVSHybridIptablesFirewallDriver in > ovs_neutron_plugin.ini* / [securitygroup] firewall_driver = > neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver > > enable_security_group

Re: [openstack-dev] [all][python3] use of six.iteritems()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/10/2015 02:15 AM, Robert Collins wrote: > I'm very glad folk are working on Python3 ports. > > I'd like to call attention to one little wart in that process: I > get the feeling that folk are applying a massive regex to find > things like d.it

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