[openstack-dev] [cross-project] Meeting SKIPPED, Tue April 5th, 21:00 UTC

Hi all! We will be skipping the cross-project meeting since there are no agenda items to discuss, but someone can add one [1] to call a meeting next time. Thanks! [1] - https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda -- Mike

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

On 04/04/2016 08:45 PM, Jeremy Stanley wrote: On 2016-04-04 20:06:03 -0400 (-0400), Jay Pipes wrote: I'm really not sure why you are being so hostile to my proposal. Essentially, I wanted to involve the upstream Infra team in this so they can advise on the project and ensure that the 3rd party

[openstack-dev] [Openstack-operators] - Containers Sessions in Austin Ops@Summit

Hello all, We are going to have two sessions in the ops summit about containers deployment with OpenStack. (Monday, probably going to be 4:40-6:10) In order to make these sessions useful i think the most important topic that i want to tackle is feedback from operators running OpenStack and

Re: [openstack-dev] [mistral] Bi-weekly team meetings

Ok, thanks guys. I’m going to wait for a few more days and then aggregate all info. Renat Akhmerov @Nokia > On 05 Apr 2016, at 09:57, Hardik Parekh wrote: > > HI, > > I am ok with following timimings. > Tue, Web, Thu 5.00 UTC at [#openstack-meeting,

Re: [openstack-dev] [tricircle] Hello

Hi, Lige, Welcome to join Tricircle. You can start from https://wiki.openstack.org/wiki/Tricircle, and the todo-list is listed in https://etherpad.openstack.org/p/TricircleToDo, and last week we just discussed the cross OpenStack L2 networking:

[openstack-dev] [Neutron] Newton blueprints call for action

Hi Neutrinos, During today's team meeting [0], we went through the current milestone workload [1]. This is mostly made of Mitaka backlog items, amongst which we discussed two blueprints [2, 3]. These two efforts had their spec approved during the Mitaka timeframe, but code lagged behind, and

[openstack-dev] [tricircle] Hello

Hello Team， I am lige, a openstack coder in China UnionPay and glad to join our team. thx. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [mistral] Bi-weekly team meetings

HI, I am ok with following timimings. Tue, Web, Thu 5.00 UTC at [#openstack-meeting, #openstack-meeting-alt] Mon 16.00 UTC at #openstack-meeting (current time slot) On Tue, Apr 5, 2016 at 8:26 AM, Hardik Parekh wrote: > HI, > > I am ok with following time. > > > On

Re: [openstack-dev] [mistral] Bi-weekly team meetings

HI, I am ok with following time. On Mon, Apr 4, 2016 at 3:45 PM, Lingxian Kong wrote: > seems like only this one suits for me(UTC+12). > > * Tue, Web, Thu 5.00 UTC at [#openstack-meeting, #openstack-meeting-alt] > > On Mon, Apr 4, 2016 at 9:14 PM, Renat Akhmerov

Re: [openstack-dev] [Tricircle] Naming convention

Hi Chaoyi, > In the experience of development, using full name as far as possible to > reduce the PEP8 naming convention prompt ion. But if the naming will make us > hard to write one clause less than 80 characters(ensure one clause in one > line), then sometimes the abbreviation has to be

Re: [openstack-dev] [magnum] Proposing Eli Qiao for Magnum core reviewer team

+1 On Sat, Apr 2, 2016 at 7:24 AM, Kai Qiang Wu wrote: > + 1 for Eli :) > > > Thanks > > Best Wishes, > > > Kai Qiang Wu (吴开强 Kennan） > IBM China System and Technology Lab, Beijing > > E-mail:

Re: [openstack-dev] [Tricircle] Naming convention

Hi, Shinobu, Fully agree with you that this is a dilemma situation: If we use full word, for example "availaibility_zone_aggregate", then the length of one line easily exceed 80 characters, especially if there are several indents, if we don't use short name, it's very difficult to make sure

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Mon, Apr 4, 2016 at 5:32 PM, Sean M. Collins wrote: > Inessa Vasilevskaya wrote: > > different configurations of of_interface and ovsdb_interface options > > (dsvm-fullstack [2] and rally tests are by now all I can think of). > > Wait, we have *two* different configuration

Re: [openstack-dev] [Tricircle] Naming convention

Hi Chaoyi, Thank you for your reply. How about this: # tricircle/api/pod.py 94 aggregate = az_ag.create_ag_az(context, 95 ag_name=ag_name, 96

Re: [openstack-dev] [neutron][api] advanced search criteria

Hi Ihar, On 2016/04/05 7:57, Ihar Hrachyshka wrote: Hi all, in neutron, we have a bunch of configuration options to control advanced filtering features for API, f.e. allow_sorting, allow_pagination, allow_bulk, etc. Those options have default False values. I saw allow_bulk option is set

Re: [openstack-dev] [Tricircle] Naming convention

Hi, Shinobu, Thanks for your suggestion. When using PyCharm as the IDE, one issue is that if we use abbreviation for the word to name the function or variables, there is some PEP8 promotion that you'd better to name it in a whole word, but not abbreviation. Best Regards Chaoyi Huang ( Joe

[openstack-dev] [Infra] Meeting Tuesday April 5th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday April 5th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

On 2016-04-04 20:06:03 -0400 (-0400), Jay Pipes wrote: > I'm really not sure why you are being so hostile to my proposal. > Essentially, I wanted to involve the upstream Infra team in this > so they can advise on the project and ensure that the 3rd party CI > system that gets built matches what is

Re: [openstack-dev] [neutron][api] advanced search criteria

On 4 April 2016 at 17:08, Jay Pipes wrote: > On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: > >> - why do we even need to control those features with configuration >> options? can we deprecate and remove them? >> > > This would be my choice. Configuration options that make

[openstack-dev] [horizon] mitaka mid-cycle report

Hello everybody, I know this is a bit late, but I just now came across a blog that our very own Cindy Lu wrote about the Mitaka Horizon mid-cycle. It looks to me as though this never made it out to the mailing list. So, I just wanted to send it along to the ML. Thanks, Cindy!

Re: [openstack-dev] [neutron][api] advanced search criteria

On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: - why do we even need to control those features with configuration options? can we deprecate and remove them? This would be my choice. Configuration options that make the Neutron API behave differently from one deployment to another should be put

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

On 04/04/2016 06:56 PM, Jeremy Stanley wrote: On 2016-04-04 13:54:34 -0400 (-0400), Jay Pipes wrote: On 03/30/2016 11:00 PM, Robert Collins wrote: On 26 March 2016 at 09:08, Jeremy Stanley wrote: On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote: [...] 3) The upstream

[openstack-dev] [neutron][api] advanced search criteria

Hi all, in neutron, we have a bunch of configuration options to control advanced filtering features for API, f.e. allow_sorting, allow_pagination, allow_bulk, etc. Those options have default False values. In the base API controller class, we have support for both native

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

On 2016-04-04 13:54:34 -0400 (-0400), Jay Pipes wrote: > On 03/30/2016 11:00 PM, Robert Collins wrote: > >On 26 March 2016 at 09:08, Jeremy Stanley wrote: > >>On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote: > >>[...] > >>>3) The upstream Infrastructure team works with

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

May be you just don't have enough pain, Sean :) I'd agree that these should be coalesced, with a deprecation period then... E. On Mon, Apr 4, 2016 at 2:32 PM, Sean M. Collins wrote: > Inessa Vasilevskaya wrote: > > different configurations of of_interface and

[openstack-dev] [NFV][Telco] Telco Working Group meeting for Wednesday April 6th CANCELLED

Hi all, I will be on a flight during the meeting slot for Wednesday April 6th and have been unable to source someone else to run the meeting, as a result it is canceled. I would also like to highlight that at this point I believe all of the active Telco Working Group use cases have been

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On Mon, Apr 4, 2016 at 3:22 PM, Doug Wiegley wrote: > I don’t know, -1 really means, “there is something wrong, the submitter > should fix it and clear the slate.” Whereas -2 has two meanings. The first > is “procedural block”, and the second is “f*** you.” > > I

Re: [openstack-dev] [nova][neutron] What to do about booting into port_security_enabled=False networks?

On 4/1/2016 10:50 AM, Matt Riedemann wrote: On 3/31/2016 8:42 AM, Sahid Orentino Ferdjaoui wrote: On Wed, Mar 30, 2016 at 09:46:45PM -0500, Matt Riedemann wrote: On 3/30/2016 5:55 PM, Armando M. wrote: On 29 March 2016 at 18:55, Matt Riedemann

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

I was on vacation last week so I am just seeing this now. I agree that now that we are in Newton we should just remove the non-pluggable code and move forward with the migration. John __ OpenStack Development Mailing List

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

Inessa Vasilevskaya wrote: > different configurations of of_interface and ovsdb_interface options > (dsvm-fullstack [2] and rally tests are by now all I can think of). Wait, we have *two* different configuration options??? WHY WHY WHY -- Sean M. Collins

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

> On Apr 4, 2016, at 10:37 AM, Armando M. wrote: > > > > On 4 April 2016 at 09:22, Ihar Hrachyshka > wrote: > Armando M. > wrote: > > > > On 4 April 2016 at 09:01, Ihar

Re: [openstack-dev] [all] fyi, continued tenant -> project changes in devstack

On 04/04/2016 02:52 PM, Sean Dague wrote: The following patches are making changes to shift from tenant -> project for all the references in devstack (it's not quite done yet, but this was done as a lot of small patches to make potential reverts easy) -

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

Thanks a lot for the opportunity Steve, the kolla core team, and the kolla community! :) Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 04/04/2016 11:41 AM, Armando M. wrote: On 4 April 2016 at 09:36, Ihar Hrachyshka > wrote: Graham > wrote: On 04/04/2016 17:11, Ihar Hrachyshka wrote: Hi all,

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

One of these patchsets was mine, so I feel qualified to send a response :) On 04/04/2016 12:06 PM, Armando M. wrote: On 4 April 2016 at 09:51, Ihar Hrachyshka > wrote: Doug Wiegley

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

