[openstack-dev] [designate] Non Candidacy for PTL - Pike

Happy new year! As you may have guessed from the subject, I have decided that the time has come to step aside as PTL for the upcoming cycle. It is unfortunate, but my work has pivoted in a different direction over the last year (containers all the way down man - but hey, I got part of my wish to

Re: [openstack-dev] [tc][goals] Microversions in OpenStack projects

On Jan 9, 2017, at 3:43 PM, LAM, TIN wrote: > As noted in [1], "Add microversion to REST APIs" is one of the cross-project > community goals. Given the scope and the fact there is still discussion on > what "microversion" means to each project and the exact technical >

Re: [openstack-dev] [Ceilometer] Scale deployment

On 09/01/17 07:21 PM, Srikanth Vavilapalli wrote: > Thanks Gordon for your inputs, Quick follow-up question: I see few new > alternatives existing in place of ceilometer mongo storage: Gnocchi and > Panko. Are these recommended data storage options from now on for Ceilometer? > Also, I

Re: [openstack-dev] [Ceilometer] Scale deployment

Thanks Gordon for your inputs, Quick follow-up question: I see few new alternatives existing in place of ceilometer mongo storage: Gnocchi and Panko. Are these recommended data storage options from now on for Ceilometer? Also, I suppose Gnocchi and Panko needs to be deployed on a separate node

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday Cancelled

Due to a scheduling conflict I need to cancel the next Nova Bugs Team Meeting. The next meeting will be Tuesday, January 23, 2017 at 1800UTC in #openstack-meeting-4. I've updated the meeting agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam -- Augustina Ragwitz Señora Software

[openstack-dev] [py3][devstack] being explicit about enabling python 3 for services

At the BCN summit, one of the suggestions for enabling Python 3 in devstack was to provide an explicit whitelist of services that should be run under Python 3. The first phase of that is in [1], which adds both a white and black list. The automatic detection using the python classifiers is

[openstack-dev] [tc][goals] Microversions in OpenStack projects

As noted in [1], "Add microversion to REST APIs" is one of the cross-project community goals. Given the scope and the fact there is still discussion on what "microversion" means to each project and the exact technical implementation, what are your thoughts on the direction the community should

[openstack-dev] [nova] nova-api-metadata managing firewall

Hi nova-devs, I raised a bug about nova-api-metadata messing with iptables on a host https://bugs.launchpad.net/nova/+bug/1648643 It got closed as won’t fix but I think it could do with a little more discussion. Currently nova-api-metadata will

[openstack-dev] Meeting at 20:00UTC this Wednesday, 11th January

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 11th January in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon If we have spare time this meeting I think we should look into getting some patches reviewed

[openstack-dev] [nova] Inconsistency of parameter type in Nova API Reference

Hi Nova developers. In Nova API Reference(*1), the following parameters' values are 'null' in HTTP request body samples. And their parameter types are defined as 'string'. * 'confirmResize' parameter in "Confirm Resized Server (confirmResize Action)" * 'lock' parameter in "Lock Server (lock

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

I'm sad to see you stepping down. Thanks a lot Armando for your amazing service as PTL! -- - Andreas IRC: andreas_s On Mo, 2017-01-09 at 15:11 +0100, Armando M. wrote: > Hi neutrinos, > > > The PTL nomination week is fast approaching [0], and as you might have > guessed by the

Re: [openstack-dev] [heat] glance v2 support?

On 10/01/17 12:35 +0530, Rabi Mishra wrote: On Mon, Jan 9, 2017 at 4:45 PM, Flavio Percoco wrote: On 06/01/17 09:34 +0530, Rabi Mishra wrote: On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi wrote: Greetings Heat folks! My question is simple: When do

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

I prefer 2.b from instinct. Not sure it could be linked to the vitrage_id[1] evolution. If an uuid is created for the alarm, the implementation could be quite straightforward. [1]: https://blueprints.launchpad.net/vitrage/+spec/standard-vitrage-id On Tue, Jan 10, 2017 at 1:55 AM Afek, Ifat

Re: [openstack-dev] [heat] glance v2 support?

On Mon, Jan 9, 2017 at 4:45 PM, Flavio Percoco wrote: > On 06/01/17 09:34 +0530, Rabi Mishra wrote: > >> On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi >> wrote: >> >> Greetings Heat folks! >>> >>> My question is simple: >>> When do you plan to support

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU]Re: [ALU]Re: [ALU][vitrage]how touseplaceholder vertex

