[openstack-dev] [requirements] modifying the 'is it packaged' test

We currently have a test where we ask if things are packaged in distros. http://git.openstack.org/cgit/openstack/requirements/tree/README.rst#n268 I think we should modify that, in two ways. The explanation for the question ignores a fairly large audience of deployers who don't wait for distribu

[openstack-dev] What's Up, Doc? 21 August 2015 (Early edition)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi everyone, First of all, apologies for missing last week's newsletter: I got so caught up in the documentation swarm happening here in Brisbane that it totally slipped my mind! To make up for it, have this week's newsletter a day early :) In swarm n

[openstack-dev] [nova][qa] libvirt + LXC CI - where's the beef?

After spending a few hours on https://bugs.launchpad.net/nova/+bug/1370590 I'm annoyed by the fact we don't yet have a CI system for testing libvirt + LXC. At the Juno midcycle in Portland I thought I remember some guy(s) from Rackspace talking about getting a CI job running, whatever happened

Re: [openstack-dev] [nova][cinder] Extending attached disks

On Wed, Aug 19, 2015 at 7:48 PM, wrote: > Hi everyone, > > Apologises for the duplicate send, looks like my mail client doesn't > create very clean HTML messages. Here is the message in plain-text. I'll > make sure to send to the list in plain-text from now on. > > In my current pre-production de

[openstack-dev] [nova][cinder] Extending attached disks

Hi everyone, Apologises for the duplicate send, looks like my mail client doesn't create very clean HTML messages. Here is the message in plain-text. I'll make sure to send to the list in plain-text from now on. In my current pre-production deployment we were looking for a method to live exten

[openstack-dev] [nova][cinder] Extending attached disks

Hi everyone,In my current pre-production deployment we were looking for a method to live extend attached volumes to an instance. This was one of the requirements for deployment. I've worked with libvirt hypervisors before so it didn't take long to find a workable solution. However I'm not sure how

Re: [openstack-dev] [nova] contextlib.nested and Python3 failing

On Aug 19, 2015, at 16:51, Sylvain Bauza wrote: > Ideas appreciated. Instead of using the nested context managers, a way I like is to decorate a nested function in the test and call it, for example: def test_thing(self): @mock.patch(...) @mock.patch(...) @mock.patch(...) def

Re: [openstack-dev] [packaging] asks from the ops meetup

On 08/19/2015 07:22 PM, Ian Cordasco wrote: > Questions in-line, but I'd appreciate a better summary > > On 8/19/15, 17:50, "Matthew Thode" wrote: > >> I'll start by giving this out, but I'll also summarize the asks we had >>from upstream. >> >> https://etherpad.openstack.org/p/PAO-ops-packaging

Re: [openstack-dev] [nova] contextlib.nested and Python3 failing

haha :) -- dims On Wed, Aug 19, 2015 at 7:59 PM, Sylvain Bauza wrote: > > > Le 19/08/2015 16:51, Sylvain Bauza a écrit : > >> Hi, >> >> I was writing some tests so I added a contextlib.nested to a checked >> TestCase [1]. Unfortunately, contextlib.nested is no longer available in >> Python3 and

Re: [openstack-dev] [packaging] asks from the ops meetup

Questions in-line, but I'd appreciate a better summary On 8/19/15, 17:50, "Matthew Thode" wrote: >I'll start by giving this out, but I'll also summarize the asks we had >from upstream. > >https://etherpad.openstack.org/p/PAO-ops-packaging > > >General services: > - gate check on example config

Re: [openstack-dev] [Horizon] Update on Angular Identity work

Hi Thai, Thanks for investigating the two options. Option 2 might be better. Folks have to learn the new pattern of writing multiple files, so I think the learning curve for a new table directive is not that much of a difference. I think option 2 is going to be easier to maintain, since we have

Re: [openstack-dev] [fuel] Gerrit dashboard update: ready for core reviewers, disagreements

Thank you Dmitry, everyone can now open review inbox following [1]. Full link was also updated by Dmitry on main Fuel wiki page. [1] http://bit.ly/1LjYO4t On Wed, Aug 12, 2015 at 8:53 PM Cameron Seader wrote: > test > > On 08/12/2015 07:16 PM, Dmitry Borodaenko wrote: > > Fuelers, > > > > I've

