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

I would add on top of that Dmirty said that HA queues also increases probability to have messages duplications under certain scenarios (besides of that they are ~10x slower). Would Openstack services tolerate if RPC request will be duplicated? What I've already learned - No. Also if

Re: [openstack-dev] [nova]New Quota Subteam on Nova

On Tue, 2015-12-01 at 11:45 -0800, Vilobh Meshram wrote: > Having worked in the area of Quotas for a while now by introducing > features like Cinder Nested Quota Driver [1] [2] I strongly feel that > something like a Nova Quota sub-team will definitely help. Mentioning > about Cinder Quota driver

Re: [openstack-dev] [swift] [oslo.messaging] [fuel] [ha] Is Swift going to support oslo.messaging?

Hi Mehdi, Thank you for your reply! It works for us. 2015-12-01 20:40 GMT+03:00 Mehdi Abaakouk : > Hi, > > Current scheme supports only one RabbitMQ node with url parameter. >> > > That's not true, you can pass many hosts via the url like that: >

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

2015-12-02 13:11 GMT+03:00 Bogdan Dobrelya : > On 01.12.2015 23:34, Peter Lemenkov wrote: > > Hello All! > > > > Well, side-effects (or any other effects) are quite obvious and > > predictable - this will decrease availability of RPC queues a bit. > > That's for sure. > >

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

Dmitry Although, I am a big fan of disabling replication for RPC, I think it is too late to introduce it so late by default. I would suggest that we control this part of OCF script with a specific parameter 'e.g. enable RPC replication' and set it to 'true' by default. Then we can set this option

Re: [openstack-dev] [nova] jsonschema for scheduler hints

Le 02/12/2015 15:23, Sean Dague a écrit : We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we handle that with our strict jsonschema is that we allow additional

Re: [openstack-dev] [ironic][inspector] CMDB integration

On Wed, Dec 2, 2015 at 5:23 PM, Dmitry Tantsur wrote: > What tripleo currently does is creating a JSON file with credentials in > advance, then enroll nodes with it. We were considering CSV as a starter. Cheers, Serge Kovaleff http://www.mirantis.com cell: +38 (063)

Re: [openstack-dev] [all] [glance] Proposal to add Abhishek to Glance core team

On 01/12/15 01:21 -0500, Nikhil Komawar wrote: Hi, As the requested (re-voting) on [1] seemed to conflict with the thread title, I am __init__ing a new thread for the sake of clarity, closure and ease of vote. Please do provide feedback on the proposal by me on this thread [1]. Other reference

Re: [openstack-dev] [nova] [ironic] Hardware composition

