[openstack-dev] [nova] The vote for new Nova API sub-team meeting time

Hi, Looks like it's time to think about adjust nova api meeting now. I found really hard find a time which good for everyone. But let me give a try. I find out those time slots: 1400UTC: this is the time which closes to most people can join the meeting. But it's still very late or early for some

Re: [openstack-dev] [all][release] Release countdown for week R-4, Mar 7 - 11

Hi Doug. I have one question related with last item: "Release actions". Who will prepare patches for Reno and for updating .gitreview? Should it be done by related project team or it will be done by someone else? On 5 March 2016 at 02:01, Doug Hellmann wrote: > The Mitaka 3 milestone has passed,

Re: [openstack-dev] [Heat] Dealing with nonexistent resources during resource-list / stack-delete

On 03/08/2016 06:26 PM, Zane Bitter wrote: On 08/03/16 08:03, Johannes Grassler wrote: I think you're being a little too pessimistic. I was going to explain one approach, but it turned out to be easier to just submit a patch: https://review.openstack.org/290027 Ah, that one looks good, thanks

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

On 03/08/2016 11:43 PM, David Lyle wrote: I'm wondering if since horizon is really the only project consuming these xstatic libraries and none are likely to venture down this path of madness with us that it would be safe to manage the xstatic requirements and upper-constraints locally. Technica

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

> On 09 Mar 2016, at 08:43, Sukhdev Kapur wrote: > > Hi Marc, > > I am driving the ironic-ml2 integration and introduced baremetal type for > vmic_type. Basically that’s my plan. So in my current implementation I use the baremetal vnic_type [1] and add a binding profile [2]. > You can very

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

Sent from HUAWEI AnyOffice 发件人：shinobu.kj 收件人：openstack-dev, 抄送：openst...@lists.openstack.org, 时间：2016-03-08 19:21:15 主题:Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo ) If you want anyone to joint this linuxcon to present the Tricle, let me know. IMHO I could -; Cheers, S On Tu

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

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 some investigation, it appears your tarball jobs were broken up until h

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

Interesting, maybe we can co-present on Tricircle in Linux con. For the m-l is mainly for development topics. Let's move it to non-maillist discussion. Sent from HUAWEI AnyOffice 发件人：shinobu.kj 收件人：openstack-dev, 抄送：openst...@lists.openstack.org, 时间：2016-03-08 19:21:15 主题:Re: [openstack-dev] [Tri

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

Irc? On Mar 9, 2016 5:50 PM, "joehuang" wrote: > > Interesting, maybe we can co-present on Tricircle in Linux con. For the m-l > is mainly for development topics. Let's move it to non-maillist discussion. > > Sent from HUAWEI AnyOffice > *发件人：*shinobu.kj > *收件人：*openstack-dev, > *抄送：*openst...@l

Re: [openstack-dev] [Tricircle] LinuxCon+Container Con (Tokyo )

#openstack-tricircle ? On Wed, Mar 9, 2016 at 4:55 PM, Shinobu Kinjo wrote: > Irc? > On Mar 9, 2016 5:50 PM, "joehuang" wrote: > >> >> Interesting, maybe we can co-present on Tricircle in Linux con. For the m-l >> is mainly for development topics. Let's move it to non-maillist discussion. >> >

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

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 some investigation, it a

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

2016-03-09 7:43 GMT+09:00 Armando M. : > > > On 8 March 2016 at 15:07, Doug Hellmann wrote: >> >> Excerpts from Armando M.'s message of 2016-03-08 12:49:16 -0700: >> > Hi folks, >> > >> > There's a feature or two that are pending to be delivered in Mitaka >> > [1,2], >> > and those involve changes

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

On 9 March 2016 at 07:08, Richard Su wrote: > > > On 03/08/2016 09:58 AM, 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 at 16:58, Jame

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