Re: [openstack-dev] [nova] contextlib.nested and Python3 failing

Le 19/08/2015 16:51, Sylvain Bauza a écrit : Hi, I was writing some tests so I added a contextlib.nested to a checked TestCase [1]. Unfortunately, contextlib.nested is no longer available in Python3 and there is no clear solution on how to provide a compatible import for both python2 and py

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

Sounds great. Thank you Roman! I've heard complains about tests not passing for [1]. Now it's passed, so I hope that issues are resolved. [1] https://review.openstack.org/#/c/212906/ On Wed, Aug 19, 2015 at 10:51 AM Sebastian Kalinowski < skalinow...@mirantis.com> wrote: > Indeed, great news! >

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

As it simply has blocking bugs, and so it can't even be called experimental, only prototype. I don't vote though for reverting the code. I just want to ensure that we don't recommend it to anyone except other developers, who want to try it and may be propose some fixes. On Wed, Aug 19, 2015 at 3:5

[openstack-dev] [app-catalog] IRC Meeting Thursday August 20th at 17:00UTC

Howdy! Our next OpenStack App Catalog meeting will take place this Thursday August 20th at 17:00 UTC in #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog Please add agenda items if there's anything specific you would like to discuss (or of cou

[openstack-dev] [nova] contextlib.nested and Python3 failing

Hi, I was writing some tests so I added a contextlib.nested to a checked TestCase [1]. Unfortunately, contextlib.nested is no longer available in Python3 and there is no clear solution on how to provide a compatible import for both python2 and python3: - either providing a python3 compatible

[openstack-dev] [packaging] asks from the ops meetup

I'll start by giving this out, but I'll also summarize the asks we had from upstream. https://etherpad.openstack.org/p/PAO-ops-packaging General services: - gate check on example config and doc generation - was mentioned this has broken in the past and taken a while to fix - document dep

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

Folks Why not enable it as an experimental? On Wed, Aug 19, 2015 at 12:20 PM, Mikhail Semenov wrote: > As we considered today, Ubuntu bootstrap will not be shipped in MOS 7.0. > It was a hard decision based on the issue with NICs naming [1]. > This bug can be fixed only by changing the naming o

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

On 19/08/15 11:52, Edgar Magana wrote: Folks, I just want to share with you the feedback collected today during the networking session on Ops Meet-up: https://etherpad.openstack.org/p/PAO-ops-network-model Special thanks to Ryan and Doug for helping on some questions. Line 28 on https://eth

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

On 08/19/2015 05:29 PM, Ryan Moats wrote: > They didn't mention a release by name, so I think it may be fair that they > were testing pre-kilo - I'll take the action item to follow up with them... > > Ryan > > "Sean M. Collins" wrote on 08/19/2015 04:25:22 PM: > >> From: "Sean M. Collins" >> T

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

They didn't mention a release by name, so I think it may be fair that they were testing pre-kilo - I'll take the action item to follow up with them... Ryan "Sean M. Collins" wrote on 08/19/2015 04:25:22 PM: > From: "Sean M. Collins" > To: "OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

Mikhail, thanks for the update. I'm glad that we have an agreement here, and collaborative decision have been made not to enable something in 7.0 which is proven to be not yet production ready, such late in the release cycle. I'm all for completing this work in 8.0 though. Can you please: - provid

Re: [openstack-dev] Cross-project meeting times

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That makes it 4am for me, so I'm out :( L On 20/08/15 01:39, Morgan Fainberg wrote: > I am ok with this moving as long as it doesn't camp on the Keystone meeting > time ;). In all seriousness I'm not opposed to moving the meeting if it will > inclu

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

To expand on that a bit, I think the DVR complaints were vague because of the simple fact that the overwhelming majority were or wanted to run linuxbridge, not OVS, so DVR was a theoretical thing for them. doug > On Aug 19, 2015, at 2:21 PM, Salvatore Orlando wrote: > > The etherpad contains

Re: [openstack-dev] [Neutron] Kuryr - virtual sprint