The vote is unanimous in favor of Vikram joining the core reviewer team. I have made the appropriate permission changes in gerrit. Welcome to the core reviewer team Vikram! Regards -steve From: Steven Dake > Reply-To: "OpenStack Development Mailing

Re: [openstack-dev] [Neutron][networking-ovn] Changing OVN plugin release model for Newton

On Mon, Apr 4, 2016 at 12:22 PM, Kyle Mestery wrote: > On Mon, Apr 4, 2016 at 8:15 AM, Russell Bryant wrote: > > Hello, everyone. > > > > While bootstrapping networking-ovn, the release model has been > > "release:independent" [1], though we haven't

Re: [openstack-dev] [horizon][all] How to properly depend on Horizon

> On Apr 4, 2016, at 3:32 PM, Rob Cresswell > wrote: > > When you refer to publishing horizon on PyPI, did you mean the entire service > (horizon + openstack_dashboard), or just the horizon package? > > My advice would be to add the horizon tarball to

[openstack-dev] [all] fyi, continued tenant -> project changes in devstack

The following patches are making changes to shift from tenant -> project for all the references in devstack (it's not quite done yet, but this was done as a lot of small patches to make potential reverts easy) -

Re: [openstack-dev] [horizon][all] How to properly depend on Horizon

When you refer to publishing horizon on PyPI, did you mean the entire service (horizon + openstack_dashboard), or just the horizon package? My advice would be to add the horizon tarball to requirements.txt rather than test-requirements, and just use stable-* tarball when creating stable plugin

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On Mon, Apr 4, 2016 at 1:41 PM, Andreas Jaeger wrote: > On 04/04/2016 12:12 PM, Thierry Carrez wrote: > > Doug Hellmann wrote: > >>> [...] > >>> We would love to add all sufficiently mature projects to the > >>> installation > >>> guide because it increases visibility and adoption

Re: [openstack-dev] [fuel] Unrelated changes in patches

On Mon, Apr 04, 2016 at 04:05:28PM +0300, Matthew Mosesohn wrote: > I've seen several cases where core reviewers bully contributors into > refactoring a particular piece of logic because it contains common > lines relating to some non-ideal code, even if the change doesn't > relate to this logic.

Re: [openstack-dev] [Cinder] About snapshot Rollback?

Hi Chen, Not sure if I got you right but I brought this topic in #openstack-cinder some days ago. The idea is to be able to rollback a snapshot in Cinder. Today what is possible to do is to create a volume from a snapshot. From the user point of view, this is not ideal, as there are several

Re: [openstack-dev] [docs] Our Install Guides Only Cover Defcore - What about big tent?

On 04/04/2016 12:12 PM, Thierry Carrez wrote: > Doug Hellmann wrote: >>> [...] >>> We would love to add all sufficiently mature projects to the >>> installation >>> guide because it increases visibility and adoption by operators, but we >>> lack resources to develop a source installation mechanism

[openstack-dev] [ironic] weekly subteam status report

Hi, We are merry to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 28.03.2016): - Ironic: 196 bugs (+17) + 163 wishlist items (-1). 28 new (+3), 135 in progress