I see, you want 2 edges between PC_a and PC_b. In order to model such a use case you need to use the action update_relationship in the processor. You can it in the following way: 1. in the transformer create PC_a -> PC_b in the regular way, by using the action create_entity or

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU]Re: [ALU][vitrage]how touseplaceholder vertex

Great! So let's come back to my original question on redundant link. Before: PC_a is connected to PC_b with Cable After: PC_a is connected to PC_b with Cable *AND* Wi-Fi How to we model this? 1. Create a new edge labeled "Cable and Wi-Fi" ? 2. Assign a structured label like ["Cable",

[openstack-dev] [tc][all] Feedback from driver maintainers about future of driver projects

In preparation for the next TC meeting, a survey was sent out to driver maintainers, here is a summary of the feedback that was gathered. Major observations == * Are drivers an important part of OpenStack? YES! * Discoverability of drivers needs to be fixed immediately. * It

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Thank you Armando for your leadership in transforming the Stadium, for always being being helpful and patient shepherding a gaggle of small projects. You set an example for how to deal with difficult Layer 8 and Layer 9 issues[1]. Thank you for your leadership and your service. --N. [1]

Re: [openstack-dev] [Performance] PTG?

Here[*] you can find an etherpad of Performance team. I think Rally team will re-use it. [*] - https://etherpad.openstack.org/p/ptg-performance-team On Sat, Jan 7, 2017 at 9:35 PM, Joe Talerico wrote: > Hey Andrey - Is there a shared etherpad for the Rally/Performance

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Hi, Flavio! Does it possible to create badges per project release? On Mon, Jan 9, 2017 at 3:23 PM, Flavio Percoco wrote: > Just a heads up! > > There are still unmerged patches on this effort. If you have a couple of > spare > brain cycles, it'd be awesome to get the patches

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

On 03/01/17 12:03 -0800, Joshua Harlow wrote: Hi Oslo folks (and others), Happy new year! After serving for about a year I think it's a good opportunity for myself to let another qualified individual run for Oslo PTL (seems common to only go for two terms and hand-off to another). So I

[openstack-dev] [mistral] Team meeting - 01/09/2017

Hi, We’ll have a team meeting today at 16.00 UTC at #openstack-mistral IRC channel. Agenda: Review action items General syncup after the holidays Current status (progress, issues, roadblocks, further plans) Open discussion Renat Akhmerov @Nokia

Re: [openstack-dev] [oslo] Not running for Oslo PTL for Pike

Piling on the +1's :) Thanks for your work/guidance/leadership. -- Dims On Mon, Jan 9, 2017 at 6:27 AM, Flavio Percoco wrote: > On 03/01/17 12:03 -0800, Joshua Harlow wrote: >> >> Hi Oslo folks (and others), >> >> Happy new year! >> >> After serving for about a year I think

Re: [openstack-dev] [glance][tempest][api] community images, tempest tests, and API stability

On 1/5/17 10:19 AM, Brian Rosmaita wrote: > To anyone interested in this discussion: I put it on the agenda for > today's API-WG meeting (16:00 UTC): > > https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda As you probably noticed in the API-WG newsletter [A], this issue was discussed at last

[openstack-dev] [neutron] PTL nominations deadline and non-candidacy

Hi neutrinos, The PTL nomination week is fast approaching [0], and as you might have guessed by the subject of this email, I am not planning to run for Pike. If I look back at [1], I would like to think that I was able to exercise the influence on the goals I set out with my first self-nomination

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

On 1/9/17, 2:11 PM, "Armando M." wrote: >Hi neutrinos, > >The PTL nomination week is fast approaching [0], and as you might have >guessed by the subject of this email, I am not planning to run for Pike. >If I look back at [1], I would like to think that I was able to exercise

Re: [openstack-dev] [Ceilometer] Scale deployment

On 08/01/17 07:28 PM, Srikanth Vavilapalli wrote: > > - Deploying database cluster on separate nodes with sharding > and replica-sets enabled > we don't recommend you use ceilometer storage since it's deprecated and hasn't been worked on for over a year. > > > My questions are: > >

Re: [openstack-dev] [docs][badges][all] Docs gate broken for projects that include README.rst in docs

On 09/01/17 15:02 +0100, Andreas Jaeger wrote: On 2016-12-12 09:22, Flavio Percoco wrote: On 11/12/16 13:32 +0100, Flavio Percoco wrote: On 09/12/16 17:20 +0100, Flavio Percoco wrote: Greetings, Some docs jobs seem to be broken by the latest (or not?) docutils release. The breakage seems to

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 09/01/17 17:55 +0200, Andrey Kurilin wrote: Hi, Flavio! Does it possible to create badges per project release? mmh, it's currently not possible. Could you elaborate on why you need a specific tag per release? IS it to tag the releases that were done after the inclusion in the big tent?

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Ifat, I think there is a situation that all the alarms are reported by the monitored system. We use vitrage to: 1. Found the relationships of the alarms, and find the root cause. 2. Deduce the alarm before it really occured. This comprise two aspects:

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU]Re: [ALU][vitrage]how touseplaceholder vertex