Hi Gal, even if I've been a lurker so far, I'm interested in attending for learning and contributing to it with my massive bug-injecting skills! You said "virtual sprint" and "somewhere in september" - I think "somewhere" refers to dates? Anyway I am pretty much open to any date from September 7t

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

On Wed, Aug 19, 2015 at 05:11:55PM EDT, Ryan Moats wrote: > One thing came up during lunch was including unit and functional testing of > dual stack in the check and gate queues - I was regaled over lunch with one > operator's experiences in trying to run Neutron on a dual stack system. We are tes

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

The etherpad contains some complaints around DVR implementation that might deserve furhter exploration. However, as pointed out by Jay, the comments made leave very little room for actionable items. It would be great if the author(s) could fill in with more details. Salvatore On 19 August 2015 at

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

One thing came up during lunch was including unit and functional testing of dual stack in the check and gate queues - I was regaled over lunch with one operator's experiences in trying to run Neutron on a dual stack system. Ryan Moats (regXboi) Edgar Magana wrote on 08/19/2015 03:43:44 PM: > Fr

Re: [openstack-dev] [openstack-ansible][keystone] Federation beyond Shibboleth

On 08/19/2015 04:23 AM, Jesse Pretorius wrote: On 12 August 2015 at 18:48, Adam Young > wrote: The simplest one is Kerberos + SSSD; Kerberos provides Authentication. mod_lookup_identity uses SSSD to get Groups. It turns LDAP into another Federated

Re: [openstack-dev] [devstack] Possible issues cryptography 1.0 and os-client-config 1.6.2

On 20 August 2015 at 01:42, Sean Dague wrote: > Sorry about jumping the gun there. We thought, incorrectly, we had the > right fix. And it's a conference week so access to my local test env > wasn't easy. No worries - these things happen. Having higher fidelity tests would give some more insulat

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

Actually, there were very few requirements collected. So, your summary is correct. I feel that this time we did not get a lot of input s we got during the Ops meet-up in Philadelphia. I also recommend to read the burning issues ether pads, there are few suggestions on the networking side. Actu

Re: [openstack-dev] [Neutron] Etherpad from the Ops Meetup

On Wed, Aug 19, 2015 at 2:52 PM, Edgar Magana wrote: > Folks, > > I just want to share with you the feedback collected today during the > networking session on Ops Meet-up: > https://etherpad.openstack.org/p/PAO-ops-network-model > > Special thanks to Ryan and Doug for helping on some questions.

Re: [openstack-dev] [Neutron] "binding information" for networks

On Wed, Aug 19, 2015 at 2:34 PM, Gal Sagie wrote: > Hello all, > > Recently i have came across two use cases that having "binding" > information, or metadata > for networks can be useful. (similar to the port binding profile for that > matter) > > For example: > > 1) In project Kuryr we want to h

Re: [openstack-dev] [nova] should we combine a set of minor microversion bump needed fix into one microversoin bump?

On 8/19/2015 2:16 PM, Matt Riedemann wrote: On 8/19/2015 1:33 PM, Matt Riedemann wrote: On 8/19/2015 12:18 PM, Chen CH Ji wrote: In doing [1] [2], some suggestions raised that those kind of change need microversion bump which is fine however, another concern raised on whether we need comb

Re: [openstack-dev] [fuel][puppet] The state of collaboration: 9 weeks

Matt, I appreciate that it has barely been 2 months since we've started following the new model of collaboration (see thread subject :), so the intent of highlighting Bogdan's work was exactly what you said: put it on your radar. We have discussed the swift ring rebalance patch in the IRC meeting

Re: [openstack-dev] [Horizon] Update on Angular Identity work

Hi Lin,I agree with you and Eric that we have a lot of HTML fragments. Some of them I think make sense as directives:The table footer is a good example of something we can convert into a directive: https://review.openstack.org/#/c/207631/The table header on the other hand is something more specific

Re: [openstack-dev] [nova] should we combine a set of minor microversion bump needed fix into one microversoin bump?