Re: [openstack-dev] [nova] [infra] The same SRIOV / NFV CI failures missed a regression, why?

On 03/30/2016 11:00 PM, Robert Collins wrote: On 26 March 2016 at 09:08, Jeremy Stanley wrote: On 2016-03-25 15:20:00 -0400 (-0400), Jay Pipes wrote: [...] 3) The upstream Infrastructure team works with the hired system administrators to create a single CI system that can

Re: [openstack-dev] [puppet][ec2api] - Official EC2 puppet module repo

On Mon, Apr 4, 2016 at 9:12 AM, Denis Egorenko wrote: > Hi Marcos, > > Are you still working on your initial commit to puppet-ec2api [1] ? > > [1] https://review.openstack.org/#/c/276103/ > It might be a good idea to redo this review with a newer version of the

[openstack-dev] [openstack-ansible][security] Update: Host security hardening

Howdy folks, I wanted to take a few moments to update everyone on the host security hardening work in the openstack-ansible-security[1] role for OpenStack-Ansible. Current status -- The role has run in every Mitaka gate job for OpenStack-Ansible since January 2016 and seems to be

Re: [openstack-dev] [nova] New resource tracker

On 04/04/2016 01:21 PM, Rayson Ho wrote: I found that even in the latest git tree, the resource_tracker is still marked as "deprecated and will be removed in the 14.0.0" in releasenova/conf/compute.py . With the Mitaka release coming up this week, is it still true that the code will be removed?