[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

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 s

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

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 new people in oslo.mes

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: > > > On Mon, Mar 7, 2016 at 8:57

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 job! +1 from my side though I am not a core. > >

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 any issues, and the patch

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 Mitaka, but it just adds the > model-migration te

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

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 you think? >> >> I agree that [1] should be included in Mitaka, bu

[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 needed.

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 a

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 needed.

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

[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: > > 20

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 at 16:58, James Slagle > > > > wrote: > >

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

ack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsu

Re: [openstack-dev] [Mistral] Mistral with IPV6

Hi, Guy! I think there is the same issue as in ceilometerю Furthermore, Mistral and Ceilometer are using the same framework for constructing their Rest API. So, the fix probably should be the same. On Wed, Mar 9, 2016 at 4:15 PM, Paz, Guy (Nokia - IL) wrote: > > > Hello, > > We are trying to de

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

On 03/09/2016 01:11 AM, Tim Bell wrote: From: Matt Fischer mailto:m...@mattfischer.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Tuesday 8 March 2016 at 20:35 To: "OpenStack Development Mailing List (not for usa

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

On 2016-03-09 09:47:41 +0100 (+0100), Thierry Carrez wrote: > Could we retrigger a neutron-vpnaas-tarball job pointing to the 8.0.0.0b3 > tag so that the tarball is properly generated and uploaded ? No, because that state of neutron-vpnaas is broken (it needs Andreas' tox.ini fix to work) so would

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

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 but I'll go as far as saying there are personal and professional reasons for me to not run a

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

On 03/09/2016 01:44 AM, Matt Fischer wrote: I don't think your example is right: "PKI will validate that token without going to any keystone server". How would it track revoked tokens? I'm pretty sure that they still get validated, they are stored in the DB even.

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

Excerpts from Thierry Carrez's message of 2016-03-09 11:35:45 +0100: > 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.

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

Vikash Kumar wrote: On Wed, Mar 9, 2016 at 3:42 PM, Vikash Kumar wrote: I have written a sample neutron agent which subscribe for the AFTER_CREATE event of router. I have defined a sample method as callback, but the method doesn't gets called anytime. Also, in logs: 2016-03-09 01:36

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

Henry Gessau wrote: By tomorrow we intend to tag the heads of all the neutron alembic branches with the MITAKA label [1][2][3][4]. If you have a patch that adds an alembic migration and you want to get it in Mitaka you must be associated with a targeted BP/RFE/bug [5] and get your code me

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

Hi, Plugin examples mustn't be removed, those plugins are part of integration tests for fuel plugin builder, which should be able to build any version of plugin. So there are two ways to solve the problem: 1. Before test run update compatibility matrix for plugins automatically. 2. Continue fixin

Re: [openstack-dev] [glance] Austin Design Summit space needs

On 24/02/16 11:42 -0400, Flavio Percoco wrote: Hey Folks, It's that time of the year. We need to choose what our needs with regards to slots and sessions are for the next summit. We can choose among 3 different types of sessions: * Fishbowl slots (Wed-Thu) Our traditional largish rooms organiz

[openstack-dev] [kolla] ubuntu deploy gate

The ubuntu deploy gate is failing because of commit 7f6de0a7e0d784181a6f99270768712e761f113a. Please see review https://review.openstack.org/#/c/290243/ for more details. For the moment ignore the ubuntu deploy gate un

Re: [openstack-dev] [Fuel] Overriding and removing VIPs from plugins

Guys, I suppose that any solution for the plugins merge ordering issue (either alerting about error or allowing user to manually set order) would be very helpful and much better then no solution at all (like we currently have). Maybe we should create a blueprint to not miss/forget about it? Regar

Re: [openstack-dev] [keystone] Using multiple token formats in a one openstack cloud

On Wed, Mar 9, 2016 at 7:19 AM, Adam Young wrote: > On 03/09/2016 01:11 AM, Tim Bell wrote: > > > From: Matt Fischer < m...@mattfischer.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Tuesday 8 March 2016 at 20:35 > To

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

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 were done for master in [9] on master, and [7]

[openstack-dev] [puppet] [neutron] Adding puppet-ovn part of Puppet OpenStack

Hi, networking-ovn is a project part of OpenStack Neutron: http://docs.openstack.org/developer/networking-ovn/readme.html "OVN provides virtual networking for Open vSwitch and is a component of the Open vSwitch project. This project provides integration between OpenStack Neutron and OVN." Red Ha

Re: [openstack-dev] [app-catalog] Nominating Kirill Zaitsev to App Catalog Core

Thanks everyone, this is an honor and great responsibility. I would do my best as App Catalog Core.  --  Kirill Zaitsev Software Engineer Mirantis, Inc On 9 March 2016 at 05:50:53, Christopher Aedo (d...@aedo.net) wrote: On Thu, Mar 3, 2016 at 1:10 PM, Christopher Aedo wrote: > I'd like to p

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

Igor, i completely agree, actually plugin examples is almost a copy-paste. The only thing i see useful in the built plugins example is the ability to point some code lines, discussing plugin design and writing documentation. Why not to generate this examples automatically from templates? Also, as

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

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: > > > Hi folks, > > > > > > There's a feature or two that are pending to be delivered in Mitaka > > [1,2], > > >

Re: [openstack-dev] [all][release] Release countdown for week R-4, Mar 7 - 11

Excerpts from Sergey Kraynev's message of 2016-03-09 11:08:32 +0300: > Hi Doug. > > I have one question related with last item: "Release actions". > Who will prepare patches for Reno and for updating .gitreview? > Should it be done by related project team or it will be done by someone else? The s

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

Ilya, What do you mean by "templates" the plugin which is create by just "fpb --create plugin-name"? It doesn't cover enough, package installation and all range of tasks executions. Thanks, On Wed, Mar 9, 2016 at 6:16 PM, Ilya Kutukov wrote: > Igor, i completely agree, actually plugin examples

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

r/is almost a copy-paste/is almost a copy-paste from plugins templates On Wed, Mar 9, 2016 at 6:16 PM, Ilya Kutukov wrote: > Igor, i completely agree, actually plugin examples is almost a copy-paste. > > The only thing i see useful in the built plugins example is the ability to > point some code

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: > > > > Hi folks, > > > > > > > > There's a featur

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: > Ilya, > > What do

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)" mailto:std...@cisco.com>> Reply-To: "openstack-dev@lists.openstack.org

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 f

[openstack-dev] [all][infra] Switching images for testing

We're migrating already since Friday jobs using the so-called bare-trusty images to ubuntu-trusty images. These images are used for for most of unit and functional tests, for documentation etc. Devstack is still run on devstack-trusty nodes for now, but will also move at a later date. A direct be

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

On 03/07/2016 10:52 PM, Richard Jones wrote: We've solved *most* of the issues around releasing new xstatic packages, documented here[1] (and related documentation). We have one final issue that's blocking us, which is that during the xstatic release there will be a point at which Horizon may be

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

Because it doesn't make much sense for a plugin developer to have scripts to build packages for installation on slave nodes. For default template it's better to have something minimalistic and the rest of the tasks commented, otherwise it may create a lot of confusion. On Wed, Mar 9, 2016 at 6:37

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 library, which is not even us

Re: [openstack-dev] [L2-Gateway] Install and Configuration issue

Hi Irena, I was not clear in my initial message...but I am using the stable/liberty branch. It is interesting that the master branch has this set in the plugin now. Clearly the code is evolving a bit for Mitaka. However you helped me to discover what was wrong (I think). I forgot to change to the

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

Colette Alexander wrote: On Tue, Mar 8, 2016 at 1:37 PM, Doug Hellmann mailto:d...@doughellmann.com>> wrote: As I understood it when this course was originally proposed, the idea was to have a few folks already in leadership positions go take the training and evaluate it. Then, assu

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

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 >> 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 met

[openstack-dev] [nfv][telco] Telco Working Group meeting for Wednesday Marcch 16th CANCELLED

Hi all, There will be no Telco Working Group [1] meeting for Wednesday March 16th as we will be lacking a chair. Thanks, Steve [1] https://wiki.openstack.org/wiki/TelcoWorkingGroup __ OpenStack Development Mailing List (n

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

+1, Diana's contribution to the front-end aspect of Horizon during several recent release cycles was second to none! On Wed, Mar 9, 2016 at 2:15 AM Richard Jones wrote: > +1 we need Diana's perspective, knowledge and enthusiasm > > On 9 March 2016 at 10:03, Tripp, Travis S wrote: > >> +1, no qu

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

On 2016-03-09 15:32:58 + (+), Vikram Hosakote (vhosakot) wrote: > FYI, the bug is seen in Ubuntu gate just on devstack-trusty-rax > machine and not on devstack-trusty-osic and > devstack-trusty-ovh. Due to long-standing issues uploading images to Rackspace's Glance implementation (and a

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

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 alwa

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 > > take the training a

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 16

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

On 9 March 2016 at 08:16, 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: > > > > Hi folks, > > > > > > > > There's a feature or t

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 want to get it >> in >> Mitaka you must be

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

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 > >> wrote: > >> I have written a sample neutron agent which subscribe for the > AFTER_CREATE > >> ev

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 wrote: > >> On Wed

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 have a few folks already in

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

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 20

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: > >> > >>> > >>> > >>> As I understood it when

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 versions from which > w

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? > > > > On 3/4/2016 6:27 AM, Markus Zoeller wrote: > > What's t

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 wrote

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 wer

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

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

[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 https://wiki.openstack

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 Riedema

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, given -stable > originated from

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 create stable/mitaka branch

[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: open

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] [release][all][ptl] preparing to creat

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 specify the dependencies twice

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 channel is also for packaging disc

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

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 an

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 workarounds for poor pa

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 cross-distr

  1   2   >