On 8/19/2015 1:33 PM, Matt Riedemann wrote: On 8/19/2015 12:18 PM, Chen CH Ji wrote: In doing [1] [2], some suggestions raised that those kind of change need microversion bump which is fine however, another concern raised on whether we need combine a set of those kind of changes (which may o

[openstack-dev] [Neutron] Etherpad from the Ops Meetup

Folks, I just want to share with you the feedback collected today during the networking session on Ops Meet-up: https://etherpad.openstack.org/p/PAO-ops-network-model Special thanks to Ryan and Doug for helping on some questions. Cheers, Edgar __

Re: [openstack-dev] [fuel][puppet] The state of collaboration: 9 weeks

Dmitry, I've appreciated the feedback on my patches from your team and the work they are doing, it's great that everyone is working together better now. I think getting more puppet core reviewers is certainly on the horizon and will happen with continued effort, it just takes time and trust. But i

Re: [openstack-dev] [Neutron][fwaas] APAC friendly meeting

OK - UTC sounds good to me, so if anyone is available we can conduct the meeting this week - so in about 5 hours? I'll push an update to the ircmeetings repo. I think it'll be a light agenda from my end due to my last minute decision, but it'll at least give everyone time to say hello and b

[openstack-dev] [Neutron] "binding information" for networks

Hello all, Recently i have came across two use cases that having "binding" information, or metadata for networks can be useful. (similar to the port binding profile for that matter) For example: 1) In project Kuryr we want to have a binding information which maps the Neutron network to docke

Re: [openstack-dev] [nova] should we combine a set of minor microversion bump needed fix into one microversoin bump?

On 8/19/2015 12:18 PM, Chen CH Ji wrote: In doing [1] [2], some suggestions raised that those kind of change need microversion bump which is fine however, another concern raised on whether we need combine a set of those kind of changes (which may only change some error code) into one bump ? ap

[openstack-dev] [glance] [nova] Image Prefetching – Precaching

Hi everyone, This is my first email to the OS developer forum, so forgive me if I misplaced the subject tags J. Straight to the point: for a project we’re involved in, we think that a pre-fetcher mechanism would be great for a variety of use cases. There was an attempt with this blueprint: ht

Re: [openstack-dev] [neutron][fwaas][dvr] FWaaS with DVR

Great writeup, I think this is an excellent starting place for our efforts moving forward. There is also some information on an accepted spec about firewall insertion[1], search for the phrase "Phase 2" where firewalls can be associated with ports - and also some of my thinking about having FwaaS

Re: [openstack-dev] [fuel][puppet] The state of collaboration: 9 weeks

On 08/18/2015 03:33 AM, Dmitry Borodaenko wrote: > Two weeks ago, I flagged the patch sets to commits ratio as the biggest > problem that Fuel contributors to Puppet OpenStack should address, and > over the past two weeks the situation has improved dramatically. In > first and second week of Augu

Re: [openstack-dev] [cinder] Proposing Gorka Eguileor for core

Congratulations! Welcome Gorka! Jay On 08/19/2015 12:01 PM, Mike Perez wrote: On 12:13 Aug 13, Mike Perez wrote: It gives me great pleasure to nominate Gorka Eguileor for Cinder core. Gorka's contributions to Cinder core have been much apprecated: https://review.openstack.org/#/q/owner:%22G

[openstack-dev] [Neutron] Kuryr - virtual sprint

