[openstack-dev] [heat][infra] heat-templates dsvm gate

Hi all, I would like to discuss how to fix and improve $subject, which targets to validate the templates present in the repo. Current state is the following: the gate does merely validate the "parseability" of YAML/JSON templates and very basic check on template structure. Any other real checks a

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

+1 thanks for all the hard work Richard! On Wed, Dec 2, 2015 at 7:56 PM, David Lyle wrote: > I propose adding Richard Jones[1] to horizon-core. > > Over the last several cycles Timur has consistently been providing > great reviews, actively participating in the Horizon community, and > making me

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

+1 thanks for all the hard work! And Timur will fix pagination too :) On Wed, Dec 2, 2015 at 7:52 PM, David Lyle wrote: > I propose adding Timur Sufiev[1] to horizon-core. > > Over the last several cycles Timur has consistently been providing > great reviews, actively participating in the Horizo

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

> -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > > On Wed, Dec 02 2015, AFEK, Ifat (Ifat) wrote: > > > Can this be supported without defining an alarm for every VM > separately? > > No, it's not possible. You'd have to create the alarm for each instance > for now.

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Ryota, Thanks for your response, please see my comments below. Ifat. > -Original Message- > From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com] > > Hi, > > > Sorry for my late response... > > It seems like a fundamental question whether we should have rich > function or intelligence in

[openstack-dev] Open Cloud Symposium Call for Proposals – LCA2016

We are pleased to announce that the call for proposals to the Open Cloud Symposium for linux.conf.au 2016 is now open! The symposium – a one day mini-conference dedicated to all things cloud – will be held on Monday 01 February 2016 in Geelong, Victoria as part of linux.conf.au 2016. Presentation

Re: [openstack-dev] [Openstack-operators] [nova] [openstack-operators] Tools to move instances between projects?

Excerpts from Kris G. Lindgren's message of 2015-12-02 15:43:13 -0800: > I can describe our specific uses cases, not sure our same limitations apply > to everyone. > > Every developer in our company has a project created for them (user-username) > they are allowed to spinup 5 vm's in this projec

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 2 December 2015 at 01:16, Thierry Carrez wrote: > Armando M. wrote: > >> One solution is, like you mentioned, to make some (or all) of them > >> full-fledged project teams. Be aware that this means the TC would judge > >> those new project teams individually and might reject them if we feel >

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