Re: [openstack-dev] [kolla][vote] Nominating Vikram Hosakot for Core Reviewer

+1 Nice work Vikram. On Thu, Mar 31, 2016 at 4:04 PM, Jeff Peeler wrote: > +1 > > On Tue, Mar 29, 2016 at 12:07 PM, Steven Dake (stdake) > wrote: > > Hey folks, > > > > Consider this proposal a +1 in favor of Vikram joining the core reviewer > > team. His

Re: [openstack-dev] [cinder][nova] Cinder-Nova API meeting

Hi All, As we have much to do, our next meeting about improving the Cinder-Nova API interaction will take place __April 6th, 2100UTC__ on the #openstack-meeting-cp channel. You can follow up the recent activities on this etherpad: https://etherpad.openstack.org/p/cinder-nova-api-changes

[openstack-dev] [Announce]Bandit 1.0 stable released

Bandit release 1.0 stable - This milestone release includes a number of major new features, as follow: - Test IDs: bandit tests are now given unique IDs. These IDs can be used in all situations where a test name would have been used previously (include, exclude, etc).

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Mon, 2016-04-04 at 16:16 +, Fox, Kevin M wrote: > config management systems are another piece to the puzzle. If your > using them to mange your containers, you still may end up needing two > different, incompatible versions of the recipes to run on the same > host during upgrades. Its

[openstack-dev] [nova] New resource tracker

I found that even in the latest git tree, the resource_tracker is still marked as "deprecated and will be removed in the 14.0.0" in releasenova/conf/compute.py . With the Mitaka release coming up this week, is it still true that the code will be removed? I googled and found this status update

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 4 April 2016 at 09:51, Ihar Hrachyshka wrote: > Doug Wiegley wrote: > > On Apr 4, 2016, at 10:22 AM, Ihar Hrachyshka wrote: >>> >>> Armando M. wrote: >>> >>> On 4 April 2016 at 09:01, Ihar Hrachyshka

Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath Munirajulu as Octavia Core