Hello everyone, During our last meeting an idea was brought up that we try to do a virtual sprint for Kuryr somewhere in September. Basically the plan is very similar to the mid cycle sprints or feature sprints where we iterate on couple of tasks online and finish gaps we might have in Kuryr. (I

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

Indeed, great news! I would only suggest to wait a little bit more that a few days with switching to the voting mode since it looks like there will be not so many patches proposed to python-fuelclient as we are heading towards Hard Code Freeze. I hope that the next step will be to enable Python 3

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

[openstack-dev] [nova] should we combine a set of minor microversion bump needed fix into one microversoin bump?

In doing [1] [2], some suggestions raised that those kind of change need microversion bump which is fine however, another concern raised on whether we need combine a set of those kind of changes (which may only change some error code) into one bump ? apparently there are pros and cons for doing s

Re: [openstack-dev] [Fuel][MOS][Bootstrap] Please try Ubuntu bootstrap in MOS 7.0

As we considered today, Ubuntu bootstrap will not be shipped in MOS 7.0. It was a hard decision based on the issue with NICs naming [1]. This bug can be fixed only by changing the naming of network interfaces( http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) and i

Re: [openstack-dev] [TripleO] Moving instack upstream

- Original Message - > From: "Dmitry Tantsur" > To: openstack-dev@lists.openstack.org > Sent: Wednesday, 19 August, 2015 5:57:36 PM > Subject: Re: [openstack-dev] [TripleO] Moving instack upstream > > On 08/19/2015 06:42 PM, Derek Higgins wrote: > > On 06/08/15 15:01, Dougal Matthews

Re: [openstack-dev] [neutron][fwaas][dvr] FWaaS with DVR

Resending, forgot the [neutron] tag-Mickey Spiegel/San Jose/IBM wrote: -To: openstack-dev@lists.openstack.orgFrom: Mickey Spiegel/San Jose/IBMDate: 08/19/2015 09:45AMSubject: [fwaas][dvr] FWaaS with DVRCurrently, FWaaS behaves differently with DVR, applying to only north/south traffic, wher

Re: [openstack-dev] [cinder] Proposing Gorka Eguileor for core

On 12:13 Aug 13, Mike Perez wrote: > It gives me great pleasure to nominate Gorka Eguileor for Cinder core. > > Gorka's contributions to Cinder core have been much apprecated: > > https://review.openstack.org/#/q/owner:%22Gorka+Eguileor%22+project:openstack/cinder,p,0035b6410002dd11 > > 60/90 da

Re: [openstack-dev] [Fuel] Great updates to tests and CI jobs

Roman, well done! ;) Best regards, Boris Pavlovic On Wed, Aug 19, 2015 at 8:38 AM, Roman Prykhodchenko wrote: > Hi folks! > > Today I’m proud to announce that since this moment python-fuelclient has > it’s own python-jobs in OpenStack CI. Thanks to all of you who helped me > making Fuel Client

Re: [openstack-dev] [TripleO] Moving instack upstream

On 08/19/2015 06:42 PM, Derek Higgins wrote: On 06/08/15 15:01, Dougal Matthews wrote: - Original Message - From: "Dan Prince" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Thursday, 6 August, 2015 1:12:42 PM Subject: Re: [openstack-dev] [TripleO] Moving ins

[openstack-dev] [fwaas][dvr] FWaaS with DVR

Currently, FWaaS behaves differently with DVR, applying to only north/south traffic, whereas FWaaS on routers in network nodes applies to both north/south and east/west traffic. There is a compatibility issue due to the asymmetric design of L3 forwarding in DVR, which breaks the connection tracking

[openstack-dev] [neutron] RFE for DHCP agent changes for networking-calico

FYI, I've raised the new RFE bug that I suggested below: https://bugs.launchpad.net/neutron/+bug/1486649 Neil On 18/08/15 23:22, Neil Jerram wrote: > Although the DHCP-related patches below are I think very close to mergeable, > Brian Haley on IRC queried what, process-wise, motivates mergi

Re: [openstack-dev] [TripleO] Moving instack upstream

On 06/08/15 15:01, Dougal Matthews wrote: - Original Message - From: "Dan Prince" To: "OpenStack Development Mailing List (not for usage questions)" Sent: Thursday, 6 August, 2015 1:12:42 PM Subject: Re: [openstack-dev] [TripleO] Moving instack upstream I would really like to see