Hi Yujun, After some more checks, I found out the current code will handle your case as well, because it will go into the 2.c.1. Alexey > -Original Message- > From: Weyl, Alexey (Nokia - IL) [mailto:alexey.w...@nokia.com] > Sent: Monday, January 09, 2017 10:54 AM > To: OpenStack

Re: [openstack-dev] [Openstack-operators] [nova] Automatically disabling compute service on RBD EMFILE failures

On Sat, Jan 07, 2017 at 12:04:25PM -0600, Matt Riedemann wrote: > A few weeks ago someone in the operators channel was talking about issues > with ceph-backed nova-compute and OSErrors for too many open files causing > issues. > > We have a bug reported that's very similar sounding: > >

[openstack-dev] [nova] Next notification meeting

Hi, The next notification subteam meeting will be held on 2017.01.10 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170110T17 __ OpenStack

[openstack-dev] [neutron] Team and drivers meetings

Hi neutrinos, A reminder that from this week on it is business as usual. Therefore the calendar for team and drivers meetings is back up and running. Cheers, Armando __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tripleo] removing glance-registry & api v1

On 05/01/17 19:21 -0500, Emilien Macchi wrote: Just some heads-up for those who were interested by removing Glance Registry from TripleO (yes Flavio, I'm looking at you !). Because TripleO relies on Heat for the pingtest (validation that OpenStack cloud is up and running) and because Heat

Re: [openstack-dev] [heat] glance v2 support?

On 06/01/17 09:34 +0530, Rabi Mishra wrote: On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi wrote: Greetings Heat folks! My question is simple: When do you plan to support Glance v2? https://review.openstack.org/#/c/240450/ The spec looks staled while Glance v1 was

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU][vitrage]how touseplaceholder vertex

What will happen is the following: We have a connection between PC_a and PC_b with label Cable. Now a new event arrives and the transformer builds the following trio: (Vertex_A, Neighbors((Vertex_B, Edge), UPDATE) This transformed data arrives to the processor that goes to the UPDATE action: 1.

Re: [openstack-dev] [docs][badges][all] Docs gate broken for projects that include README.rst in docs

On 2016-12-12 09:22, Flavio Percoco wrote: > On 11/12/16 13:32 +0100, Flavio Percoco wrote: >> On 09/12/16 17:20 +0100, Flavio Percoco wrote: >>> Greetings, >>> >>> Some docs jobs seem to be broken by the latest (or not?) docutils >>> release. The >>> breakage seems to be related to the latest

Re: [openstack-dev] [heat] project specific question for the next user survey

Dear team Thanks for joining the vote. Base on the polling result, we decide to go with the question that: *What's the expected load on your Heat deployment?* - *Few small stacks (<100 resources each) * - *Lots of small stacks (<100 resources each) * - *Few big stacks (>100 resources

Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments

Thanks -Original Message- From: Christian Schwede [mailto:cschw...@redhat.com] Sent: Thursday, January 05, 2017 1:29 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [TripleO] Fixing Swift rings when upscaling/replacing nodes in TripleO deployments On 05.01.2017

Re: [openstack-dev] [tripleo][ui] FYI, the tripleo-ui package is currently broken

On 6 January 2017 at 14:52, Julie Pichon wrote: > Hi folks, > > Just a heads-up that the DLRN "current"/dev package for the Tripleo UI > is broken in Ocata and will cause the UI to only show a blank page, > until we resolve some dependencies issues within the -deps package. >

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

Just a heads up! There are still unmerged patches on this effort. If you have a couple of spare brain cycles, it'd be awesome to get the patches relative to the projects you've +2 votes on in. I'll proceed to abandon remaining patches in 2 weeks from now assuming that projects are not

Re: [openstack-dev] [nova] placement/resource providers update 7

On Fri, 6 Jan 2017, Chris Dent wrote: * CORS support in placement API: https://review.openstack.org/#/c/392891/ This is one we should probably get in in Ocata because it enables the sole piece of configurability that is present in the WSGI middleware stack used for the placement API. Unlike

Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next User Survey?

On Tue, Jan 3, 2017 at 9:08 AM, Emilien Macchi wrote: > (Happy new year folks!) > > Forwarding Heidi's email to TripleO folks, so anyone can contribute to it. > > Feel free to propose questions on: > https://etherpad.openstack.org/p/tripleo-user-survey-2017 > > The question

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

 Thank you for being PTL for as long as you did. If it weren't for your effort with the vendor and advanced services decomposition, Neutron would have died under review load. I hope this means we'll be seeing more code from you! :) On Mon, Jan 9, 2017 at 6:11 AM, Armando M.