+1 From: Brandon Logan Sent: Thursday, March 31, 2016 8:04 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [lbaas] [octavia] Proposing Bharath Munirajulu as Octavia Core +1 On Wed, 2016-03-30 at 13:56

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Doug Wiegley wrote: On Apr 4, 2016, at 10:22 AM, Ihar Hrachyshka wrote: Armando M. wrote: On 4 April 2016 at 09:01, Ihar Hrachyshka wrote: Hi all, I noticed that often times we go and -2 all the

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 4 April 2016 at 09:36, Ihar Hrachyshka wrote: > Graham wrote: > > On 04/04/2016 17:11, Ihar Hrachyshka wrote: >> >>> Hi all, >>> >>> I noticed that often times we go and -2 all the patches in the review >>> queue >>> on every neutron specific gate

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 4 April 2016 at 09:22, Ihar Hrachyshka wrote: > Armando M. wrote: > > >> >> On 4 April 2016 at 09:01, Ihar Hrachyshka wrote: >> Hi all, >> >> I noticed that often times we go and -2 all the patches in the review >> queue on every

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

> On Apr 4, 2016, at 10:22 AM, Ihar Hrachyshka wrote: > > Armando M. wrote: > >> >> >> On 4 April 2016 at 09:01, Ihar Hrachyshka wrote: >> Hi all, >> >> I noticed that often times we go and -2 all the patches in the review queue

Re: [openstack-dev] [monasca][release] missing build artifacts

Please see below: On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann wrote: > Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +: >> Hi Doug, You had mentioned issues with three repos: >> >> 1. monasca-ceilometer >> 2. monasca-log-api >> 3. monasca-thresh

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Graham wrote: On 04/04/2016 17:11, Ihar Hrachyshka wrote: Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done to make sure that nothing known to be broken land in

[openstack-dev] [mistral] Team meeting minutes - 04/04/2016

Thanks for joining our meeting today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-04-04-16.01.html Meeting log:

[openstack-dev] [Fuel] Broken plugins.

Hi guys, if you develop or testing Fuel plugins with current Fuel master ISOs - be aware that with last changes into Fuel tasks serialize system plugins are currently broken. There is a patch [0] which partially fixes this from nailgun side and I am working on library part of it. I believe that

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

Yeah, they were really slammed for 1.0 and were rejecting a lot of good ideas. 1.2 is significantly better since they had time to start to pull in some of those ideas. While its still marked beta, their Deployment api (http://kubernetes.io/docs/user-guide/deployments/) seems to be a very good

[openstack-dev] [Fuel] Broken plugins.

Hi guys, if you develop or testing Fuel plugins with current Fuel master ISOs - be aware that with last changes into Fuel tasks serialize system plugins are currently broken. There is a patch [0] which partially fixes this from nailgun side and I am working on library part of it. I believe that

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

Armando M. wrote: On 4 April 2016 at 09:01, Ihar Hrachyshka wrote: Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done to make sure that

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 04/04/2016 17:11, Ihar Hrachyshka wrote: > Hi all, > > I noticed that often times we go and -2 all the patches in the review queue > on every neutron specific gate breakage spotted. This is allegedly done to > make sure that nothing known to be broken land in merge gate until we fix > the

Re: [openstack-dev] [Neutron][networking-ovn] Changing OVN plugin release model for Newton

On Mon, Apr 4, 2016 at 8:15 AM, Russell Bryant wrote: > Hello, everyone. > > While bootstrapping networking-ovn, the release model has been > "release:independent" [1], though we haven't actually made any releases. > This follows the state of OVN itself, which is still fast

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

config management systems are another piece to the puzzle. If your using them to mange your containers, you still may end up needing two different, incompatible versions of the recipes to run on the same host during upgrades. Its doable, but care has to be done. Thanks, Kevin

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

I look forward to the first (as far as I know) tempest plugin for a service in its own repo! :) On Mon, Apr 4, 2016 at 4:49 PM Hayes, Graham wrote: > On 04/04/2016 16:36, Jordan Pittier wrote: > > > > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham >

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 4 April 2016 at 09:01, Ihar Hrachyshka wrote: > Hi all, > > I noticed that often times we go and -2 all the patches in the review > queue on every neutron specific gate breakage spotted. This is allegedly > done to make sure that nothing known to be broken land in merge

Re: [openstack-dev] [neutron] -2'ing all patches on every gate breakage