Re: [openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

Excerpts from Nikolay Makhotkin's message of 2015-08-19 17:16:14 +0300: > Hi, Davanum! > > Have you already read the thread [1]? It is about acknowledge feature in > oslo.messaging. Particularly, about the absent of this feature in > oslo.messaging. > > The guys from messaging said that it is ver

Re: [openstack-dev] Cross-project meeting times

I am ok with this moving as long as it doesn't camp on the Keystone meeting time ;). In all seriousness I'm not opposed to moving the meeting if it will include more people / make lives better for those who are there. Sent via mobile > On Aug 19, 2015, at 08:20, Sean Dague wrote: > > +1 for

[openstack-dev] [Fuel] Great updates to tests and CI jobs

Hi folks! Today I’m proud to announce that since this moment python-fuelclient has it’s own python-jobs in OpenStack CI. Thanks to all of you who helped me making Fuel Client compatible with the upstream CI. Besides sharing great news I think it’s necessary to share changes we had to do, in ord

Re: [openstack-dev] Cross-project meeting times

+1 for moving it earlier. On August 19, 2015 6:17:06 AM PDT, Anne Gentle wrote: >Hi all, > >In last week's TC Highlights blog post [1] I asked if there is interest >in >moving the cross-project meeting. Historically it is held after the TC >meeting, but there isn't a requirement for those timin

Re: [openstack-dev] Cross-project meeting times

On Wed, Aug 19, 2015 at 9:33 AM, Jeremy Stanley wrote: > On 2015-08-19 08:17:06 -0500 (-0500), Anne Gentle wrote: > > In last week's TC Highlights blog post [1] I asked if there is interest > in > > moving the cross-project meeting. Historically it is held after the TC > > meeting, but there isn'

Re: [openstack-dev] [openstack-infra][third-paty][CI][nodepool]Using Nodepool for creating slaves.

Hi Ramy, I got the following you mentioned, so as per my understanding here are the points: - We need to install CI master on a VM (*Using Ubuntu 14.04 in my case*). - The Master VM should have properties like 8 GB RAM, 100 GB HD. - Nodepool, Jenkins and Zull will be installed in the mas

Re: [openstack-dev] Cross-project meeting times

On 2015-08-19 08:17:06 -0500 (-0500), Anne Gentle wrote: > In last week's TC Highlights blog post [1] I asked if there is interest in > moving the cross-project meeting. Historically it is held after the TC > meeting, but there isn't a requirement for those timings to line up. I've > heard from Eur

Re: [openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

Hi, Davanum! Have you already read the thread [1]? It is about acknowledge feature in oslo.messaging. Particularly, about the absent of this feature in oslo.messaging. The guys from messaging said that it is very problematically to add that kind of feature to oslo.messaging because it does not fi

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

Hi Rick, Huge improvement. Log server is looking great! Thanks! Next question is what (cinder) patch set is that job running? It seems to be cinder master [1]. Is that intended? That's fine to validate general functionality, but eventually it needs to run the actual cinder patch set under test.

Re: [openstack-dev] [openstack-infra][third-paty][CI][nodepool]Using Nodepool for creating slaves.

Hi Xies, Abhi, It works a bit differently. Nodepool is responsible to launch VMs which it then registers as Jenkins Slaves. These Jenkins slaves have “labels” which identify certain user-properties such as Operating System, image contents, etc. When CI wants to run a test case it submits the job

Re: [openstack-dev] [Neutron][bgpvpn] Service Plugin vs Service driver

Hi, thanks for your reply irena and salvatore. Currently, we're targeting 4 backends : bagpipe (the ref impelmentations compatible with other ref implementations of neutron), ODL, contrail and nuage. Contrail and bagpipe work with networks attachments to a bgpvpn connection, while ODL and Nuage w

Re: [openstack-dev] [devstack] Possible issues cryptography 1.0 and os-client-config 1.6.2

On 08/18/2015 09:34 PM, John Griffith wrote: > > > On Tue, Aug 18, 2015 at 7:42 PM, John Griffith > wrote: > > > > On Tue, Aug 18, 2015 at 2:14 PM, Robert Collins > mailto:robe...@robertcollins.net>> wrote: > > On 19 August 2015 at 03:51, Sean

Re: [openstack-dev] [openstack-deb] Devstack stable/juno fails to install

On 8/18/2015 5:49 PM, Tony Breeds wrote: On Tue, Aug 18, 2015 at 10:04:56PM +, Jeremy Stanley wrote: On 2015-08-18 15:48:08 -0500 (-0500), Matt Riedemann wrote: [...] You'd also have to raise the cap on swiftclient in g-r stable/juno to python-swiftclient>=2.2.0,<2.4.0. [...] Followed b

[openstack-dev] Cross-project meeting times

Hi all, In last week's TC Highlights blog post [1] I asked if there is interest in moving the cross-project meeting. Historically it is held after the TC meeting, but there isn't a requirement for those timings to line up. I've heard from European and Eastern Standard Time contributors that it's a

Re: [openstack-dev] [cinder] [third-party] ProphetStor CI account

HI Ramy: Many thanks, I completed to install log-server. http://download.prophetstor.com/prophetstor_ci/203895/3/check/prophetstor-ds vm-tempest-cinder-ci/5111/logs/ So, can you help me to re-enable my gerrit account? -Original Message- From: Asselin, Ram

Re: [openstack-dev] [openstack][nova] Streamlining of config options in nova

Markus Zoeller/Germany/IBM@IBMDE wrote on 08/17/2015 09:37:09 AM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List \(not for usage questions\)" > > Date: 08/17/2015 09:48 AM > Subject: Re: [openstack-dev] [openstack][nova] Streamlining of config > options in no

[openstack-dev] [tricircle] Cancellation of Weekly Team Meeting 2015.08.19

Hi Team, Due to inability of several team members to attend today's meeting, the meeting would be canceled and discussion are welcomed on the mailing list :) -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei Technologies Co,. Ltd Email: huangzhip...@huawei

Re: [openstack-dev] [Neutron][bgpvpn] Service Plugin vs Service driver

Current VPNaaS Service Plugin inherits from VpnPluginRpcDbMixin, which is not required for some vendor solutions, since L3 is implemented without leveraging L3 Agents to manage router namespaces (ODL, MidoNet, etc). I guess if Mixin usage will be changed to conditional RPC support based on drivers

Re: [openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

Nikolay, Do you mean that you will *NOT* use oslo.messaging and use pika directly. I'd strongly discourage that possibility. Few members on the oslo.messaging team are looking at pika library already and are doing a prototype: https://github.com/dukhlov/oslo.messaging/blob/master/oslo_messaging/_

Re: [openstack-dev] [nova] API: Question on 'Retry-After': 0 in HTTPForbidden

ok thanks for confirm, I will file a bug and fix it~, Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com Phone: +86-10-82454158 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 10019

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

> -Original Message- > From: Robert Collins [mailto:robe...@robertcollins.net] > Sent: Wednesday, August 19, 2015 11:38 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable] [infra] How to auto-generate stable > release notes > > On 1

[openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

Hi, folks! Recently we've had the discussion with oslo.messaging team about acknowledge feature in RabbitMQ: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068806.html After that Mistral team did the research about using *kombu *or *pika* library for implementation of remote procedu

Re: [openstack-dev] Fw: [heat-translator] Nominating new core reviewers

+1 > Hello, > > I am glad to nominate Vahid Hashemian [1] and Srinivas Tadepalli [2] for > the Heat-Translator core reviewers team. > > Both of them have been providing significant contribution, development and > review, since the beginning of this year and knows code base well. > > Existing cor

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

On 19 August 2015 at 21:19, Thierry Carrez wrote: > Robert Collins wrote: >> [...] >> Proposed data structure: >> - create a top level directory in each repo called release-notes >> - within that create a subdirectory called changes. >> - within the release-notes dir we place yaml files containing

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] [TripleO][Tuskar] Steps to follow to provide MidoNet as Neutron backend in TripleO's overcloud

Sorry, I meant "Tuesday". On 19 August 2015 at 10:51, Jaume Devesa wrote: > Thanks Steven. > > I've registered the blueprint: > > https://blueprints.launchpad.net/tripleo/+spec/midonet-deployment-support > > We'll start preparing the pseudo-thirdparty job, develop the feature and > bother you g

Re: [openstack-dev] [TripleO][Tuskar] Steps to follow to provide MidoNet as Neutron backend in TripleO's overcloud

Thanks Steven. I've registered the blueprint: https://blueprints.launchpad.net/tripleo/+spec/midonet-deployment-support We'll start preparing the pseudo-thirdparty job, develop the feature and bother you guys in the IRC channel as soon as you approve the blueprint. Can we discuss it next Thursd

[openstack-dev] [Heat] Bugs for Rackspace resources that use scheduler tasks

Hi Randall, Jason this is re bug https://bugs.launchpad.net/heat/+bug/1393268 As most of in-tree resources are now fixed in this regard, Steve Baker asked me to create separate bugs for Rackspace resources from Heat's contrib that need fixing. As I am not comfortable with messing around in those

Re: [openstack-dev] [stable] [infra] How to auto-generate stable release notes

Robert Collins wrote: > [...] > Proposed data structure: > - create a top level directory in each repo called release-notes > - within that create a subdirectory called changes. > - within the release-notes dir we place yaml files containing the > release note inputs. > - within the 'changes' subdi

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

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 in themselves in my case), then it would be nice to express this. However thinking a bit more, I believe t

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

Hi, > After thinking about this some more, I'm not actually going to address Rob's > points above. What I want to do is go back and discuss... what do people > think about having an API that allows the initial provision state to be > specified, for a node that is created in Ironic. I'm assuming th

Re: [openstack-dev] [Congress] [Murano] multiple numbers of arguments for table

Hi Tim We use fixed count of columns. So I believe there should not be any bad impact of this change. Regards Filip On 08/18/2015 11:22 PM, Tim Hinrichs wrote: Hi all, We're contemplating a small syntax change in the Congress policy language and wanted to see if it would cause anyone probl

[openstack-dev] [Fuel] Code review process in Fuel and related issues

Hi all, let's discuss code review process in Fuel and what we can improve. For those who want to just have a quick context of this email, please check out presentation slides [5]. ** Issues ** Depending on a Fuel subproject, I'm aware of two buckets of issues with code review in Fuel: a) It is ha

