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

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

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

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

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

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

[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

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

[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

[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

[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

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 >

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

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

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

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

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

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

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

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

[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

[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

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

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

+1 for both. regards Shu > -Original Message- > From: Pradeep Singh [mailto:ps4openst...@gmail.com] > Sent: Tuesday, January 24, 2017 11:58 AM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Re: [openstack-dev] [Zun]

[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

[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

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

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

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.

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

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

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

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

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

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

[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

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 >

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

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,

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

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

[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

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

[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

[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

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

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

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

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:rosmaita.foss...@gmail.com] Sent: Tuesday, January 24, 2017 4:32 AM Cc: Sabari Murugesan; OpenStack Development

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

[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

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

[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 openstack@l.o.o 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

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

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

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

[openstack-dev] [Heat] Breaking change to 3rd-party Template plugin API

This email is directed at anyone who maintains a 3rd-party Template plugin for Heat. (Do such people exist?) Good news: you know how it's never been clear what parts of the Stack and Resource interfaces you could rely on to be stable? I'm proposing to fix that in Pike. Bad news: you know

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

On 2017-01-24 13:10:26 -0800 (-0800), Ihar Hrachyshka wrote: > On Tue, Jan 24, 2017 at 12:46 PM, Jeremy Stanley wrote: [...] > > I guess the question I have is who, then, can tell our > > operators/users what Neutron drivers are reasonably supported? It > > sounds like you're

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

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

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

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

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

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

As Spyros mentioned, an option is to start by cloning the existing templates. However, I have a concern for this approach because it will incur a lot of duplication. An alternative approach is modifying the existing CoreOS templates in-place. It might be a little difficult to implement but it

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.

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

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

Le 24/01/2017 22:22, Dan Smith a écrit : >> No. Have administrators set the allocation ratios for the resources they >> do not care about exceeding capacity to a very high number. >> >> If someone previously removed a filter, that doesn't mean that the >> resources were not consumed on a host.

[openstack-dev] [tripleo] Officially support Python 3.5 in Pike

OpenStack community decided to officially support Python 3.5 by the end of Pike cycle: https://governance.openstack.org/tc/goals/pike/python35.html To track this work in TripleO, I created a blueprint: https://blueprints.launchpad.net/tripleo/+spec/support-python-35 I'm also tracking the work

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

On 1/24/2017 2:38 PM, Sylvain Bauza wrote: It's litterally 2 days before FeatureFreeze and we ask operators to change their cloud right now ? Looks difficult to me and like I said in multiple places by email, we have a ton of assertions saying it's acceptable to have not all the filters.

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

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 »

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]

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

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

> No. Have administrators set the allocation ratios for the resources they > do not care about exceeding capacity to a very high number. > > If someone previously removed a filter, that doesn't mean that the > resources were not consumed on a host. It merely means the admin was > willing to

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

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

[openstack-dev] [tacker] Core team changes / proposing Dharmendra Kushwaha

Tackers, I'd like to propose following changes to the Tacker core team. Stephen Wong After being associated with Tacker project from its genesis, Stephen Wong (irc: s3wong) has decided to step down from the core-team. I would like to thank Stephen for his contribution to Tacker, particularly

Re: [openstack-dev] [neutron] PTL candidacy

>I would really like us to discuss this issue head-on and see what is missing in Neutron APIs and what would take to make them extensible so that vendors do not run around trying to figure out alternative solutions The Neutron API is already very extensible and that's problematic. Right now a

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

There is a SFC Horizon code patch available. And our presentation video GUI is based on that. Louis/Vikram, I am on business trip and have difficulty to access some openstack links. Could you share the link to our SFC Horizon work? Thanks, Cathy -Original Message- From: Bernard

Re: [openstack-dev] [neutron] change in argument type for allocate_partially_specified_segment

I pushed https://review.openstack.org/#/c/425023 as one of approaches. On Wed, Jan 25, 2017 at 10:29 AM Anna Taraday wrote: > Thanks for bringing this up! > > I was assuming that from Ocata everyone should switch from usage 'old' > TunnelTypeDriver to updated one. >

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

+1 for both. -Original Message- From: Wenzhi Yu [mailto:wenzhi...@163.com] Sent: Tuesday, January 24, 2017 7:02 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

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

Hello Bernard, I believe the design docs and API parts are good and once I had the environment up and running I didn't have any problems following the examples or running the commands. My biggest hurdle was around getting the devstack environment functioning, I was following the steps here:

Re: [openstack-dev] [neutron] change in argument type for allocate_partially_specified_segment

Thanks for bringing this up! I was assuming that from Ocata everyone should switch from usage 'old' TunnelTypeDriver to updated one. Revering both back to session means reverting all refactor and this is not in line with enginefacade work and as I remember some of OVO patches we waiting for this

Re: [openstack-dev] [requirements][docs] updating the minimum version of sphinx

On 2017-01-25 05:03, Matthew Thode wrote: > On 01/24/2017 09:57 PM, Matthew Thode wrote: >> Basically I'd like to ask the docs people if they are fine with updating >> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to >> sphinx>=1.5.1. This change seems fairly major, especially

[openstack-dev] [infra] Problem with Jenkins

Hello! I have 2 similar patches with different change_id. On the first case Jenkins has failed: https://review.openstack.org/#/c/422481/ , on the second case Jenkins has successfully passed:https://review.openstack.org/# /c/424553/ . I can not understand the reason for it. Besides all test that

Re: [openstack-dev] [requirements][docs] updating the minimum version of sphinx

On 2017-01-25 08:24, Andreas Jaeger wrote: > On 2017-01-25 05:03, Matthew Thode wrote: >> On 01/24/2017 09:57 PM, Matthew Thode wrote: >>> Basically I'd like to ask the docs people if they are fine with updating >>> the minimum version of sphinx from sphinx>=1.2.1,!=1.3b1,<1.4 to >>>

Re: [openstack-dev] [nova] Announcing my PTL candidacy for Pike

Thanks for stepping up again, Matt! You've been an excellent Nova PTL: knowledgeable, diligent, pragmatic, welcoming, (and fun!). I look forward to working with you and learning from you in the next release. Thanks for all you do (and thanks to your family too)! Enjoy your time in Mexico; you

Re: [openstack-dev] [nova] [placement] [operators] Optional resource asking or not?

On 1/24/2017 2:57 PM, Matt Riedemann wrote: On 1/24/2017 2:38 PM, Sylvain Bauza wrote: It's litterally 2 days before FeatureFreeze and we ask operators to change their cloud right now ? Looks difficult to me and like I said in multiple places by email, we have a ton of assertions saying it's

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

Or start writing down (in the BP) what you want to put in the driver. Network, lbaas, scripts, the order of the scripts and then we can see if it's possible to adapt to the current coreos driver. Spyros On Jan 24, 2017 22:54, "Hongbin Lu" wrote: > As Spyros mentioned, an

[openstack-dev] [neutron] change in argument type for allocate_partially_specified_segment

Hi Anna, I see that as part of [1], we changed the argument type for the $subj function from session to context. Sadly, it turns out we still call it with a session from the 'old' TunnelTypeDriver. I suspect the same issue may affect allocate_fully_specified_segment. I assume that means all

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

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

In deed, excellent and well qualified candidates. Best of Luck to both -Sukhdev On Tue, Jan 24, 2017 at 7:16 AM, Armando M. wrote: > Hi neutrinos, > > No, it's not what you might be thinking...I am just delighted to see two > excellent candidates willing to take the

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

On Tue, Jan 24, 2017 at 11:53 AM, Alexis Monville < alexis.monvi...@redhat.com> wrote: > > > > > I spent quite a bit of our cross project session at the Ocata Summit > doing a > > quick recap of the concept of Servant Leadership and it seemed like > plenty > > of attendees appreciated that. Would

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

Cathy, I believe Mohan Kumar did that work. - Louis -Original Message- From: Cathy Zhang Sent: Tuesday, January 24, 2017 5:39 PM To: OpenStack Development Mailing List (not for usage questions); Henry Fourie; Vikram Choudhary Cc: Cathy Zhang Subject: RE: [openstack-dev]

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

2017-01-25 0:27 GMT+08:00 Matt Riedemann : > 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

  1   2   >