[openstack-dev] [aodh][vitrage] Aodh generic alarms

Hi Julien, I’m sending this mail regarding the generic alarm that Alexey Weyl from the Vitrage team is trying to implement in Aodh [1][2]. We understood that Aodh aims to be OpenStack alarming service, which is much more than an ‘engine of alarm evaluation’ (as you wrote in your comment in ger

[openstack-dev] [cinder] High load with oflag=direct

Hi, I'm using cinder with lvm (mitaka release). Actually all works well, but I noticed that when I create a new bootable volume from an image, the storage backend has an intensive cpu/disk usage with a load around 12. I think this happens because cinder use dd with oflag=direct during the copy. I u

[openstack-dev] [neutron] PTL candidacy

Hi team, I would like to propose my PTL candidacy for Pike. Some of you already know me. If not, here is my brief OpenStack bio. I joined the community back in Havana, and managed to stick around till now. During the time, I fit several project roles like serving as a Neutron liaison of different

Re: [openstack-dev] [Neutron] PTL Candidacy

I'm on board with getting visibility into the drivers with improvements to driverlog, etc. What I'm uncertain of is providing much in the lines of 'validation'. Core reviewers don't frequently have access to the hardware or software required to validate these drivers so we can't be sure if the feat

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

As I understand it, if someone configures Nova to use 2.40 via settings, then it will use 2.40 for every request. This could likely break Horizon in weird ways, which makes it seem risky to try and support it. What I don’t really understand about this FFE, is why we need to modify the behaviour

[openstack-dev] [nova] Device tag in the API breaks in the old microversion

Unfortunately the device tag support in the API was broken in the old Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks to Kevin Zheng to find out that. Actually there are two bugs, just all of them are about device tag. The first one [0] is a mistake in the initial introduce

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

No, for some reason Nova will now always limit the number of entries it sends in a single response, no matter what microversion you use. If you use microversion of at least 2.40, it will let you request more responses, to get all the entries. I don't know why they did it like that. On Tue, Jan 24,

Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership

+1 for both. regards Shu > -Original Message- > From: Pradeep Singh [mailto:[email protected]] > Sent: Tuesday, January 24, 2017 11:58 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core team

Re: [openstack-dev] Sabari Murugesan stepping down from Glance core

Nice work Sabari, Thank you for your efforts and help you provided. Hope to see you back in the list. All the best, Abhishek -Original Message- From: Brian Rosmaita [mailto:[email protected]] Sent: Tuesday, January 24, 2017 4:32 AM Cc: Sabari Murugesan; OpenStack Development M

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

HI! Thing is, running Galera without enforcing it very bad idea for production use. Permissive mode was added more or less for testing purposes, running real production with it is dangerous, since it's not enforcing the mandatory Galera requirement, one of them is a "All tables must have a primary

[openstack-dev] [nova] Next notification meeting

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

[openstack-dev] [kuryr][ptl] PTL candidacy

Hi Kuryrs! I am putting forward my candidacy[1] for a second term as the PTL. It is great to work with all of you every day to make kuryr deliver on its mission. Over this current cycle, we've managed to rebuild the team after we had some core departures and I think we are in a very good place, w

Re: [openstack-dev] [all] New deadline for PTG Travel Support Program

These submissions will be evaluated next week and grantees will be notified by Friday, January 20th. Were people who were not granted also get notifications? I am not sure if I was not granted or if I simply did not apply as I thought I did. Thanks very much! Eran _

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

Thanks Alex for writing in details. On Tue, Jan 24, 2017 at 6:05 PM, Alex Xu wrote: > Unfortunately the device tag support in the API was broken in the old > Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks > to Kevin Zheng to find out that. > > Actually there are two bug

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

Sorry, forgot to mention tempest patch - https://review.openstack.org/#/c/424572/1 (but broken cases seems clear without that patch also) Regards Ghanshyam Mann +818011120698 On Tue, Jan 24, 2017 at 7:34 PM, Ghanshyam Mann wrote: > Thanks Alex for writing in details. > > > On Tue, Jan 24, 2017

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: Hi Ifat, > We understood that Aodh aims to be OpenStack alarming service, which is much > more than an ‘engine of alarm evaluation’ (as you wrote in your comment in > gerrit). Well, currently it's not really more than that. We've been to the pa

[openstack-dev] [launchpad] [docs] Adding checklist to bug reporting

Hi everyone, The documentation team has been having issues with bugs being filed asking for troubleshooting and support for years. We have been doing our best to redirect and close, but it is becoming increasingly unmanageable. I know other projects struggle with this issue too. We implemented

Re: [openstack-dev] [kolla-ansible] [kolla] Am I doing this wrong?

Ah, I think you may be misreading what Sean is saying there. What he means is kolla-ansible provides the bare minimum config templates to make the service work. To template every possible config option would be too much of a maintenance burden on the project. Of course, users will want to cust

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

Hi Julien, Before I reply to everything you wrote, I would like to ask a question that seems to be the core issue here. On 24/01/2017, 12:58, "Julien Danjou" wrote: On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: > We understood that Aodh aims to be OpenStack alarming service, whic

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

> So the current API behavior is as below: > > 2.32: BDM tag and network device tag added. > 2.33 - 2.36: 'tag' in the BDM disappeared. The network device tag still > works. > 2.37: The network device tag disappeared also. Thanks for the summary. For the visual minded like me, I made some ASCII ar

[openstack-dev] [kolla] Docs status?

Hi Kolla, Does anyone know the current status of docs refactor? I believe there was someone looking into it (apologies can't remember their name). If not, I'd like to propose a vote for some immediate changes that can improve things. Regards, -Paul _

Re: [openstack-dev] [kolla] Docs status?

CCing Ianeta Hutchinson and Joseph Robinson that I know were helping the efforts ☺ On 1/24/17, 12:06 PM, "Paul Bourke" wrote: Hi Kolla, Does anyone know the current status of docs refactor? I believe there was someone looking into it (apologies can't remember their name).

[openstack-dev] Subject: [Keystone][Tempest][QA] Tempest full fails with policy.v3cloudsample.json and gate is using old policy.json

Hi, Firstly, apologies for the cross post from [email protected] but I think this is a more appropriate mailing list and I'd like to add some more information. I have been running tempest full against a Keystone v3 enabled cloud using the stable newton policy.v3cloudsample.json *1 and it is failing

Re: [openstack-dev] Subject: [Keystone][Tempest][QA] Tempest full fails with policy.v3cloudsample.json and gate is using old policy.json

Hi Liam, As you said, this is a known issue of the "policy.v3cloudsample.json" policy file. The cloud_admin rule is supposed to be something like: or I have a project scoped token for the "is_admin" project with the admin role, or I have a domain scoped token for the specified domain with the admi

Re: [openstack-dev] [networking-sfc]

On 20 January 2017 at 00:06, Michael Gale wrote: > Hello, > > Are there updated install docs for sfc? The only install steps for a > testbed I can find are here and they seem outdated: > https://wiki.openstack.org/wiki/Neutron/ServiceInsertionAndChaining There is also a SFC chapter in the netw

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Kirill, "If OS wants support Galera, it needs to comply with the Galera requirements" <<< This is true for master/ocata NOT Newton. Ihar's response is perfectly acceptable thing to do for Newton in the community to highlight the possibility of this situation. Downstream folks can do what they nee

Re: [openstack-dev] [Zun] Propose a change of the Zun core team membership

+1 from me! Kevin has made significant contribution to Zun, he deserves this! Best Regards, Wenzhi Yu(yuywz) > 在 2017年1月24日，下午5:12，Shuu Mutou 写道： > > +1 for both. > > regards > Shu > > >> -Original Message- >> From: Pradeep Singh [mailto:[email protected]] >> Sent: Tuesday, Janu

[openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance core. She has been an active reviewer and contributor to the Glance project during the Newton and Ocata cycles, has contributed to other OpenStack projects, and has represented Glance in some interactions with other project team

Re: [openstack-dev] [puppet] CI status for Ubuntu

On Fri, Jan 20, 2017 at 6:34 PM, Alex Schultz wrote: > Just FYI, > > We switched the Ubuntu scenario jobs to non-voting this week due to > the large amount of breakage caused by the ocata-proposed update to m2 > based packages. The Ubuntu beaker jobs are still voting on the > modules themselves.

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: > Vitrage, and I assume that other projects, needs an “Alarm Manager”. The role > of an Alarm Manager is to store all alarms in the system, keep their history, > notify on changes, etc. Vitrage does not declare itself as an Alarm Manager, > mainl

[openstack-dev] [tripleo] Proposing Honza Pokorny core on tripleo-ui

I have been discussed with TripleO UI core reviewers and it's pretty clear Honza's work has been valuable so we can propose him part of Tripleo UI core team. His quality of code and reviews make him a good candidate and it would also help the other 2 core reviewers to accelerate the review process

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

On Thu, Jan 19, 2017 at 11:53 AM, Christian Berendt wrote: > As discussed in one of the last team meetings I want to propose the > deprecation (this cycle) and removal (next cycle) of the Debian support in > Kolla. > > More than 1 week ago I sent a pre warning mail to the openstack-operators >

Re: [openstack-dev] [tripleo] Proposing Honza Pokorny core on tripleo-ui

On 01/24/2017 06:52 AM, Emilien Macchi wrote: > I have been discussed with TripleO UI core reviewers and it's pretty > clear Honza's work has been valuable so we can propose him part of > Tripleo UI core team. > His quality of code and reviews make him a good candidate and it would > also help the

Re: [openstack-dev] [octavia] Nominating German Eichberger for Octavia core reviewer

Glad to be back! Thanks for the trust, German From: Michael Johnson Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday, January 23, 2017 at 11:41 AM To: "'OpenStack Development Mailing List (not for usage questions)'" Subject: Re: [openstack-dev] [octavia]

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Galera only supported since Ocata? On Tue, Jan 24, 2017 at 4:30 PM, Davanum Srinivas wrote: > Kirill, > > "If OS wants support Galera, it needs to comply with the Galera > requirements" <<< This is true for master/ocata NOT Newton. > > Ihar's response is perfectly acceptable thing to do for Newt

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Newton is already shipped! -- Dims On Tue, Jan 24, 2017 at 9:23 AM, Kirill Proskurin wrote: > Galera only supported since Ocata? > > On Tue, Jan 24, 2017 at 4:30 PM, Davanum Srinivas wrote: >> >> Kirill, >> >> "If OS wants support Galera, it needs to comply with the Galera >> requirements" <<<

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Please see http://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines On Tue, Jan 24, 2017 at 9:34 AM, Davanum Srinivas wrote: > Newton is already shipped! > > -- Dims > > On Tue, Jan 24, 2017 at 9:23 AM, Kirill Proskurin > wrote: >> Galera only supported since Ocata? >

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

Hi, we had a brief conversation in the channel about this. My team at Linaro is planning to start working with Kolla after the PTG to produce fully deployable ARM64 containers. The preference for us is to produce Debian based containers, as well as any others that are required to meet the project

Re: [openstack-dev] [puppet] CI status for Ubuntu

On 01/24/2017 02:43 PM, Corey Bryant wrote: > > On Fri, Jan 20, 2017 at 6:34 PM, Alex Schultz > wrote: > > Just FYI, > > We switched the Ubuntu scenario jobs to non-voting this week due to > the large amount of breakage caused by the ocata-proposed update

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

We do not backport db changes, but if the existing migration does not work in certain circumstances, should not we fix it to make it work if it is possible? This will allow to deploy new deployments with Newton code on Galera. On Tue, Jan 24, 2017 at 6:45 PM Davanum Srinivas wrote: > Please see

Re: [openstack-dev] [horizon] feature freeze exception request -- nova simple tenant usages api pagination

It was done like that to circumvent the existing possibility DoS-like usage requests when there are thousands of instances. Some of the history behind that decision can be found in the spec discussions [1]. And an easier to read spec can be found here [2]. [1] https://review.openstack.org/#/c/38

[openstack-dev] [neutron] PTL Candidacy

Hi neutrinos, No, it's not what you might be thinking...I am just delighted to see two excellent candidates willing to take the reins of the project going forward [1,2]. I couldn't hope for more enthusiasm; best of luck to both candidates and anyone else who is going to step up! This is exciting!

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Ann, Don't you still need alembic>=0.8.10 to be present? -- Dims On Tue, Jan 24, 2017 at 10:05 AM, Anna Taraday wrote: > We do not backport db changes, but if the existing migration does not work > in certain circumstances, should not we fix it to make it work if it is > possible? > This will a

Re: [openstack-dev] [puppet] CI status for Ubuntu

On Tue, Jan 24 2017, Thomas Goirand wrote: > FYI, this was a very unfortunate upload of the latest webob version in > Sid, which was reverted. IMO though, OpenStack should prepare itself to > support the latest version to avoid failures once we decide that webob > 1.7.x should be uploaded again. A

[openstack-dev] [all] Get Active in Upstream Training

Hi All, As most of you know we have a continuous effort to help newcomers to join our community by organizing and holding Upstream contribution trainings before every OpenStack Summit. The training [1][2] is a 1.5 - 2 days long hands-on course focusing on the first steps of becoming an active

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

On 1/24/2017 3:34 AM, Ghanshyam Mann wrote: But from looking at api-ref and db, i am little bit confused. API-ref says device tag as "An arbitrary tag." [6] and DB also have it as Column(String(255)) [7] But our tag validation we mistakenly removed is more strict actually as per [8] which seems

Re: [openstack-dev] [vote][kolla] deprecation for Debian distro support

Gema, Yes team meeting sounds good. I am changing my vote from choice 2 to abstain until this is sorted out. Regards -steve -Original Message- From: Gema Gomez Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, January 24, 2017 at 7:42 AM To: "op

Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

-Original Message- From: Brian Rosmaita Reply: OpenStack Development Mailing List (not for usage questions) Date: January 24, 2017 at 07:37:24 To: OpenStack Development Mailing List Subject:  [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core > I'd like to propose Dha

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Nope, this won't be necessary. 0.8.10 - allows us to create pk on alembic_version table automatically, but only for new deployments. I propose manually add pk on this table if it is not existing. On Tue, Jan 24, 2017 at 7:25 PM Davanum Srinivas wrote: > Ann, > > Don't you still need alembic>=0

[openstack-dev] [telemetry] remaining ocata items

hi, so i just wanted to create a list of items i'm tracking for ocata that i'd like to see in: ceilometer - polling definition file support [1] - configurable control exchanges [2] - deprecate collector [3] - equivalent publisher/dispatcher support [4] gnocchi - creator(user+project) unique ids

Re: [openstack-dev] [All projects that use Alembic] Absence of pk on alembic_version table

Cool. Then i'd support a backport when the review against master merges. Thanks Ann and Kirill. -- Dims On Tue, Jan 24, 2017 at 10:33 AM, Anna Taraday wrote: > Nope, this won't be necessary. > > 0.8.10 - allows us to create pk on alembic_version table automatically, but > only for new deployment

Re: [openstack-dev] [telemetry] remaining ocata items

On Tue, Jan 24 2017, gordon chung wrote: > ceilometer > - polling definition file support [1] > - configurable control exchanges [2] > - deprecate collector [3] I've -2ed this for now because it is too late to have the TripleO changes pushed. That's a shame, but we'll do it first week in Pike. >

Re: [openstack-dev] [puppet] CI status for Ubuntu

On 01/24/2017 04:15 PM, Julien Danjou wrote: > On Tue, Jan 24 2017, Thomas Goirand wrote: > >> FYI, this was a very unfortunate upload of the latest webob version in >> Sid, which was reverted. IMO though, OpenStack should prepare itself to >> support the latest version to avoid failures once we d

Re: [openstack-dev] [TC][Glance][Nova][TripleO][Heat][Mistral][Ironic][Murano] Glare

Hey, Flavio :) Thanks for your questions! As you said currently only Nokia's adopting Glare for its own platform, but if we talk about OpenStack, that I believe Mistral will start to use it soon. In my opinion Glare's adoption is low due to the fact that the project is not included under Big Tent.

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

On 1/24/2017 2:05 AM, Alex Xu wrote: Unfortunately the device tag support in the API was broken in the old Microversion https://bugs.launchpad.net/nova/+bug/1658571, which thanks to Kevin Zheng to find out that. Actually there are two bugs, just all of them are about device tag. The first one [0

Re: [openstack-dev] [nova] Device tag in the API breaks in the old microversion

On 1/24/2017 9:18 AM, Matt Riedemann wrote: First, thanks to Kevin and Alex for finding this issue and explaining it in detail so we can understand the scope. This is a nasty unfortunate issue which I really wish we could just fix without a microversion bump but we have microversions for a reas

[openstack-dev] [puppet] Thank you.

I attempted to send this out last week but think I messed it up by sending from my work email address which isn't the one I am signed up to the lists with. Seeing Alex's note in IRC this morning reminded me that I had probably screwed it up... I just wanted to let everyone know how much I trul

Re: [openstack-dev] [telemetry] remaining ocata items

On Tue, Jan 24, 2017 at 10:53 AM, Julien Danjou wrote: > On Tue, Jan 24 2017, gordon chung wrote: > >> ceilometer >> - polling definition file support [1] >> - configurable control exchanges [2] >> - deprecate collector [3] > > I've -2ed this for now because it is too late to have the TripleO > ch

Re: [openstack-dev] [tc][swg] Sessions for Atlanta PTG - writing a TC Vision/Other options

On Mon, Jan 23, 2017 at 2:00 PM, Colette Alexander wrote: > Hello Stackers, > > As we move into the last four weeks of work before the PTG in Atlanta, I > wanted to check in to talk about what the Stewardship Working Group has > planned and what we're looking to accomplish during our one day (Mond

Re: [openstack-dev] [tripleo] Update TripleO core members

+1 On 01/23/2017 01:03 PM, Emilien Macchi wrote: Greeting folks, I would like to propose some changes in our core members: - Remove Jay Dobies who has not been active in TripleO for a while (thanks Jay for your hard work!). - Add Flavio Percoco core on tripleo-common and tripleo-heat-templates

Re: [openstack-dev] [puppet] Thank you.

On Fri, Jan 20, 2017 at 2:29 PM, Cody Herriges wrote: > I attempted to send this out last week but think I messed it up by sending > from my work email address which isn't the one I am signed up to the lists > with. Seeing Alex's note in IRC this morning reminded me that I had > probably screwed

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

Hello everyone, We've reached our agreement! http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_28264d5a40d0088c New deliverable process will be lightweight - just normal +2+2+PTL vote is needed to add new deliverable. I'm going to create new deliverables.yaml file in Kolla repository which will a

[openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both on the current CI solution and in getting tripleo-quickstart jobs for it); So I would like to propose him as part of the TripleO CI core team. I think he'll make a great addition to the team and will help move CI issues forward q

Re: [openstack-dev] [all] New deadline for PTG Travel Support Program

Eran Rom wrote: >> These submissions will be evaluated next week and grantees will be >> notified by Friday, January 20th. > Were people who were not granted also get notifications? > I am not sure if I was not granted or if I simply did not apply as I > thought I did. Yes everyone gets notificati

[openstack-dev] [ironic] [ptl] Ironic PTL Candidacy for Pike

Hi all! I am announcing my candidacy for PTL for the Ironic team for the Pike release cycle. In case you don't know me, I'm dtantsur on IRC. I started working on Ironic around late spring or summer 2014, and I'm probably best known as a founder of ironic-inspector sub-project. I work for Red Hat.

[openstack-dev] [keystone] PTL candidacy

Hello everyone! I have been involved in OpenStack since late 2013 and now it is time to put my name forward as a candidate for keystone PTL during the Pike development cycle. See my openstack/election change in [1]. As your PTL, I would like to see our team's focuses classified into three catego

Re: [openstack-dev] [all] [tc] [api] refreshing and revalidating api compatibility guidelines

On Mon, 23 Jan 2017, Sean Dague wrote: We all inherited a bunch of odd and poorly defined behaviors in the system we're using. They were made because at the time they seemed like reasonable tradeoffs, and a couple of years later we learned more, or needed to address a different use case that peo

Re: [openstack-dev] [tripleo] Update TripleO core members

On Mon, Jan 23, 2017 at 3:33 PM, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on tripleo-common and tripl

Re: [openstack-dev] [puppet] CI status for Ubuntu

On Tue, Jan 24 2017, Thomas Goirand wrote: > Check this bug entry: > https://bugs.debian.org/851032 > > This may have been fixed since Newton though. The FTBFS was reported > against packages aimed for Debian Stretch. This is likely a race condition, it has nothing to do with webob IMHO. We fixed

Re: [openstack-dev] [telemetry] remaining ocata items

On 24/01/17 11:53 AM, Emilien Macchi wrote: > Yes, even outside TripleO, it's already hard to follow all changes > made in projects, so please do not deprecate things at the end of a > cycle. > Let's take some time, we do it in Pike, making good communication, so > folks like TripleO etc can have

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think he'll m

Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

Dharini has tackled sticky bugs and complex feature work with good judgement, patience, and agility. Her work is highly valuable to the project and community. I'm happy to offer a vote in favor. On Tue, Jan 24, 2017 at 5:36 AM, Brian Rosmaita wrote: > I'd like to propose Dharini Chandrasekar (dh

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On 01/24/2017 12:03 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think he'll make a gr

Re: [openstack-dev] [Neutron] PTL Candidacy

On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > I'm on board with getting visibility into the drivers with improvements to > driverlog, etc. What I'm uncertain of is providing much in the lines of > 'validation'. Core reviewers don't frequently have access to the hardware or > software req

[openstack-dev] [murano] [ptl] PTL Candidacy for Pike

Hi, My name is Felipe Monteiro. I have decided to run for Murano PTL for the Pike release cycle. I would like to continue to grow Murano in order to make the project more stable, mature and performant, while exploring avenues to evolve the project. I've been working on the project for the past co

Re: [openstack-dev] [telemetry] remaining ocata items

On Tue, Jan 24, 2017 at 12:52 PM, gordon chung wrote: > > > On 24/01/17 11:53 AM, Emilien Macchi wrote: >> Yes, even outside TripleO, it's already hard to follow all changes >> made in projects, so please do not deprecate things at the end of a >> cycle. >> Let's take some time, we do it in Pike,

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 07:03:56PM +0200, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 1:33 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think he'll m

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On 24/01/17 03:01 AM, Afek, Ifat (Nokia - IL) wrote: > We understood that Aodh aims to be OpenStack alarming service, which is much > more than an ‘engine of alarm evaluation’ (as you wrote in your comment in > gerrit). If I may describe another use case for generic alarms - of OPNFV > Doctor:

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

+1 On Tue, Jan 24, 2017 at 2:10 PM, Brent Eagles wrote: > > > On Tue, Jan 24, 2017 at 1:33 PM, Juan Antonio Osorio > wrote: > >> Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both >> on the current CI solution and in getting tripleo-quickstart jobs for >> it); So I would like

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

+1 On 01/24/2017 11:03 AM, Juan Antonio Osorio wrote: Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both on the current CI solution and in getting tripleo-quickstart jobs for it); So I would like to propose him as part of the TripleO CI core team. I think he'll make a great ad

Re: [openstack-dev] [telemetry] remaining ocata items

On Tue, Jan 24, 2017 at 2:05 PM, Emilien Macchi wrote: > On Tue, Jan 24, 2017 at 12:52 PM, gordon chung wrote: > > > > > > On 24/01/17 11:53 AM, Emilien Macchi wrote: > >> Yes, even outside TripleO, it's already hard to follow all changes > >> made in projects, so please do not deprecate things

Re: [openstack-dev] [telemetry] remaining ocata items

On 24/01/17 02:05 PM, Emilien Macchi wrote: > I'm ok if you deprecate it in Ocata, as long: > > 1) it's properly document how to make a transition to the new services. > 2) We don't remove it in Pike, because work to deprecate it would have > been done end of Ocata. > > Deal? no. period. (triple

[openstack-dev] [magnum] CoreOS template v2

Hi, The CoreOS template is not really up to date and in sync with upstream CoreOS « Best Practice » (https://github.com/coreos/coreos-kubernetes), it is more a port of th fedora atomic template but CoreOS has its own Kubernetes deployment method. I’d like to implement the changes to sync kuber

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

-Original Message- From: Michał Jastrzębski Reply: OpenStack Development Mailing List (not for usage questions) Date: January 24, 2017 at 11:01:14 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverab

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think he'll

Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable

Excerpts from Ian Cordasco's message of 2017-01-24 14:55:31 -0500: > -Original Message- > From: Michał Jastrzębski > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: January 24, 2017 at 11:01:14 > To: OpenStack Development Mailing List (not for usage questio

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On Tue, Jan 24 2017, gordon chung wrote: > just curious, why doesn't vitrage send an event to aodh (on the error > topic) in this case rather than get nova to do it? if you created an > event alarm in aodh to check for vitrage error events could it solve the > use case? i don't know if we store

[openstack-dev] [Requirements] Freeze

We are going to be freezing Thursday at ~20:00 UTC. So if you need any changes we'll be needing needing them in soon, with reasoning. Thanks. -- Matthew Thode (prometheanfire) signature.asc Description: OpenPGP digital signature ___

Re: [openstack-dev] [Neutron] PTL Candidacy

Definitely, both are great candidates and my best wishes to both during this process. Given the latest issues related with the memory consumption[1] in CI jobs, I’m just wondering if you have a plan to deal and/or improve it in Neutron. Regards, Victor Morales irc: electrocucaracha [1] htt

Re: [openstack-dev] [Requirements] Freeze

Hey Matthew, The OpenStackClient team will be posting patches to bump the minimum level of python-openstacksdk to the latest release 0.9.13 (out today). We'll also be releasing a new python-openstackclient version (3.8.0), which should also be the minimum version. On Tue, Jan 24, 2017 at 3:22 PM,

Re: [openstack-dev] [Neutron] PTL Candidacy

On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > > I'm on board with getting visibility into the drivers with improvements to > > driverlog, etc. What I'm uncertain of is providing much in the lines of > > 'validation'. Core rev

Re: [openstack-dev] [magnum] CoreOS template v2

Hi. IMO, you should add a BP and start by adding a v2 driver in /contrib. Cheers, Spyros On Jan 24, 2017 20:44, "Kevin Lefevre" wrote: > Hi, > > The CoreOS template is not really up to date and in sync with upstream > CoreOS « Best Practice » (https://github.com/coreos/coreos-kubernetes), > it

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

On 24/01/17 03:05 PM, Julien Danjou wrote: > I think Aodh emits notifications when something happens so it can be in > Panko indeed. I don't think it'd be fair to force Panko to have (a > recent) history though. :) i'm going to add a work item (for anyone): allow multiple notification topics on

Re: [openstack-dev] [puppet] Thank you.

Cody, Thank you for your contributions over the years. On Fri, Jan 20, 2017 at 12:29 PM, Cody Herriges wrote: > I attempted to send this out last week but think I messed it up by sending > from my work email address which isn't the one I am signed up to the lists > with. Seeing Alex's note in

Re: [openstack-dev] [Requirements] Freeze

On 01/24/2017 02:28 PM, Steve Martinelli wrote: > > The OpenStackClient team will be posting patches to bump the minimum > level of python-openstacksdk to the latest release 0.9.13 (out today). > We'll also be releasing a new python-openstackclient version (3.8.0), > which should also be the minim

Re: [openstack-dev] [Neutron] PTL Candidacy

On 24 January 2017 at 12:46, Jeremy Stanley wrote: > On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: > > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > > > I'm on board with getting visibility into the drivers with > improvements to > > > driverlog, etc. What I'm uncertain

Re: [openstack-dev] [TripleO] Proposing Sergey (Sagi) Shnaidman for core on tripleo-ci

On Tue, Jan 24, 2017 at 12:03 PM, Juan Antonio Osorio wrote: > Sagi (sshnaidm on IRC) has done significant work in TripleO CI (both > on the current CI solution and in getting tripleo-quickstart jobs for > it); So I would like to propose him as part of the TripleO CI core team. > > I think he'll m

Re: [openstack-dev] [tripleo] Update TripleO core members

On Mon, Jan 23, 2017 at 2:03 PM, Emilien Macchi wrote: > Greeting folks, > > I would like to propose some changes in our core members: > > - Remove Jay Dobies who has not been active in TripleO for a while > (thanks Jay for your hard work!). > - Add Flavio Percoco core on tripleo-common and triple

Re: [openstack-dev] [Neutron] PTL Candidacy

On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote: > On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: >> On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: >> > I'm on board with getting visibility into the drivers with improvements to >> > driverlog, etc. What I'm uncertain o

  1   2   >