+1, now we can see more merges in angular patches. On 12/03/2015 12:22 AM, David Lyle wrote: I propose adding Timur Sufiev[1] to horizon-core. Over the last several cycles Timur has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi, Sorry for my late response... It seems like a fundamental question whether we should have rich function or intelligence in on-the-fly event alarm evaluation. I think we can add simple operations (like aggregating alarm) in aodh evaluator, and other operations (like deducing with referring

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

It would be better if we can document the scenarios / cases where individual tests make sense. As a developer this confuses me the most. On Thu, Dec 3, 2015 at 10:21 AM, Takashi Yamamoto wrote: > hi, > > On Thu, Dec 3, 2015 at 11:19 AM, Armando M. wrote: > > Hi Neutrinos, > > > > I would like t

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

hi, On Thu, Dec 3, 2015 at 11:19 AM, Armando M. wrote: > Hi Neutrinos, > > I would like to share a proposal with you on how we could scale our > ever-growing testing needs, and at the same time, provide guidance to the > developers who care about the quality of the work they produce, and how they

Re: [openstack-dev] [magnum] Mesos Conductor

Hi Bharath, Actually I have already filed a bp here: https://blueprints.launchpad.net/magnum/+spec/unify-coe-api ,sorry for the late notify. We may need some discussion for this in next Week's meeting. I will attend next week's meeting and we can have discussion with team then, hope it is OK. ;-)

Re: [openstack-dev] [neutron][midonet] networking-midonet weekly irc meeting

On Mon, Nov 30, 2015 at 12:52 PM, Takashi Yamamoto wrote: > hi, > > we are going to migrate networking-midonet meeting from slack to irc. > the plan is to have it 7:00 UTC on every Tuesdays. > if you are interested but have a different time preference, > please speak up. > thank you. it will be h

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On 12/01/2015 03:50 PM, Fox, Kevin M wrote: I just upgraded to keystone liberty for one of my production clouds, and went with apache since eventlet was listed as deprecated. It was pretty easy. Just ran into one issue. RadosGW wouldn't work against it until I added "WSGIChunkedRequest On'" in

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

On 12/02/2015 01:57 PM, David Lyle wrote: Let's try that again. I propose adding Richard Jones[1] to horizon-core. Over the last several cycles Richard has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions around angu

Re: [openstack-dev] [release] preparing your mitaka-1 milestone tag

Excerpts from Zane Bitter's message of 2015-12-02 19:17:25 -0500: > On 27/11/15 09:32, Doug Hellmann wrote: > > Next week (Dec 1-3) is the Mitaka 1 milestone deadline. Release > > liaisons for all managed projects using the cycle-with-milestones > > release model will need to propose tags for their

[openstack-dev] [app-catalog] IRC Meeting Thursday December 3rd at 17:00UTC

Hi there! Tomorrow we'll have our next OpenStack Community App Catalog meeting (Dec 3rd) at 1700UTC 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 cour

Re: [openstack-dev] [puppet] Config support for oslo.config.cfg.MultiStrOpt

Martin, I see no reason this shouldn't just be pushed into puppetlabs-inifile. I can't actually find a real "spec" for INI file and even the Wiki link[3] calls out that there is no actual spec. On Fri, Nov 27, 2015 at 5:04 AM, Martin Mágr wrote: > Greetings, > > I've submitted patch to puppe

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

Hi Neutrinos, I would like to share a proposal with you on how we could scale our ever-growing testing needs, and at the same time, provide guidance to the developers who care about the quality of the work they produce, and how they can protect it from the dreadful regressions! In [1] you will se

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

I was not a deputy - but I had been subscribed to launchpad bugs for years, but had a procmail filter set so it went into a folder that prior to this new initiative, had remained unread for years. As part of this new effort I try and spend at least 15 minutes a day checking the folder and working o

Re: [openstack-dev] [release] preparing your mitaka-1 milestone tag

On 27/11/15 09:32, Doug Hellmann wrote: Next week (Dec 1-3) is the Mitaka 1 milestone deadline. Release liaisons for all managed projects using the cycle-with-milestones release model will need to propose tags for their repositories by Thursday. Tag requests submitted after Dec 3 will be rejected

[openstack-dev] [swift] tracking todo items

Sometimes there's stuff you want to change in a project, but it's not really a bug, and it's not really something big either. Adding it to the bug tracker doesn't quite seem right, and it seems like needless paperwork to make a blueprint or spec for it. So how do we track these things so we don'

Re: [openstack-dev] [nova] [openstack-operators] Tools to move instances between projects?

Excerpts from Kris G. Lindgren's message of 2015-12-02 12:52:10 -0800: > Hello, > > I was wondering if someone has a set of tools/code to work allow admins to > move vm's from one tenant to another? We get asked this fairly frequently in > our internal cloud (atleast once a week, more when we s

Re: [openstack-dev] [Openstack-operators] [nova] [openstack-operators] Tools to move instances between projects?

I can describe our specific uses cases, not sure our same limitations apply to everyone. Every developer in our company has a project created for them (user-username) they are allowed to spinup 5 vm's in this project to do dev/test/POC whatever. These projects are not tied into show back or us

Re: [openstack-dev] [FUEL] FFE request for erlang and rabbitmq-server packaged for centos7

Based on time of this request, you seem to be late to the party... FF is in action. Formally it was requested before FF, but as I mentioned in my email [1], we'd need at least a day for consider exception and assess related risks. Filing it couple of hours before FF doesn't give a chance to do it.

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

OK, thanks for the input. I'll get the patches out to enable this by Friday this week, once Mitaka-1 is cut for Neutron. On Wed, Dec 2, 2015 at 11:34 AM, Brandon Logan wrote: > Makes complete sense. > > On Wed, 2015-12-02 at 10:38 -0600, Kyle Mestery wrote: > > We're hoping to cut Neutron M-1 th

Re: [openstack-dev] [Openstack-operators] [nova] [openstack-operators] Tools to move instances between projects?

On 12/2/2015 2:52 PM, Kris G. Lindgren wrote: Hello, I was wondering if someone has a set of tools/code to work allow admins to move vm's from one tenant to another? We get asked this fairly frequently in our internal cloud (atleast once a week, more when we start going through and cleaning u

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

+1 from me From: David Lyle Sent: Thursday, 3 December 2015 5:52 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core I propose adding Timur Sufiev[1] to horizon-core. Over the las

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

Another +1 from me From: David Lyle Sent: Thursday, 3 December 2015 5:57 AM To: OpenStack Development Mailing List Subject: Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core Let's try that again. I propose adding Richard Jones[1

Re: [openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

Thanks team for stepping up to fill this important role. Please let me know if there is anything I can do to assist you. Adrian On Dec 2, 2015, at 2:19 PM, Everett Toews mailto:everett.to...@rackspace.com>> wrote: On Dec 2, 2015, at 12:32 AM, 王华 mailto:wanghua.hum...@gmail.com>> wrote: Adria

Re: [openstack-dev] [magnum][api] Looking for a Cross-Project Liaison for the API Working Group

On Dec 2, 2015, at 12:32 AM, 王华 mailto:wanghua.hum...@gmail.com>> wrote: Adrian, I would like to be an alternate. Regards Wanghua On Wed, Dec 2, 2015 at 10:19 AM, Adrian Otto mailto:adrian.o...@rackspace.com>> wrote: Everett, Thanks for reaching out. Eli is a good choice for this role. We sh

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Hello, Here is our status (Dec, 2). We are on track now. This (Dec, 2) morning we've got results of 6 tests (swarm) - 3 succeeded, 3 failed. Failures were caused issues in ISO and QA scripts, and were fixed during the day. In the end of the day (Dec, 2) we've got another green custom ISO, which

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

+1! On 3 December 2015 at 07:31, Matthias Runge wrote: > On 02/12/15 19:52, David Lyle wrote: > > I propose adding Timur Sufiev[1] to horizon-core. > > > > Over the last several cycles Timur has consistently been providing > > great reviews, actively participating in the Horizon community, and >

Re: [openstack-dev] [Sahara] Instance customization for Bootstrapping the cluster nodes

Hi, we don't have such feature right now. It could be implemented by adding support for defining user data on the templates level. We already passing some user data to the VMs, so, it'll be really easy to implement it in Sahara. You can submit spec or blueprint for it. Thanks. On Wed, Nov 25, 2

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 2015-11-25 14:02:47 +0800 (+0800), Tom Fifield wrote: [...] > Putting this out there - over at the Foundation, we're here to > Protect and Empower you. So, if you've ever been reprimanded by > management for choosing not to abuse the community process, > perhaps we should arrange an education se

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 2015-11-23 21:20:56 + (+), David Chadwick wrote: > Since the ultimate arbiter is the PTL, then it would be wrong to allow > members of the same organisation as the PTL to perform all three code > functions without the input of anyone from any other organisation. This > places too much po

Re: [openstack-dev] [keystone][all] Move from active distrusting model to trusting model

On 2015-11-24 11:43:26 +0100 (+0100), Thierry Carrez wrote: > Right. The code is either in and supported by everyone, or out. [...] And as mentioned in Morgan's original post, it can be both at different points in time. Contributions should be approved or not on their own merits and not those of t

Re: [openstack-dev] [oslo] A special thank you to Davanum (Dims)

On 2015-11-23 10:49:23 -0800 (-0800), Joshua Harlow wrote: > Dims is my hero ;) > > Lol, this thread is interesting :-P Wholeheartedly seconded (thirded? fourthed?)! It's awesome to congratulate someone on how great they are when they're not in the middle of stepping down from something for once.

Re: [openstack-dev] [stable] Post-release bump after 2014.2.4?

On 2015-11-24 14:34:19 +0100 (+0100), Alan Pevec wrote: > > But to illustrate better the issue I'm seeing: > > http://tarballs.openstack.org/cinder/cinder-stable-juno.tar.gz contains > > a directory cinder-2014.2.4.dev24, which is kind of wrong. That's the > > bit that I'd like to see fixed. > > T

Re: [openstack-dev] Learning to Debug the Gate

On 11/23/2015 02:19 PM, Anita Kuno wrote: > On 11/18/2015 06:03 PM, Mikhail Medvedev wrote: >> We had a mini tutorial today in #openstack-infra, were Clark Boylan >> explained how one can bring up an environment to debug logstash-2.0. >> This is tangential to "debugging the gate", but still could b

Re: [openstack-dev] [stable][infra][qa] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 12/2/2015 2:33 PM, Jeremy Stanley wrote: [Apologies for the delayed reply, after more than a week without Internet access it's taking me more than a week to catch up with everything on the mailing lists.] On 2015-11-20 10:21:47 + (+), Kuvaja, Erno wrote: [...] So we were brainstorm

[openstack-dev] [Murano] How to debug a failed deployment?

Hello, I am trying to deploy a hello world HOT package in murano but the deployment runs forever and does not stop (does not succeed or fail). Stan advised me to modify the config setting below to set a timeout: # Time for waiting for a response from murano agent during the # deployment (integer

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

On 11/30/2015 09:04 AM, Coffman, Joel M. wrote: On 11/25/15, 11:33 AM, "Ben Swartzlander" mailto:b...@swartzlander.org>> wrote: On 11/24/2015 03:27 PM, Nathan Reller wrote: the cinder admin and the nova admin are ALWAYS the same people There is interest in hybrid clo

[openstack-dev] [nova] [openstack-operators] Tools to move instances between projects?

Hello, I was wondering if someone has a set of tools/code to work allow admins to move vm's from one tenant to another? We get asked this fairly frequently in our internal cloud (atleast once a week, more when we start going through and cleaning up resources for people who are no longer with t

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

+1 for both Richard and Timur. Great additions to the team! Doug Fish     - Original message -From: "Chen, Shaoquan" To: "OpenStack Development Mailing List (not for usage questions)" Cc:Subject: Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-coreDate: Wed, Dec 2, 20

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

On 02/12/15 19:57, David Lyle wrote: > Let's try that again. > > I propose adding Richard Jones[1] to horizon-core. > Please respond with comments, +1s, or objections within one week. Yes, +1 from me. Matthias __ OpenStack

Re: [openstack-dev] [stable][infra][qa] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

[Apologies for the delayed reply, after more than a week without Internet access it's taking me more than a week to catch up with everything on the mailing lists.] On 2015-11-20 10:21:47 + (+), Kuvaja, Erno wrote: [...] > So we were brainstorming this with Rocky the other night. Would > th

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

On 02/12/15 19:52, David Lyle wrote: > I propose adding Timur Sufiev[1] to horizon-core. > > Over the last several cycles Timur has consistently been providing > great reviews, actively participating in the Horizon community, and > making meaningful contributions particularly around testing and >

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

We need to run the normal Swarm on Thu to assess the damage from the FF merge party. If we manage to run a custom Swarm in parallel with that, we should, but normal Swarm takes priority. If we can't run custom Swarm on Thu, we have to rely on the results from normal Swarm on Fri. On Dec 2, 2015 10

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

+1 for both Timur and Richard! On 12/2/15, 10:57 AM, "David Lyle" wrote: >Let's try that again. > >I propose adding Richard Jones[1] to horizon-core. > >Over the last several cycles Richard has consistently been providing >great reviews, actively participating in the Horizon community, and >mak

Re: [openstack-dev] OpenStack-Announce List

On 2015-11-20 11:41:43 +0100 (+0100), Thierry Carrez wrote: > Tom Fifield wrote: [...] > > * Important security advisories > > Actually it's all security advisories, not just "important" ones. [...] I would counter that the VMT don't bother to write and publish "unimportant" security advisories,

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

Makes complete sense. On Wed, 2015-12-02 at 10:38 -0600, Kyle Mestery wrote: > We're hoping to cut Neutron M-1 this week [1]. We have implemented > release notes in the main Neutron repository [2] , but not in the *aaS > repositories. At the time, I thought this was a good approach and we > could

[openstack-dev] [fuel] Fuel 8.0 Feature Freeze

Fuel 8.0 (based on Liberty) is now in Feature Freeze [0]. [0] https://wiki.openstack.org/wiki/FeatureFreeze Aside from feature commits that have received feature freeze exceptions listed in Mike's email [1], only bugfix commits are now allowed to be merged. [1] http://lists.openstack.org/piperma

Re: [openstack-dev] [Fuel][FFE] Disabling HA for RPC queues in RabbitMQ

2015-12-02 16:52 GMT+03:00 Jordan Pittier : > > On Wed, Dec 2, 2015 at 1:05 PM, Dmitry Mescheryakov < > dmescherya...@mirantis.com> wrote: > >> >> >> My point is simple - lets increase our architecture scalability by 2-3 >> times by _maybe_ causing more errors for users during failover. The >> fai

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

Timur, I'm sure you can chime in even if your vote doesn't count [yet]! On Wed, Dec 2, 2015 at 12:11 PM, Tripp, Travis S wrote: > Definite +1 for me. I think they are great additions to the team! > > -Travis > > > > > > On 12/2/15, 11:57 AM, "David Lyle" wrote: > > >Let's try that again. > >

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

Definite +1 for me. I think they are great additions to the team! -Travis On 12/2/15, 11:57 AM, "David Lyle" wrote: >Let's try that again. > >I propose adding Richard Jones[1] to horizon-core. > >Over the last several cycles Richard has consistently been providing >great reviews, actively

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On 30 November 2015 at 11:25, Gururaj Grandhi wrote: > Hi, > > > > This is to announce that we have setup a Third Party CI > environment for Proliant iLO Drivers. The results will be posted under > "HP Proliant CI check" section in Non-voting mode. We will be running > the basic dep

Re: [openstack-dev] [Fuel] Feature Freeze Exception Request: Task Based Deployment in Astute

Correct. See my summary email at http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html . On Wed, Dec 2, 2015 at 10:11 AM Igor Kalnitsky wrote: > Hey folks, > > As we decided on today's IRC meeting in #fuel-dev, FFE exception is > granted on the following conditions (if get

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Dmitry, thank you! I confirm that the plan looks good for our team, we'll follow it. Regards, Igor Marnat On Wed, Dec 2, 2015 at 9:39 PM, Andrew Maksimov wrote: > Thank you Dmitry for very detailed plan and risks assessment. > Do we want to run swarm against custom iso with centos7 on Thu even

Re: [openstack-dev] [Fuel][FFE] Component registry

ETA Wednesday, 10th Summary of meeting: http://lists.openstack.org/pipermail/openstack-dev/2015-December/081131.html On Wed, Dec 2, 2015 at 10:07 AM Igor Kalnitsky wrote: > Fuelers, > > As we decided on today's IRC meeting in #fuel-dev, FFE is granted for > 1 week only. > > Thanks, > igor > > On

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

Well, I'm not sure if I'm eligible to chime in (yet), but IMO Richard is the first candidate here (and me is the second one) :). On Wed, Dec 2, 2015 at 9:59 PM Rob Cresswell (rcresswe) wrote: > An equally big +1! > > On 02/12/2015 18:56, "David Lyle" wrote: > > >I propose adding Richard Jones[1

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

I only have some historical, anecdotal, and rapidly waning memory of previous releases. Nevertheless my feeling is that the process has been a success so far. In past times it would not have been a surprise if a bug fell under the radar until that well known brownish matter hit the proverbial fan.

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

٩(͡๏̮͡๏)۶ +1! On Wed, Dec 2, 2015 at 11:58 AM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > An equally big +1! > > On 02/12/2015 18:56, "David Lyle" wrote: > > >I propose adding Richard Jones[1] to horizon-core. > > > >Over the last several cycles Timur has consistently been providin

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

+1! On Wed, Dec 2, 2015 at 11:57 AM, Rob Cresswell (rcresswe) < rcres...@cisco.com> wrote: > A big +1 for me! > > On 02/12/2015 18:52, "David Lyle" wrote: > > >I propose adding Timur Sufiev[1] to horizon-core. > > > >Over the last several cycles Timur has consistently been providing > >great rev

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

An equally big +1! On 02/12/2015 18:56, "David Lyle" wrote: >I propose adding Richard Jones[1] to horizon-core. > >Over the last several cycles Timur has consistently been providing >great reviews, actively participating in the Horizon community, and >making meaningful contributions around angul

Re: [openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

A big +1 for me! On 02/12/2015 18:52, "David Lyle" wrote: >I propose adding Timur Sufiev[1] to horizon-core. > >Over the last several cycles Timur has consistently been providing >great reviews, actively participating in the Horizon community, and >making meaningful contributions particularly ar

Re: [openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

Let's try that again. I propose adding Richard Jones[1] to horizon-core. Over the last several cycles Richard has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions around angularJS and overall project stability and heal

[openstack-dev] [horizon] Proposal to add Richard Jones to horizon-core

I propose adding Richard Jones[1] to horizon-core. Over the last several cycles Timur has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions around angularJS and overall project stability and health. Please respond with

[openstack-dev] [horizon] Proposal to add Timur Sufiev to horizon-core

I propose adding Timur Sufiev[1] to horizon-core. Over the last several cycles Timur has consistently been providing great reviews, actively participating in the Horizon community, and making meaningful contributions particularly around testing and stability. Please respond with comments, +1s, or

[openstack-dev] [Neutron] Bug deputy process

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

[openstack-dev] [Fuel] Feature Freeze Exceptions

Hi all, we ran a meeting and made a decision on feature freeze exceptions. Full log is here: https://etherpad.openstack.org/p/fuel-8.0-FF-meeting The following features were granted with feature freeze exception: 1. CentOS 7. ETA: Monday 7th. Blueprint: https://blueprints.launchpad.net/fuel

Re: [openstack-dev] [all][oslo] On Python 3, request_id must by Unicode, not bytes

Seems ok with me, not ideal but knowing the support of python 3.x in openstack it doesn't seem harmful to fix this while we still are able to; and in general if thats 'req-$uuid' ascii/unicode should be fine (since that's all that is). -Josh Victor Stinner wrote: Hi, The next oslo.context r

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Thank you Dmitry for very detailed plan and risks assessment. Do we want to run swarm against custom iso with centos7 on Thu evening to measure level of regression? I remember that we were considering this approach. Regards, Andrey Maximov On Wed, Dec 2, 2015 at 12:48 AM, Dmitry Borodaenko wrot

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

+1 Regards, Martin From: Kyle Mestery To: openstack-dev@lists.openstack.org Date: 02/12/2015 16:40 Subject:[openstack-dev] [neutron] Release Notes for *aaS projects We're hoping to cut Neutron M-1 this week [1]. We have implemented release notes in the main Neutron reposit

Re: [openstack-dev] [Fuel] Feature Freeze Exception Request: Task Based Deployment in Astute

Hey folks, As we decided on today's IRC meeting in #fuel-dev, FFE exception is granted on the following conditions (if get them right): * the feature is marked as experimental * patches should be merged by the end of next week Thanks, igor On Tue, Dec 1, 2015 at 10:01 PM, Vladimir Kuklin wrote

Re: [openstack-dev] [Fuel][FFE] Component registry

Fuelers, As we decided on today's IRC meeting in #fuel-dev, FFE is granted for 1 week only. Thanks, igor On Wed, Dec 2, 2015 at 5:42 PM, Andrian Noga wrote: > Colleagues, > > Folks, > I would like to request feature freeze exception for Component registry > https://blueprints.launchpad.net/fuel

Re: [openstack-dev] [cinder][nova]Move encryptors to os-brick

From: "duncan.tho...@gmail.com" mailto:duncan.tho...@gmail.com>> Reply-To: "openstack-dev@lists.openstack.org" mailto:openstack-dev@lists.openstack.org>> Date: Monday, November 30, 2015 at 9:13 AM To: "openstack-dev@list

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

I’m in favor of things living in the repo where their code lives. The fewer dependencies the better. Especially if we stop adding them. So, I agree. doug > On Dec 2, 2015, at 9:38 AM, Kyle Mestery wrote: > > We're hoping to cut Neutron M-1 this week [1]. We have implemented > release notes in

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

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

Re: [openstack-dev] [Fuel] Nominating Dmitry Burmistrov to core reviewers of fuel-mirror

Mike, Yes, probably the best place to describe further plans is README file. I'll create a patch. Vladimir Kozhukalov On Tue, Dec 1, 2015 at 8:30 PM, Mike Scherbakov wrote: > Vladimir, > if you've been behind of this, could you please share further plans in > separate email thread or (better)

[openstack-dev] [FUEL] FFE request for erlang and rabbitmq-server packaged for centos7

Hello! We have got - erlang=18.1 https://review.fuel-infra.org/#/c/12896/ - rabbitmq-server=3.5.6 https://review.fuel-infra.org/#/c/12901/ packaged for ubuntu trusty in corresponding requests. Those requests are not merged yet but probably would today evening. We need some time to backport it for

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On 12/02/2015 11:56 AM, Jim Rollenhagen wrote: > On Mon, Nov 30, 2015 at 12:48:44PM -0500, Anita Kuno wrote: >> On 11/30/2015 12:33 PM, Dmitry Tantsur wrote: >>> I was there and I already said that I'm not buying into "spamming the >>> list" argument. There are much less important things that I see

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

Hi thanks Sean for bringing this point, I have been working on the change and on the (abandoned) spec. I'll try here to summarize all the discussions we had and what we decided. > From: Sean Dague [mailto:s...@dague.net] > Sent: 02 December 2015 13:31 > To: OpenStack Development Mailing List (no

Re: [openstack-dev] [Fuel] Feature Freeze is soon

Thank you all for participation. I'll write up a summary here in the next few hours. IRC log is unfortunately totally useless [1] due to freenode issues. Please help me to get the full log here: https://etherpad.openstack.org/p/fuel-8.0-FF-meeting [1] http://irclog.perlgeek.de/fuel-dev/2015-12-02

[openstack-dev] [release][barbican][heat][manila] finishing reno integration work

We have 3 managed projects following the release:cycle-with-milestones release model (barbican, heat, manila) that haven't completed the work to add reno to their projects for managing release notes. Please complete the work today so you don't miss the M-1 milestone deadline tomorrow. Doug _

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

On Wed, Dec 02 2015, AFEK, Ifat (Ifat) wrote: > As we understand it, if we take the first approach you describe, then we can > have an alarm refer to all the VMs in the system, but then if the alarm is > triggered by one VM or by five VMs, the result will be the same - only one > alarm will be act

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Julien, Please see our questions below. Ifat and Elisha. > -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > > On Wed, Dec 02 2015, ROSENSWEIG, ELISHA (ELISHA) wrote: > > Regarding the second point: Say we have 30 different types of alarms > > we might want to ra

[openstack-dev] [tc] Request for comment on requiring running Linux as DefCore capability

A recent change request for the DefCore guidelines to “Flag validation tests as being OS specific[1]" has sparked a larger discussion about whether DefCore should explictly require running Linux as a compute capability. The DefCore Committee has prepared a document[2] covering the issue and possibl

Re: [openstack-dev] [ironic] Announcing Third Party CI for Proliant iLO Drivers

On Mon, Nov 30, 2015 at 12:48:44PM -0500, Anita Kuno wrote: > On 11/30/2015 12:33 PM, Dmitry Tantsur wrote: > > I was there and I already said that I'm not buying into "spamming the > > list" argument. There are much less important things that I see here > > right now, even though I do actively use

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 2015-11-16 20:57:09 -0600 (-0600), Matt Riedemann wrote: [...] > Arguably we could still be testing grenade on stable/kilo by just > installing Juno 2014.2.4 (last Juno point release before EOL) and > then upgrading to stable/kilo. I encourage you, say in a month's time, to try "just" installin

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

On Wed, Dec 02 2015, ROSENSWEIG, ELISHA (ELISHA) wrote: > Regarding the second point: Say we have 30 different types of alarms we might > want to raise on an OpenStack instance (VM). What I understand from your > explanation is that when we create a new instance, we need to create 30 new > alarms

Re: [openstack-dev] [heat][tripleo] User Initiated Rollback

On 02/12/15 11:02, Steven Hardy wrote: So, chatting with Giulio today about https://bugs.launchpad.net/heat/+bug/1521944 has be thinking about $subject. The root case of that issue is essentially a corner case of a stack-update, combined with some coupling within the Neutron API which prevents

Re: [openstack-dev] [tripleo][ironic][heat] Adding back the tripleo check job

On Wed, Dec 02, 2015 at 03:58:01PM +, Derek Higgins wrote: > > > >Ah, I think all we have here is a terminology mismatch around "non voting" > >vs "non gating". > > > >AFAIK what is being proposed is to reinstate the TripleO jobs so they *do* > >vote on any change (+1/-1), but they do not blo

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 2015-11-17 02:49:30 + (+), Rochelle Grober wrote: > I would like to make a plea that while Juno is locked down so as > no changes can be made against it, the branch remains on the > git.openstack.org site. We don't so much delete the stable/juno branch as replace its final state with a

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

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

Re: [openstack-dev] [TripleO] RFC: profile matching

On 12/02/2015 03:59 AM, Dmitry Tantsur wrote: > On 12/01/2015 06:55 PM, Ben Nemec wrote: >> Sorry for not getting to this earlier. Some thoughts inline. >> >> On 11/09/2015 08:51 AM, Dmitry Tantsur wrote: >>> Hi folks! >>> >>> I spent some time thinking about bringing profile matching back in, so

[openstack-dev] [puppet] [tripleo] stop maintaining puppet-tuskar

Hi, I don't find any official statement on the Internet, but I've heard Tuskar is not going to be maintained anymore (tell me if I'm wrong). If I'm not wrong, I suggest we stop maintaining puppet-tuskar, and stable/liberty would be the latest release that we have maintained. I would also drop all

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

Hi, In Vitrage[3] project, we would like to be notified on every alarm that is triggered, and respond immediately (e.g. by generating RCA insights, or by triggering new alarms on other resources). We are now in the process of designing our integration with AODH. If I understood you correctly,

[openstack-dev] [Neutron] Liberty release for L2GW

Folks, This is to let everybody know that Liberty release for L2GW project is released and is available at - https://pypi.python.org/pypi/networking-l2gw Feel free to download it and use it. Please let us know if you see any issue with it. Authors of outstanding or new patches, please use your b

  1   2   >