Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+1 from me. Diana’s almost single handedly fixed our Bootstrap usage and gives lots of great reviews all across Horizon too. The boost to branding, theming and potential for accessibility, as well as huge reduction in CSS/HTML maintenance overhead, has been brilliant. Rob On 9 Mar 2016, at

[openstack-dev] The #openstack-packaging channel requires an invite?

Someone showed up in the -stable channel this morning asking for help with packaging. I gather they were there because the IRC wiki [1] says the #openstack-stable channel is also for packaging discussions, given -stable originated from distro people. I redirected them to

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

It got renamed a couple of months/year ago to #openstack-stable: https://bugs.launchpad.net/openstack-ci/+bug/1360324 Documentation should have been updated to reflect this change. Channel being invite-only is probably a side-effect of the migration. Mathieu On 2016-03-09 12:48 PM, Matt

Re: [openstack-dev] [nova] patches that improve code quality

On 3/9/2016 6:22 AM, Radomir Dopieralski wrote: Some of the code we have in Nova is admittedly hard to read and brittle. This is true even though we cave excellent code review, and the reviewers that deeply care for the quality of code that is being merged. Some of this code has been there

[openstack-dev] [TripleO] Including Aodh and Gnocchi in Mitaka

Hey Guys: As many of you know, we have been working on getting Aodh and Gnocchi support into TripleO. We would like to formally request these two be made blockers to get into Mitaka release for TripleO. We tried to get these into Liberty, but due to time constraints it seems slim that that would

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

I’m not a core but I wanted to add my complete agreement with making Diana a core in horizon. She has done some incredible work in horizon through her work on the code, reviews and also community attitude and assistance getting people (myself included) familiar with horizon. Beth > On 8 Mar

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

On 9 March 2016 at 09:14, Assaf Muller wrote: > On Wed, Mar 9, 2016 at 9:40 AM, Ihar Hrachyshka > wrote: > > Vikash Kumar wrote: > > > >> > >> > >> On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar > >>

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On 3/9/2016 11:57 AM, Louis Taylor wrote: On Wed, Mar 9, 2016 at 5:48 PM, Matt Riedemann wrote: Someone showed up in the -stable channel this morning asking for help with packaging. I gather they were there because the IRC wiki [1] says the #openstack-stable

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

On 09/03/16 12:26 -0500, Doug Hellmann wrote: It's time to start opening the stable branches for libraries. I've prepared a list of repositories and the proposed versions from which we will create stable/mitaka branches, and need each team to sign off on the versions. If you know you intend to

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

On 02/29/2016 11:19 AM, Vladimir Kuklin wrote: > Hi Ivan > > Thanks for bringing this up. Frankly, I think that we hurried a little > bit by making our integration with upstream puppet manifests too > continuous. I would suppose that we used a little bit different technique. > > First of all, we

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10 Mar 2016 2:58 AM, "Radomir Dopieralski" wrote: > > On 03/09/2016 04:43 PM, Serg Melikyan wrote: >>> >>> This is exactly my first thought. The plugins *must* depend on Horizon, >>> and they have to use the same versions of XStatic packages anyways, > > >> so why

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

Thanks, Yeah I just gone over doc. and tried to use the subscription. After looking into code I understood thats its not for interprocess. @Armando - Thanks for updating faq On Wed, Mar 9, 2016 at 10:40 PM, Armando M. wrote: > > > On 9 March 2016 at 09:14, Assaf Muller

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Excerpts from Doug Hellmann's message of 2016-03-09 12:26:18 -0500: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from which > we will create stable/mitaka branches, and need each team to sign off on > the versions.

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On 03/09/2016 11:36 AM, Doug Hellmann wrote: > Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800: >> On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann wrote: >> >>> >>> >>> As I understood it when this course was originally proposed, the >>> idea was to

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