Re: [openstack-dev] [congress] [murano] Congress jenkins job is failing

Hi Tim I will try it once it merges. Thanks Filio On 08/18/2015 05:46 PM, Tim Hinrichs wrote: Hi Filip, I just submitted a revert of the problematic change. Once it merges, all should be well again. Sorry for the trouble. Tim On Tue, Aug 18, 2015 at 7:57 AM Tim Hinrichs

Re: [openstack-dev] [neutron] New networking-calico project

Hi Andreas, Thanks for looking at this. I'm happy to say that Jeremy already identified the problem, in a thread on openstack-infra [1], and I've submitted a fix for it [2]. Regards, Neil [1] http://lists.openstack.org/pipermail/openstack-infra/2015-August/003087.html [2] https://review.ope

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

On 08/19/2015 02:05 AM, Ruby Loo wrote: On 17 August 2015 at 20:20, Robert Collins mailto:robe...@robertcollins.net>> wrote: On 11 August 2015 at 06:13, Ruby Loo mailto:rlooya...@gmail.com>> wrote: > Hi, sorry for the delay. I vote no. I underst

Re: [openstack-dev] [ironic] Re: New API for node create, specifying initial provision state

To be honest, I'm tired of repeating the same arguments again and again... I personally would like to get something cool done, rather than discussing how to work around our new state machine again and again. Now to some trolling: please include a way to users to opt-out from NOSTATE -> AVAILAB

Re: [openstack-dev] [openstack-ansible][keystone] Federation beyond Shibboleth

On 12 August 2015 at 18:48, Adam Young wrote: > > The simplest one is Kerberos + SSSD; > > Kerberos provides Authentication. > mod_lookup_identity uses SSSD to get Groups. It turns LDAP into another > Federated identity, much simpler than the LDAP code in Keystone (I am > responsible for that me

Re: [openstack-dev] [Neutron][bgpvpn] Service Plugin vs Service driver

my 0.02€ on the matter inline. Regards, Salvatore On 18 August 2015 at 23:45, Mathieu Rohon wrote: > hi brandon, > > thanks for your answer. > > my answers inline, > > > > On Tue, Aug 18, 2015 at 8:53 PM, Brandon Logan < > brandon.lo...@rackspace.com> wrote: > >> ​So let me make sure I understa

Re: [openstack-dev] [neutron] New networking-calico project

On 2015-08-18 20:30, Sean M. Collins wrote: Are your ACLs set up properly? https://review.openstack.org/#/admin/projects/openstack/networking-calico,access I don't see your group - or any actual group that has rights assigned to the repo - it's empty. compare that to: https://review.openstack

  1   2   >