On 04/04/2016 12:01 PM, Ihar Hrachyshka wrote: > Hi all, > > I noticed that often times we go and -2 all the patches in the review > queue on every neutron specific gate breakage spotted. This is allegedly > done to make sure that nothing known to be broken land in merge gate > until we fix the

Re: [openstack-dev] [Neutron] Adding amuller to the neutron-drivers team

On Fri, Apr 1, 2016 at 7:58 PM, Edgar Magana wrote: > Congratulations Assaf! > > From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Thursday, March 31, 2016 at

[openstack-dev] [neutron] -2'ing all patches on every gate breakage

Hi all, I noticed that often times we go and -2 all the patches in the review queue on every neutron specific gate breakage spotted. This is allegedly done to make sure that nothing known to be broken land in merge gate until we fix the breakage on our side. While I share the goal of not

Re: [openstack-dev] [murano][release] missing build artifacts

> On Apr 3, 2016, at 3:07 PM, Serg Melikyan wrote: > > Hi Doug, > > I +1 your commit with removing build artifacts for > openstack/murano-apps repo, we indeed don't have artifacts for > murano-apps. > >> It would be good to understand what your intent is for builds.

Re: [openstack-dev] [nova] the bugs team needs (more) members

> From: Adam Lawson > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 04/01/2016 09:58 PM > Subject: Re: [openstack-dev] [nova] the bugs team needs (more) members > > Markus, > > If you van connect me with

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On 4/4/16, 5:53 AM, "Dan Prince" wrote: >On Mon, 2016-04-04 at 02:31 +, Steven Dake (stdake) wrote: >> >> On 4/3/16, 6:38 PM, "Dan Prince" wrote: >> >> > >> > >> > >> > >> > On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: >> > > >> > >

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

On 04/04/2016 16:36, Jordan Pittier wrote: > > On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham > wrote: > > As we have started to move to a tempest plugin for our functional test > suite, we have 2 choices about where it lives. > > 1 -

Re: [openstack-dev] [Ceilometer] Doubt about data recollection

Hello, In the end the RabbitMQ approach would not suffice our requirements as in our installation we have RabbitMQ in the controller. I'm trying to do it with the pipeline approach but trying to maintain the API working. I did the following with cpu_util: - name: cpu_sink

Re: [openstack-dev] [Designate] Tempest Tests - in-repo or separate