Excerpts from Sean Dague's message of 2016-03-09 12:22:08 -0500: > On 03/09/2016 11:36 AM, Doug Hellmann wrote: > > Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800: > >> On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann > >> wrote: > >> > >>> > >>> > >>>

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On 03/09/2016 12:32 PM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-03-09 12:22:08 -0500: >> On 03/09/2016 11:36 AM, Doug Hellmann wrote: >>> Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800: On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On Wed, Mar 9, 2016 at 5:48 PM, Matt Riedemann wrote: > Someone showed up in the -stable channel this morning asking for help with > packaging. I gather they were there because the IRC wiki [1] says the > #openstack-stable channel is also for packaging discussions,

[openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

It's time to start opening the stable branches for libraries. I've prepared a list of repositories and the proposed versions from which we will create stable/mitaka branches, and need each team to sign off on the versions. If you know you intend to release a bug fix version in the next couple of

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Hi, from Sahara team side, we're okay with python-saharaclient 0.13.0, no fixes expected. Thanks. On Wed, Mar 9, 2016 at 9:26 AM, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed

Re: [openstack-dev] [nova] bug reports and stable branches: tags or series?

Matt Riedemann wrote on 03/04/2016 04:29:53 PM: > From: Matt Riedemann > To: openstack-dev@lists.openstack.org > Date: 03/04/2016 04:30 PM > Subject: Re: [openstack-dev] [nova] bug reports and stable branches: > tags or series? > > >

[openstack-dev] [Neutron] stable/mitaka branch imminent for the client

Folks, Please see [1]. I gave Doug the go-ahead. Cheers, Armando [1] http://lists.openstack.org/pipermail/openstack-dev/2016-March/088853.html __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

All systems are go for: openstack/keystoneauth 2.3.0 openstack/keystonemiddleware 4.3.0 openstack/pycadf 2.1.0 openstack/python-keystoneclient 2.3.1 From: Doug Hellmann To: openstack-dev Date: 2016/03/09 06:28 PM Subject:

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

Folks, I would like to have Ihar as core reviewer for the advanced services (or any neutron-governance project for the time we have those projects in the governance). Ihar is instrumental in ensuring that gate/stable issues are dealt with promptly and swiftly and I trust he'll be using such as

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800: > On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann wrote: > > > > > > > As I understood it when this course was originally proposed, the > > idea was to have a few folks already in leadership positions go

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

On 9 March 2016 at 07:42, Ihar Hrachyshka wrote: > Henry Gessau wrote: > > By tomorrow we intend to tag the heads of all the neutron alembic branches >> with the MITAKA label [1][2][3][4]. >> >> If you have a patch that adds an alembic migration and you

Re: [openstack-dev] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/9/2016 8:54 AM, Amrith Kumar wrote: Matt, As I understand it, you have 4 changes up for review. Change [1] seeks to revert the change [6] to python-troveclient on master and reinstate the slave_of parameter. Change [2] is doing for stable/liberty, the same things that

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Good to go with: openstack/python-neutronclient 4.1.1 Thanks, Armando On 9 March 2016 at 09:26, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from which > we will

Re: [openstack-dev] [nova] patches that improve code quality

Ideally it's good practice to do refactoring the codes to add more readability. In reality, it's kind of impossible. Because there might be another process required after refactoring and it would take a time. But that's good point, honestly. On Thu, Mar 10, 2016 at 1:33 AM, Matt Riedemann

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Mike, #1 - If you truly agree with that, you should weigh in here: https://review.openstack.org/#/c/287286/ #2 - Requires a blueprint and new docs, but okay. #3 - Yes! We have very poor CI for fuel plugin builder. All it does is ensure it makes a plugin, not that it can be installed and deployed.

[openstack-dev] [glance]Why vm boots from the cirros image so slow?

hi guys. There is a question confuses me a long time. I create a vm by using the "cirros" image. Why the vm was so slow? In the VNC console, I see these info says "further output written to /dev/tty0". And the vm hangs a long time. What does the vm doing at that time?? Besides, could

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 09/03/16 19:52, Michael Krotscheck wrote: > On Wed, Mar 9, 2016 at 7:58 AM Monty Taylor > wrote: > > > > SOLUTION 4: vendor the javascript > > > > Heh. > > Heh indeed. > > SOLUTION 4.alt: use npm/bower instead of

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On 10 March 2016 at 18:23, Matthias Runge wrote: > > 4.alt.2: > move to proper packages for static file management. I mean, they need to > be built anyways. > Please define what you mean by "proper packages" here. I *think* you might mean system packages (aka Debian or Red

[openstack-dev] Branch miss-match between server and client in Kilo

Hi All Greetings for the day! I have noticed that while installing* OpenStack Kilo* using DevStack, the server components cloned are stable/kilo whereas the client components cloned are master. This leads to errors in installation or commands miss-match. For eg. *In tacker,* tacker git repo is

[openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Hi folks, in order to make a decision whether we need to support example plugins, and if actually need them [1], I'd suggest to discuss more common things about plugins. My thoughts: 1) This is not good, that our plugins created for Fuel 8 won't even install on Fuel 9. By default, we should

[openstack-dev] [QA] Meeting Thursday March 10th at 9:00 UTC

Hello everyone, Please reminder that the weekly OpenStack QA team IRC meeting will be Thursday, March 10th at 9:00 UTC in the #openstack-meeting channel. The agenda for the meeting can be found here:

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

A beautiful post, sir. Thank you for everything! On 09/03/16 22:15, Flavio Percoco wrote: Greetings, I'm not going to run for Glance's PTL position for the Newton timeframe. There are many motivations behind this choice. Some of them I'm willing to discuss in private if people are interested

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On Wed, Mar 09, 2016 at 12:28:59PM -0600, Matt Riedemann wrote: [snipped] > Ha, the irony. > > OK, so I thought awhile back, around YVR summit time, there was a group of > different packagers from different distros (debian/red hat/fedora/suse) that > were working together on some common tooling.

Re: [openstack-dev] [glance] Glance Mitaka: Passing the torch

Flavio, Glance and OpenStack benefited during your reign or period of humble service. Will miss you at the helm. Also thank you for anointing/attracting two new solid cores: Brian and Sabari Malini -Original Message- From: Tom Fifield [mailto:t...@openstack.org] Sent: Wednesday, March

Re: [openstack-dev] [nova][cinder] Limits on volume read throughput?

In my case Centos 7 is using QEMU 1.5.3 ... which is *ancient*. This is on a node with a packstack install of OpenStack. If you have a different result, I would like to know why... Got a bit further in my reading and testing. Also got my raw volume read performance in an instance from ~300MB/s

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

On 09/03/16 18:26, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > openstack/django_openstack_auth 2.2.0 Yes please Matthias -- Matthias Runge Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn, Commercial

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Folks, here is what I think: 1) I suggest to fix what is broken now. So that people who come across examples would not have to deal with issues. We may debate for other few days (hopefully not more), and all plugin devs will be suffering during this time. Also, according to Matt, > I should add

Re: [openstack-dev] [Fuel] Compatibility of fuel plugins and fuel versions

Hi Mike, Normally I would support your idea, but the reality is any plugin from 7.0 that defines a plugin role isn't going to work in 8.0 or 9.0. We changed too many task names and you just can't make a plugin support both versions not without something incredibly clever that I haven't

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On 03/09/2016 06:48 PM, Matt Riedemann wrote: > Someone showed up in the -stable channel this morning asking for help > with packaging. I gather they were there because the IRC wiki [1] says > the #openstack-stable channel is also for packaging discussions, given > -stable originated from distro

Re: [openstack-dev] [Horizon] Javascript linting and documentation

If possible, I’d really prefer we left linting work to Newton. It’ll be good to get it to a more usable state again, but we ought to be focusing on thoroughly checking the new Launch Instance for bugs and edge usage cases, as well as the outstanding bugs and blueprints targeted at RC1

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten tohorizon-core

Big +1 from me, thanks for all the hard work Diana!   - Original message -From: David Lyle To: OpenStack Development Mailing List Cc:Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-coreDate: Tue, Mar 8, 2016

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Thanks Matt. Agreed on 1, 2, 3, and 4. The reason for #5 is that there are other changes (for which we have FFE's) which will be merged and a new version of the client requested. Specifically, this change https://review.openstack.org/290177 Thanks, -amrith > -Original Message- >

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Doug, >> openstack/python-troveclient 2.1.0 Trove isn't there yet. You are aware of the conversation(s) we're having about this, and there are two. One is the FFE which requires a client change, and the second is the backwards compatibility issue that Matt raised yesterday. Thanks, -amrith

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Flavio, I believe that you are correct and that we don't need a major release. However, just to be positive, and out of an abundance of caution, I'm going to be looking to #openstack-infra or #openstack-release for confirmation. Thanks, -amrith > -Original Message- > From: Flavio

Re: [openstack-dev] [Horizon] Javascript linting and documentation

+1 to what Rob said. I guess I don't see what problems is being solved by turning the rule off, and I also don't see the harm in having more check. It does generate a lot of warnings, but invoking `npm run lint -- --quiet` gets rid of those. Also, from my experience, sphinx-based doc builds are

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

On Wed, Mar 9, 2016 at 7:58 AM Monty Taylor wrote: > > > SOLUTION 4: vendor the javascript > > > > Heh. > > Heh indeed. > > SOLUTION 4.alt: use npm/bower instead of xstatic to pull the javascript. > +1. Let's move the codebase forward, instead of continuing to build hacky

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On 03/09/2016 10:28 AM, Matt Riedemann wrote: Is that still a thing and if so, do they congregate somewhere? Because *that's* where I think people need to go, not the #openstack-stable channel. There is an #openstack-anvil channel, The anvil project had/has similar goals of being a

[openstack-dev] [trove] OpenStack Trove meeting minutes (2016-03-09)

Minutes of the OpenStack Trove meeting held today are at: http://eavesdrop.openstack.org/meetings/trove/2016/trove.2016-03-09-18.00.html -- Amrith Kumar, CTO | amr...@tesora.com Tesora, Inc | @amrithkumar 125 CambridgePark Drive, Suite 400 |

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

Matt, We discussed this at the Trove meeting. Here's my current understanding of the situation: 1. Your change https://review.openstack.org/#/c/290048/ which reverts the trove client side of the change should be merged. 2. This change (the Trove API side)

Re: [openstack-dev] The #openstack-packaging channel requires an invite?

On 03/09/2016 07:28 PM, Matt Riedemann wrote: > Ha, the irony. > > OK, so I thought awhile back, around YVR summit time, there was a group > of different packagers from different distros (debian/red > hat/fedora/suse) that were working together on some common tooling. > > Is that still a thing

Re: [openstack-dev] [horizon] Proposal to add Diana Whitten tohorizon-core

+1. Another vote in favor of ditching django altogether is good by me :) On Wed, Mar 9, 2016 at 11:25 AM Thai Q Tran wrote: > Big +1 from me, thanks for all the hard work Diana! > > > - Original message - > From: David Lyle > To: OpenStack

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/9/2016 1:34 PM, Amrith Kumar wrote: Matt, We discussed this at the Trove meeting. Here's my current understanding of the situation: 1. Your change https://review.openstack.org/#/c/290048/ which reverts the trove client side of the change should be merged. 2. This change (the Trove

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Hi, Doug Heat team is agree to use python-heatclient == 1.0.0 for creating stable branch On 9 March 2016 at 20:26, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

Excerpts from Flavio Percoco's message of 2016-03-09 14:55:00 -0400: > On 09/03/16 13:41 -0500, Amrith Kumar wrote: > >Doug, > > > >>> openstack/python-troveclient 2.1.0 > > > >Trove isn't there yet. You are aware of the conversation(s) we're having > >about this, and there are two. > > > >One is

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

I probably speak for all FwaaS cores when I say - "Welcome!" Frankly I had just assumed he had core privileges for our repo anyway via an inherited ACL. -- Sean M. Collins __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [tc] [trove][stable] proboscis tests randomly failing in stable branches; bug 1538506

On 3/9/2016 2:15 PM, Amrith Kumar wrote: Thanks Matt. Agreed on 1, 2, 3, and 4. The reason for #5 is that there are other changes (for which we have FFE's) which will be merged and a new version of the client requested. Specifically, this change https://review.openstack.org/290177

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

Hi Serg, There's a crucial difference: getting the solution to this wrong for Horizon will break the gate for all OpenStack projects. Updating an xstatic package that a plugin uses has no side-effect outside of the plugin. Richard On 10 March 2016 at 02:43, Serg Melikyan

[openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core

+2 for Diana :) - Original message - From: David Lyle To: OpenStack Development Mailing List Cc: Subject: [openstack-dev] [horizon] Proposal to add Diana Whitten to horizon-core Date: Tue, Mar 8, 2016 2:07 PM I propose

[openstack-dev] [Neutron] Linuxbridge gate failures

Neutrinos, We had two back-to-back gate failures on [1,2] and more seem to be ramping up. These are tracked in bug [3] (e-r query tracked in [4]). Can I trouble some gentle soul to have a look? Thanks, Armando [1] https://review.openstack.org/#/c/286818/ [2]

Re: [openstack-dev] [Horizon] Javascript linting and documentation

Hi Michael, The problem is that the warnings are so great that is really hard to read. What if we amended the recently added lintq to do some inline filtering of the doc warnings? This is just a bandaid of course. I also am opposed to any major linting changes until Mitaka closes. They cause

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

On 3/9/16 4:39 PM, Zane Bitter wrote: On 09/03/16 05:42, Sergey Kraynev wrote: Hi Gary, First of all you don't need to use "depends_on", because using "get_attr" already create implicit dependency from rg_a. About getting Null instead of real Ip address: It sounds like a bug, but IMO, it's

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

2016-03-09 18:26 GMT+01:00 Doug Hellmann : > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from which > we will create stable/mitaka branches, and need each team to sign off on > the versions.

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

> On 03/09/2016 04:43 PM, Serg Melikyan wrote: >>> >>> This is exactly my first thought. The plugins *must* depend on Horizon, >>> and they have to use the same versions of XStatic packages anyways, > > >> so why specify the dependencies twice? >> >> >> Plugins may require different xstatic

[openstack-dev] [all][zaqar][cloudkitty] Default ports list

Hi all, Yesterday I just found cloudkitty is using the same default port () which is used by Zaqar now. So I'm wondering if there is any rule/policy for those new services need to be aware. I googled but can't find anything about this. The only link I can find is

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

On 09/03/16 05:42, Sergey Kraynev wrote: Hi Gary, First of all you don't need to use "depends_on", because using "get_attr" already create implicit dependency from rg_a. About getting Null instead of real Ip address: It sounds like a bug, but IMO, it's expected behavior, because I suppose it

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

Join us Thursday for our weekly meeting, scheduled for March 10th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to get something on the agenda: https://wiki.openstack.org/wiki/Meetings/app-catalog Looking forward to seeing everyone there

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

On Wed, Mar 09, 2016 at 12:26:18PM -0500, Doug Hellmann wrote: > It's time to start opening the stable branches for libraries. I've > prepared a list of repositories and the proposed versions from which > we will create stable/mitaka branches, and need each team to sign off on > the versions. If

Re: [openstack-dev] [Fuel][Fuel-Library] Fuel CI issues

Today we had a sync up call and discussed this. To summarize Attendees: Aleksandr Didenko Alex Schultz Andrew Woodward Alexey Shtokolov Bartek Kupidura Bogdan Dobrelya Denis Egorenko Ivan Berezovskiy Kyrylo Galanov Maksim Malchuk Matthew Mosesohn Max Yatsenko Oleg Gelbukh Oleksiy Molchanov Petr

Re: [openstack-dev] [all][zaqar][cloudkitty] Default ports list

This is not the first time. Monasca and Murano had a collision too[1]. When this happens the changes trickle down into automation tools also and complicates things. [1] https://bugs.launchpad.net/murano/+bug/1505785 On Wed, Mar 9, 2016 at 3:30 PM, Xav Paice wrote: > From an

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann wrote: > > > The etherpad [1] doesn't discuss any other alternatives that were > evaluated and rejected. Were any other options considered? In > particular, how does this course compare to an event such as the > Community

Re: [openstack-dev] [release][all][ptl] preparing to create stable/mitaka branches for libraries

On 09/03/16 13:41 -0500, Amrith Kumar wrote: Doug, openstack/python-troveclient 2.1.0 Trove isn't there yet. You are aware of the conversation(s) we're having about this, and there are two. One is the FFE which requires a client change, and the second is the backwards compatibility issue

Re: [openstack-dev] {openstack-dev][tc] Leadership training proposal/info

On Wed, Mar 9, 2016 at 9:32 AM, Doug Hellmann wrote: > Excerpts from Sean Dague's message of 2016-03-09 12:22:08 -0500: > > On 03/09/2016 11:36 AM, Doug Hellmann wrote: > > > Excerpts from Colette Alexander's message of 2016-03-08 14:34:19 -0800: > > >> On Tue, Mar 8, 2016

Re: [openstack-dev] [Fuel] Disable observing modifications of nested fields for MutableDict and MutableList

Fuelers, please notice that the patch [1] changes behaviour of MutableDict and MutableList. observing of changes in nested objects has been disabled, because it is not trivial to handle this case properly. It is much easier to notify about changes in nester fields explicitly when it is

Re: [openstack-dev] [Fuel] UI code freeze

Hi, Thank you for your work, really happy to see it done. So as far as I can see from now on in fuel-web repository we have only Nailgun project. Is it correct? On Fri, Feb 26, 2016 at 3:53 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Dear colleagues, > > We are ready for moving

Re: [openstack-dev] [cinder] Proposal: changes to our current testing process

John, It's a good option. Let's try it! Also, we can try to find/implement something like [13] for ostestr. [13] https://github.com/mahmoudimus/nose-timer Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Mon, Mar 7, 2016 at 7:16 PM, John Griffith wrote: > > >

[openstack-dev] [Fuel] Disable observing modifications of nested fields for MutableDict and MutableList

Fuelers, please notice that the patch [1] changes behaviour of MutableDict and MutableList. observing of changes in nested objects has been disabled, because it is not trivial to handle this case properly. It is much easier to notify about changes in nester fields explicitly when it is

Re: [openstack-dev] [all] [api] Reminder: WSME is not being actively maintained

On 03/08/2016 04:44 PM, Doug Hellmann wrote: it seems like the main reason there are so many projects leveraging WSME is because everyone is just using Ironic or Ceilometer as the starting point for their APIs. can we officially say to all new projects who plan on copying API logic of Ironic et

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

On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar < vikash.ku...@oneconvergence.com> wrote: > I have written a sample neutron agent which subscribe for the AFTER_CREATE > event of router. I have defined a sample method as callback, but the method > doesn't gets called anytime. > > Also, in logs: > >

Re: [openstack-dev] [tripleo] CI jobs failures

On Tue, 2016-03-08 at 17:58 +, Derek Higgins wrote: > On 7 March 2016 at 18:22, Ben Nemec wrote: > > > > On 03/07/2016 11:33 AM, Derek Higgins wrote: > > > > > > On 7 March 2016 at 15:24, Derek Higgins > > > wrote: > > > > > > > > On 6 March 2016

[openstack-dev] [nova] patches that improve code quality

Some of the code we have in Nova is admittedly hard to read and brittle. This is true even though we cave excellent code review, and the reviewers that deeply care for the quality of code that is being merged. Some of this code has been there always, some got that way as a result of bug fixes

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

Takashi Yamamoto wrote: > hi, > > On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau wrote: >> Takashi Yamamoto wrote: >>> Henry, >>> >>> i think it's better to fix model vs migration mismatch issues [1] >>> before tagging. >>> how do

[openstack-dev] [Mistral] Mistral with IPV6

Hello, We are trying to deploy mistral with IPV6 (Keystone is IPV6, the VM that we are installing on is IPV6 too, all OS Endpoints IPV6) – by changing In the ‘mistral.conf’ -> ‘bind_host=::’ . In Murano it was working pretty straight forward by changing this param.. but unfortanly for now

[openstack-dev] [Fuel] [Openstack] Instalation Problem: Inside VM "fuel-master"

Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160309/3227

[openstack-dev] [heat] issue of ResourceGroup in Heat template

Hi, I have 3 Heat templates using ResourceGroup. There are 2 resource groups(rg_a and rg_b) and rg_b depends on rg_a. and rg_b requires the IP address of rg_a as the paremeter of rg_b. I use "rg_a_public_ip: {get_attr: [rg_a, rg_a_public_ip]}" to get the IP address of rg_a both in the section

[openstack-dev] neutron agent not receiving callback

I have written a sample neutron agent which subscribe for the AFTER_CREATE event of router. I have defined a sample method as callback, but the method doesn't gets called anytime. Also, in logs: 2016-03-09 01:36:08.220 7075 DEBUG neutron.callbacks.manager [-] Subscribe: router after_create

Re: [openstack-dev] [release] mitaka-3 development milestone

Andreas Jaeger wrote: On 03/09/2016 09:47 AM, Thierry Carrez wrote: Jeremy Stanley wrote: On 2016-03-08 15:13:40 -0500 (-0500), Corey Bryant wrote: [...] I'm only seeing neutron-vpnaas-8.0.0.0b3.dev1.tar.gz on https://tarballs.openstack.org/neutron-vpnaas. Do we need an update there? After

Re: [openstack-dev] [Fuel] Nominate Maksim Malchuk for the fuel-virtualbox-core team

+1 -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Mar 9, 2016 at 8:07 AM, Bulat Gaifullin wrote: > +1 > > Regards, > Bulat Gaifullin > Mirantis Inc. > > > > On 03 Mar 2016, at 17:03, Dmitry Klenov wrote: > > Maksim, good

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

Takashi Yamamoto wrote: > Henry, > > i think it's better to fix model vs migration mismatch issues [1] > before tagging. > how do you think? I agree that [1] should be included in Mitaka, but it just adds the model-migration test to lbaas. The test passes so I don't see

Re: [openstack-dev] [heat] issue of ResourceGroup in Heat template

Hi Gary, First of all you don't need to use "depends_on", because using "get_attr" already create implicit dependency from rg_a. About getting Null instead of real Ip address: It sounds like a bug, but IMO, it's expected behavior, because I suppose it happens due to: - you create in rg_a some

Re: [openstack-dev] [oslo] PTL for Newton and beyond

Thanks for your hard work, Dims! Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Fri, Mar 4, 2016 at 3:34 PM, Mehdi Abaakouk wrote: > Hi, > > Thanks for all the great work you have done, I have appreciated your > leadership on Oslo, > and a special thanks to bring in

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

hi, On Wed, Mar 9, 2016 at 9:01 PM, Henry Gessau wrote: > Takashi Yamamoto wrote: >> Henry, >> >> i think it's better to fix model vs migration mismatch issues [1] >> before tagging. >> how do you think? > > I agree that [1] should be included in

Re: [openstack-dev] [all][zaqar][cloudkitty] Default ports list

>From an ops point of view, this would be extremely helpful information to share with various teams around an organization. Even a simple wiki page would be great. On 10 March 2016 at 10:35, Fei Long Wang wrote: > Hi all, > > Yesterday I just found cloudkitty is using

Re: [openstack-dev] [neutron][release] Releasing python-neutronclient 4.1.2?

On Wed, Mar 9, 2016 at 4:16 PM, Doug Hellmann wrote: > Excerpts from Armando M.'s message of 2016-03-08 15:43:05 -0700: > > On 8 March 2016 at 15:07, Doug Hellmann wrote: > > > > > Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: > >

Re: [openstack-dev] [fuel][plugins] Should we maintain example plugins?

Talking about templates I mean plugins generated by FBP from the `templates` folder using command you mentioned above. Why not to extend (not replace) template-generated plugins with additional data to provide right coverage? On Wed, Mar 9, 2016 at 6:23 PM, Evgeniy L wrote:

Re: [openstack-dev] [kolla] ubuntu deploy gate

FYI, the bug is seen in Ubuntu gate just on devstack-trusty-rax machine and not on devstack-trusty-osic and devstack-trusty-ovh. Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To:

Re: [openstack-dev] [Horizon] How do we move forward with xstatic releases?

>This is exactly my first thought. The plugins *must* depend on Horizon, and >they have to use the same versions of XStatic packages anyways, so why specify >the dependencies twice? Plugins may require different xstatic library, which is not even used by Horizon. Issue raised by Richard exists

  1   2   >