Re: [openstack-dev] [neutron] PTL nominations deadline and non-candidacy

2017-01-09 8:11 GMT-06:00 Armando M. : > Hi neutrinos, > > The PTL nomination week is fast approaching [0], and as you might have > guessed by the subject of this email, I am not planning to run for Pike. If > I look back at [1], I would like to think that I was able to exercise

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On Mon, Jan 9, 2017 at 6:37 PM, Flavio Percoco wrote: > On 09/01/17 17:55 +0200, Andrey Kurilin wrote: > >> Hi, Flavio! >> >> Does it possible to create badges per project release? >> > > mmh, it's currently not possible. > > Could you elaborate on why you need a specific tag

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Yujun, I understand the use case now, thanks for the detailed explanation. Supporting this use case will require some development in Vitrage. Let me try to list down the requirements and options that we have. 1. Requirement: Raise ‘suspect’ deduced alarms in Vitrage. Implementation:

Re: [openstack-dev] STIG Tools

-Original Message- From: Joel Parker Reply: OpenStack Development Mailing List (not for usage questions) Date: January 9, 2017 at 10:25:36 To: openstack-dev@lists.openstack.org Subject: 

Re: [openstack-dev] [heat] glance v2 support?

On 01/09/2017 05:15 AM, Flavio Percoco wrote: > On 06/01/17 09:34 +0530, Rabi Mishra wrote: >> On Fri, Jan 6, 2017 at 4:38 AM, Emilien Macchi >> wrote: >> >>> Greetings Heat folks! >>> >>> My question is simple: >>> When do you plan to support Glance v2? >>>

Re: [openstack-dev] [all][py3][swift][devstack] USE_PYTHON3 works! (well somewhat)

On Mon, Jan 2, 2017 at 1:06 PM, Davanum Srinivas wrote: > Folks, > > Other teams: > Please consider adding DSVM jobs with USE_PYTHON3=True for your > projects. This will hopefully help us get to our Pike goal for Python > 3.x [10] > > As a note the variable name for DSVM jobs

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are jazzy to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. attach/detach:

Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next User Survey?

+1 From: Ligong LG1 Duan [mailto:duan...@lenovo.com] Sent: Sunday, January 08, 2017 7:41 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tripleo] Fwd: Do you want to ask a project-specific question on the next

[openstack-dev] STIG Tools

I am new to the STIG hardening process and wanted to see if there was a standard way to diff between releases (RHEL STIG 7 draft 0.2 and 0.3 for example) or between RHEL 5 and 6 or something. Obviously the reason for this is too quickly check / implement the diff instead of going through the whole

Re: [openstack-dev] STIG Tools

On 01/09/2017 11:07 AM, Ian Cordasco wrote: >> I am new to the STIG hardening process and wanted to see if there was a >> standard way to diff between releases (RHEL STIG 7 draft 0.2 and 0.3 for >> example) or between RHEL 5 and 6 or something. Obviously the reason for >> this is too quickly check

[openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

It's just come to my attention that the Newton release notes indicated deprecation of the events support in favor of Panko [1] and that it has already been removed in master [2]. But I don't believe there were any deprecation warnings for this in the Newton code, which is the typical way many

Re: [openstack-dev] [api-wg] restarting service-types-authority / service catalog work

On 14:10 Jan 06, Sean Dague wrote: > Cinder / volume - right now the devstack example of using cinder is to > use volumev2 as the service type (volumev3 is also added), which is kind > of ugly and not a thing that I'd like us to standardize on. How do we > move forward here to not make volumev2 a

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage]how touseplaceholder vertex

That’s not what I mean. When some data is changed in a some vertices, their event is pushed to the event queue, and thus the correct transformer is called. We update the data of the current vertex, and for each neighbor that we created in the transformer, we check the following: if the neighbor

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage]how touseplaceholder vertex

Thanks Alexey. Could you explain a bit more detail based on the example in comments below? On Mon, Jan 9, 2017 at 4:08 PM Weyl, Alexey (Nokia - IL) < alexey.w...@nokia.com> wrote: That’s not what I mean. When some data is changed in a some vertices, their event is pushed to the event queue, and