On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham wrote: > As we have started to move to a tempest plugin for our functional test > suite, we have 2 choices about where it lives. > > 1 - In repo (as we have [0] currently) > 2 - In a repo of its own (something like

[openstack-dev] [Fuel] Mitaka SCF is coming. Here is bugs status for python and library

Guys, we have a soft code freeze it two days. Here is our status for bugs with medium, low and wishlist priorities. 29 bugs are already moved

Re: [openstack-dev] [fuel] Unrelated changes in patches

Dmitry Guryanov wrote: > It's often not so easy to decide, if you should include some unrelated > changes to your patch, like fixing spaces, renaming variables or > something else, which don't change logic. I'd say it depends. If, for example, variable name is used inside one function - it's ok

[openstack-dev] [cross-project] New Quotas WG meeting time

Hi all, We recently changed the meeting time to accommodate more expected regular visitors to the meeting. Please find the updated info at http://eavesdrop.openstack.org/#Cross-project_Quotas_and_Nested_Quotas_Working_Group_Virtual_Standup Cheers -- Thanks, Nikhil

[openstack-dev] [Nova] live migration meeting Tuesday

The live migration meeting is at the usual time on Tuesday, please feel free to add items to the agenda. https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Regards, Paul Paul Murray Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527

Re: [openstack-dev] [puppet][ec2api] - Official EC2 puppet module repo

Hi Marcos, Are you still working on your initial commit to puppet-ec2api [1] ? [1] https://review.openstack.org/#/c/276103/ 2016-01-29 22:02 GMT+03:00 Emilien Macchi : > > > On 01/29/2016 10:35 AM, Marcos Fermin Lobo wrote: > > Hi, > > > > Since I finished to "apply" for

[openstack-dev] [Designate] Tempest Tests - in-repo or separate

As we have started to move to a tempest plugin for our functional test suite, we have 2 choices about where it lives. 1 - In repo (as we have [0] currently) 2 - In a repo of its own (something like openstack/designate-tempest) There are several advantages to a separate repo: * It will force us

Re: [openstack-dev] [Heat] Meeting time

On Wed, Mar 30, 2016 at 10:26 AM, Thomas Herve wrote: > On Wed, Mar 30, 2016 at 10:13 AM, Thomas Herve wrote: >> Hi all, >> >> I'd like to be able to attend at least one of the IRC meeting, and it >> doesn't really work right now. So if you'd like to come to

Re: [openstack-dev] [magnum] Split k8s-client in separate python package

Thanks Dims. -Original Message- From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: April-02-16 8:10 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Split k8s-client in separate python package Hongbin, Here's what i came up

[openstack-dev] [fuel] API changes for Nailgun openstack config

Hi all, Please be informed that in accordance to bug [1] openstack config API will support bulk operations for 9.0 release. 'node_id' integer parameter is replaced by 'node_ids' list in all related handlers. * URL query parameter in GET /openstack-config/ * POST /openstack-config/ * PUT

Re: [openstack-dev] [fuel] Unrelated changes in patches

On 04/04/2016 07:05 AM, Matthew Mosesohn wrote: > Hi Dmitry, > > I've seen several cases where core reviewers bully contributors into > refactoring a particular piece of logic because it contains common > lines relating to some non-ideal code, even if the change doesn't > relate to this logic. >

Re: [openstack-dev] [sahara][release] missing build artifacts

On 04/01/2016 04:48 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2016-04-01 16:27:42 -0400: Sahara team, We noticed in our audit of the links on http://releases.openstack.org/mitaka/index.html that the links to the build artifacts for sahara-extras point to missing files.

[openstack-dev] [Neutron][networking-ovn] Changing OVN plugin release model for Newton

Hello, everyone. While bootstrapping networking-ovn, the release model has been "release:independent" [1], though we haven't actually made any releases. This follows the state of OVN itself, which is still fast moving and developed in OVS master. On the OVN side, we're now targeting a first

Re: [openstack-dev] [fuel] Unrelated changes in patches

Hi Dmitry, I've seen several cases where core reviewers bully contributors into refactoring a particular piece of logic because it contains common lines relating to some non-ideal code, even if the change doesn't relate to this logic. In general, I'm ok with formatting issues, but changing how a

Re: [openstack-dev] [TripleO][Heat][Kolla][Magnum] The zen of Heat, containers, and the future of TripleO

On Mon, 2016-04-04 at 02:31 +, Steven Dake (stdake) wrote: > > On 4/3/16, 6:38 PM, "Dan Prince" wrote: > > > > > > > > > > > On Mon, 2016-03-21 at 16:14 -0400, Zane Bitter wrote: > > > > > > As of the Liberty release, Magnum now supports provisioning Mesos > > >

[openstack-dev] [fuel] Unrelated changes in patches

Hello, colleagues! It's often not so easy to decide, if you should include some unrelated changes to your patch, like fixing spaces, renaming variables or something else, which don't change logic. On the one hand you see something's wrong with the code and you'd like to fix it, on the other hand

[openstack-dev] [puppet] weekly meeting #77

Hi, We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting4. https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack As usual, free free to bring topics in this etherpad: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160405 We'll also have open discussion

Re: [openstack-dev] [Fuel] branching Mitaka April 6, 2016

What about plugins? For instance: fuel-plugin-detach-keystone -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Mon, Apr 4, 2016 at 1:44 PM, Igor Belikov wrote: > Hi, > > Fuel SCF will be taking place on April 6th, this means that we’re going to >

Re: [openstack-dev] [Fuel] branching Mitaka April 6, 2016

Hi, Igor thank you for update. Folks, I also kindly ask to review the list of patch-sets regarding SCF [1] We've already built custom iso (with [1]) which passed BVT tests [1]. https://review.openstack.org/#/q/topic:9.0-scf,n,z 2016-04-04 14:44 GMT+03:00 Igor Belikov :

[openstack-dev] [Fuel] branching Mitaka April 6, 2016

Hi, Fuel SCF will be taking place on April 6th, this means that we’re going to create stable/mitaka branches for a number of Fuel repos. PLEASE, take a look at the following list and respond if you think your project should be included or excluded from the list: * fuel-agent * fuel-astute *

  1   2   >