On 12/01/2015 02:44 PM, Vladyslav Drok wrote: Hi list! There is an idea of making use of hardware composition (e.g. http://www.intel.com/content/www/us/en/architecture-and-technology/rack-scale-architecture/intel-rack-scale-architecture-resources.html) to create nodes for ironic. The current

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

Is the meeting at 8am PST today? *From:* Mike Scherbakov [mailto:mscherba...@mirantis.com] *Sent:* Wednesday, December 02, 2015 1:57 AM *To:* OpenStack Development Mailing List (not for usage questions) < openstack-dev@lists.openstack.org> *Subject:* Re: [openstack-dev] [Fuel] Feature Freeze is

[openstack-dev] [nova] jsonschema for scheduler hints

We have previously agreed that scheduler hints in Nova are an open ended thing. It's expected for sites to have additional scheduler filters which expose new hints. The way we handle that with our strict jsonschema is that we allow additional properties -

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

Sheena, Yeah, we will have a meeting in #fuel-dev IRC channel. :) - Igor On Wed, Dec 2, 2015 at 4:25 PM, Sheena Gregson wrote: > Is the meeting at 8am PST today? > > > > From: Mike Scherbakov [mailto:mscherba...@mirantis.com] > Sent: Wednesday, December 02, 2015 1:57 AM

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,

Re: [openstack-dev] [ironic][inspector] CMDB integration

On 11/30/2015 03:07 PM, Pavlo Shchelokovskyy wrote: Hi all, we are looking at how ironic-inspector could integrate with external CMDB solutions and be able fetch a minimal set of data needed for discovery (e.g. IPMI credentials and IPs) from CMDB. This could probably be achieved with data

[openstack-dev] [Fuel][FFE] Provide possibilities to change VMware clusters on operational env

Colleagues, I would like to request feature freeze exception for Provide possibilities to change VMware clusters on operational env https://blueprints.launchpad.net/fuel/+spec/add-vmware-clusters Specification is ready for merge https://review.openstack.org/#/c/250469/12 Main patch for UI is

Re: [openstack-dev] [Fuel][library] CI gate for regressions detection in deployment data

On 01.12.2015 11:28, Aleksandr Didenko wrote: > Hi, > >> pregenerated catalogs for the Noop tests to become the very first >> committed state in the data regression process has to be put in the >> *separate repo* > > +1 to that, we can put this new repo into .fixtures.yml > >> note, we could as

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

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 the update traversal from working. But

[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

Re: [openstack-dev] [Fuel] Patch size limit

Hey folks, I agree that patches must be as small as possible. I believe it will significantly increase our review experience - more fast review, and, therefore, landing to master. However, I don't agree that we should introduce criteria based on LOC, because of mentioned reasons above. I believe

Re: [openstack-dev] [puppet] [ceph] Puppet Ceph CI

I pushed an overly optimistic review [1] for updating Openstack to Liberty. Haven't had the time to look back at it yet. The general idea was to defer the repository setup to openstack_extras and pull in the keystone setup mostly as-is directly from puppet-openstack-integration. [1]:

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

Vova, Folks, +1 to "set this option to false as an experimental feature" Thanks, Dims On Wed, Dec 2, 2015 at 10:08 AM, Vladimir Kuklin wrote: > Dmitry > > Although, I am a big fan of disabling replication for RPC, I think it is too > late to introduce it so late by

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

This seems like a totally reasonable solution, and would enable us to more thoroughly test the performance implications of this change between 8.0 and 9.0 release. +1 -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: Wednesday, December 02, 2015 9:32 AM To:

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

Colleagues, Folks, I would like to request feature freeze exception for Component registry https://blueprints.launchpad.net/fuel/+spec/component-registry Specification is already merged https://review.openstack.org/#/c/229306/ Main patch is also merged https://review.openstack.org/#/c/247913/ We

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

On 02/12/15 12:53, Steven Hardy wrote: On Tue, Dec 01, 2015 at 05:10:57PM -0800, Devananda van der Veen wrote: On Tue, Dec 1, 2015 at 3:22 AM, Steven Hardy wrote: On Mon, Nov 30, 2015 at 03:35:13PM -0800, Devananda van der Veen wrote: >Â Â On Mon, Nov

Re: [openstack-dev] [Neutron] need help in translating sql query to sqlalchemy query

Was perusing the documentation again this morning and there is another thing I found - you can call join() with the aliased=True flag to get similar results. Check out the "Constructing Aliases Anonymously" section. http://docs.sqlalchemy.org/en/latest/orm/query.html -- Sean M. Collins

Re: [openstack-dev] [ironic][inspector] CMDB integration

Another possible candidates we got from our discussions are *itop* and *Foreman*. Anything else? Cheers, Serge Kovaleff On Wed, Dec 2, 2015 at 5:34 PM, Serge Kovaleff wrote: > > On Wed, Dec 2, 2015 at 5:23 PM, Dmitry Tantsur > wrote: > >> What

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

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

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"

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

[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

[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

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

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

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

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

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

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

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

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

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

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

[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

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

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 >

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

From: "duncan.tho...@gmail.com" > Reply-To: "openstack-dev@lists.openstack.org" > Date:

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

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

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

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

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

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

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

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

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.

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"

[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

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

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

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

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

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 >

[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

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

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

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

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

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

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

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

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

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

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"

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

[openstack-dev] [watcher] weekly meeting agenda

Hello! Here is the agenda for our weekly meeting, today at 1400 UTC on #openstack-meeting-4 [1] Feel free to add any items you'd like to discuss. Thanks, Antoine [1] *https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#12.2F2.2F2015

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

Thanks all. All comments so far are from neutron side. I would like to wait inputs from horizon side, especially David. Option (c) is what we do in neutron sub-projects under neutron stadium model and I agree it makes sense and sounds natural to neutron folks. My initial mail just did not cover

Re: [openstack-dev] [midonet] IRC: ditch #midonet-dev?

On 2015年12月01日 19:14, Takashi Yamamoto wrote: On Tue, Dec 1, 2015 at 7:08 PM, Antoni Segura Puimedon wrote: On Tue, Dec 1, 2015 at 10:59 AM, Ivan Kelly wrote: +1 for #2 PS: Beware of the top-posting! It makes vote counting harder ;-)

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

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 >> the requirements are not met. We might want to clarify what

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" > wrote: On 11/24/2015 03:27 PM, Nathan Reller wrote: the cinder admin and the nova admin are ALWAYS the same people There

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

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] [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 > wrote: On Dec 2, 2015, at 12:32 AM, 王华

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

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

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

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

[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

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

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,

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

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

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

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

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

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

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

  1   2   >