Re: [openstack-dev] [nova] How to use resource_providers for shared disk resources (NFS)

Hi Jay, Thank you for information. :) Thank you, Bhagyashri -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Monday, January 30, 2017 11:31 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] How to use resource_providers for shared disk

Re: [openstack-dev] [ux] Future of the OpenStack UX team

Shamail wrote: >> Sorry for not noticing this thread and replying earlier. >> >> I've now reviewed the minutes from the meeting, and I support thingee's >> suggestion of having a UX working group. This way, UX can get the attention >> it rightly deserves. Without the research and guidelines

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 1st February

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 1st February in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

[openstack-dev] [nova] Apparently cells v1 doesn't want you swapping volumes

We've got a gate blocker introduced today: https://bugs.launchpad.net/devstack/+bug/1660511 I've got patches up to nova and devstack (first one in wins) to fix the issue by blacklisting testing swap volume in the cells v1 job. This is an FYI since I've been seeing nova changes in the gate

[openstack-dev] [Infra][Tacker] Creating feature branch for Tacker

Hello Infra team, I am implementing new API framework in tacker based on Falcon. We have decided to create separate branch for this so that we can push all the code to feature branch and once dev is completed, will merge branch to master. So we need to create Feature/branch in Tacker. Reference

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

On 1/26/2017 8:32 PM, Artom Lifshitz wrote: Since the consensus is to fix this with a new microversion, I've submitted some patches: * https://review.openstack.org/#/c/426030/ A spec for the new microversion in case folks want one. Merged. * https://review.openstack.org/#/c/424759/ The

[openstack-dev] [nova] nova-status upgrade check failing in grenade run

I've got a patch up to grenade to try and integrate the nova-status upgrade check command as part of the upgrade from newton to ocata: https://review.openstack.org/#/c/426926/ That's failing one of the checks in nova-status, the details are in a bug report I've created:

Re: [openstack-dev] [Neutron] Towards better stability of gate jobs

+1. Also, if you cant see why a particular job failed, ask in the openstack-neutron IRC channel to get more eyes on it. On Jan 30, 2017 9:39 AM, "Jakub Libosvar" wrote: > Hi all, > > we've been struggling with functional and fullstack jobs for a while > now and we'd like to

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

Hi, We are jovial 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. Continue

Re: [openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/30/2017 02:38 PM, Doug Hellmann wrote: > If we only update the constraint list, it would not be safe to > release something that relied on the features in the newer version, > because our minimum version in the global requirements list will >

Re: [openstack-dev] [QA] Gate Jobs failing after patch for bug/1628016

Thanks Andrea! For the first I will do as advised. I will just add the prefix before the name then append the path afterwards. For the second test with end_marker I will just make that upper case (‘ZzzzObject1234567890’) a lower case (‘Object1234567890’) I believe this was the intended

Re: [openstack-dev] [trove][Neutron] Towards better stability of gate jobs

I'd like to add the same call-to-action for Trove as well. When you see a gate failure, please don't simply recheck. Let's start tracking failure patterns in Launchpad and fix them. I know this is a change from what we've been doing a lot of in Trove of late so I realize that it will take some

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/glance failed

-Original Message- From: A mailing list for the OpenStack Stable Branch test reports. Reply: openstack-dev@lists.openstack.org Date: January 30, 2017 at 00:16:19 To: openstack-stable-ma...@lists.openstack.org

Re: [openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint

Excerpts from Major Hayden's message of 2017-01-30 11:55:39 -0600: > Hello there, > > I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. > > We previously set the upper constraint to 2.8.1[1] when a change appeared > that broke Ansible. The bug caused the `groupby` filter

Re: [openstack-dev] [kolla] Contributors welcome to kolla-kubernetes 0.5.0

Yes, I'd like to contribute to the blueprints and will ask questions in the kolla IRC channel. Regards, Vikram Hosakote IRC: vhosakot From: "Steven Dake (stdake)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [requirements][neutron][ffe] Jinja2 2.9.5 upper constraint

Matthew, Major, I am ok with just upper-constraints. If it were g-r then we would have to re-release 2 oslo libs at least. http://codesearch.openstack.org/?q=jinja2=fosho=.*require.*%5C.txt=oslo.middleware,oslo.reports Thanks, Dims On Mon, Jan 30, 2017 at 2:30 PM, Matthew Thode

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

Hi all, Thanks for the votes. According to the feedback, this proposal is approved. Welcome Kevin to the core team. Best regards, Hongbin -Original Message- From: Qiming Teng [mailto:teng...@linux.vnet.ibm.com] Sent: January-29-17 6:54 AM To: OpenStack Development Mailing List (not

Re: [openstack-dev] [requirements][neutron][ffe] Jinja2 2.9.5 upper constraint

On 01/30/2017 11:55 AM, Major Hayden wrote: > Hello there, > > I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. > > We previously set the upper constraint to 2.8.1[1] when a change appeared > that broke Ansible. The bug caused the `groupby` filter to return a >

Re: [openstack-dev] [requirements][ffe] oslo.context 2.12.1 in upper-constraints

On 01/30/2017 12:20 PM, Davanum Srinivas wrote: > Team, > > We have a fix in oslo.context for the problem reported over the weekend: > http://lists.openstack.org/pipermail/openstack-dev/2017-January/49.html > > A fix to disable warnings was merged into master, then cherry-picked > to

[openstack-dev] [requirements][ffe] oslo.context 2.12.1 in upper-constraints

Team, We have a fix in oslo.context for the problem reported over the weekend: http://lists.openstack.org/pipermail/openstack-dev/2017-January/49.html A fix to disable warnings was merged into master, then cherry-picked to stable/ocata. Let's please update the upper-constraints with this new

Re: [openstack-dev] [nova] How to use resource_providers for shared disk resources (NFS)

On 01/30/2017 05:55 AM, Shewale, Bhagyashri wrote: Hi nova devs, How can I use placement api's if my instance path is mounted on shared storage server (e.g. NFS)? I am trying to set multinode setup with NFS shared storage for all nodes to share disk resources along with placement services. As

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

Serg, you forgot that Glare v1 != Glare v0.1. And there is a small issue - Glare v0.1 is deprecated. So I'm just wondering what are your future plans about Glare v1. Will you use it or simply copy the v0.1 code into Murano repo? Best, Mike On Thu, Jan 26, 2017 at 2:03 AM, Serg Melikyan

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

Thanks Renat! I agree, currently we do not have a specific plan, and also several required features, like storing small blobs in database, are not merged yet. We definitely should talk about it more detailed during (and probably before) PTG. At least one session will be dedicated directly to this

[openstack-dev] [requirements][ffe] Jinja2 2.9.5 upper constraint

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello there, I just submitted a patch[0] to bump Jinja2's upper constraint to 2.9.5. We previously set the upper constraint to 2.8.1[1] when a change appeared that broke Ansible. The bug caused the `groupby` filter to return a namedtuple and it

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

Thanks everyone! On 2017-01-30 10:45, Emilien Macchi wrote: > Honza, you're now core on tripleo-ui project. Thanks for your hard > work and congrats! > > On Fri, Jan 27, 2017 at 2:45 AM, Dougal Matthews wrote: > > +1! > > > > On 25 January 2017 at 15:28, Steven Hardy

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

On 29/01/17 08:52 AM, Afek, Ifat (Nokia - IL) wrote: > On 26/01/2017, 20:09, "Julien Danjou" wrote: > >> On Thu, Jan 26 2017, gordon chung wrote: >> >>> On 26/01/17 11:41 AM, Julien Danjou wrote: >> >>> and vitrage would be an alarm orchestrator? >> >> Yup, something like

Re: [openstack-dev] [magnum][kuryr] python-k8sclient vs client-python (was Fwd: client-python Beta Release)

On Thu, Jan 26, 2017 at 12:41 PM, Davanum Srinivas wrote: > Team, > > A bit of history, we had a client generated from swagger definition for a > while in Magnum, we plucked it out into python-k8sclient which then got > used by fuel-ccp, kuryr etc. Recently the kuberneted team

Re: [openstack-dev] [QA] Gate Jobs failing after patch for bug/1628016

On Mon, Jan 30, 2017 at 3:25 PM White, Joshua L wrote: > Hi Team, > > > > I would like to get your feedback on the gate jobs failing and how to > alleviate the issue. > > > > The gate jobs are failing once the prefix is actually added for these > tests jobs below: > > >

[openstack-dev] [neutron] [classifier] No Common Classification Framework meeting

Hi, There will be no Common Classification Framework this week. The PTG PoC is still being worked on and is starting to look good, kudos to David for most of the work so far. Best regards, Igor. __ OpenStack Development

[openstack-dev] [Neutron] Towards better stability of gate jobs

Hi all, we've been struggling with functional and fullstack jobs for a while now and we'd like to bring a better stability to it as the failure rate is still quite high. This is getting annoying, specifically for voting functional job, which makes it sometimes harder to get some of our beautiful

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 5)

On Mon, Jan 30, 2017 at 03:07:42PM +0100, Gabriele Cerami wrote: > On 30 Jan, Paul Belanger wrote: > > > Before you go out an implement some sort of in-repo configuration for > > testing, I > > strongly encourage you to read up on our Zuulv3 spec[3], as we are providing > > this functionality.

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

Sagi, you're now core on TripleO CI repo. Thanks for your hard work on tripleo-quickstart transition, and also helping by keeping CI in good shape, your work is amazing! Congrats! Note: I couldn't add you to tripleo-ci group, but only to tripleo-core (Gerrit permissions), which mean you can +2

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

On 01/24/2017 04:49 AM, Kirill Proskurin wrote: 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

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

Flavio, Steve, you're now core in TripleO ! Flavio: core on tripleo-common and tripleo-heat-templates docker bits. Steve: os-collect-config and also docker bits in tripleo-common and tripleo-heat-templates. Thanks for your hard work, keep rocking! Congrats :-) On Fri, Jan 27, 2017 at 2:44 AM,

Re: [openstack-dev] [Requirements] Freeze

No worries, good to know I did not miss anything about release procedures :-) Thanks, Dmitry On Mon, Jan 30, 2017 at 6:51 PM, Matthew Thode wrote: > On 01/30/2017 03:24 AM, Dmitry Mescheryakov wrote: > > Hello Matthew, > > > > I see that you have frozen my > > CR

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

Honza, you're now core on tripleo-ui project. Thanks for your hard work and congrats! On Fri, Jan 27, 2017 at 2:45 AM, Dougal Matthews wrote: > +1! > > On 25 January 2017 at 15:28, Steven Hardy wrote: >> >> On Tue, Jan 24, 2017 at 08:52:51AM -0500, Emilien

[openstack-dev] [nova] TODOs before ocata rc1

I've started an etherpad for at least my own sanity to track TODOs before we can cut the rc1 tag for Ocata: https://etherpad.openstack.org/p/nova-ocata-rc1-todos This is mostly going to identifying release-critical bugs that we need to fix and closing gaps on release notes and documentation.

[openstack-dev] [QA] Gate Jobs failing after patch for bug/1628016

Hi Team, I would like to get your feedback on the gate jobs failing and how to alleviate the issue. The gate jobs are failing once the prefix is actually added for these tests jobs below: 1. test_list_container_contents_with_path Issue: For some reason whoever coded this test hardcoded

[openstack-dev] [nova] Next notification meeting

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

[openstack-dev] [charms] PTG topics

Hi Team We're only a few weeks off the PTG, so I think its about time we started the ball rolling on planning our time out over the Monday/Tuesday. I've created an etherpad so we can brainstorm a schedule for the two days: https://etherpad.openstack.org/p/openstack-charms-ptg-pike If you're

Re: [openstack-dev] [Requirements] Freeze

On 01/30/2017 03:24 AM, Dmitry Mescheryakov wrote: > Hello Matthew, > > I see that you have frozen my > CR https://review.openstack.org/#/c/425132/ , but it is for > stable/newton. Should not freeze apply to master only? > > Thanks, > > Dmitry > Yep, fixed, sorry about that. -- Matthew

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 5)

On 30 Jan, Paul Belanger wrote: > Before you go out an implement some sort of in-repo configuration for > testing, I > strongly encourage you to read up on our Zuulv3 spec[3], as we are providing > this functionality. What is comes down to, you'll be able to focus on writing > tests, where zuul

Re: [openstack-dev] [tripleo] CI Squad Meeting Summary (week 5)

On Mon, Jan 30, 2017 at 01:37:56PM +0100, Attila Darazs wrote: > In the spirit of "better late than never", here's a summary of our CI Squad > meeting. > > Time: Thursdays, 15:30-16:30 UTC > Place: https://bluejeans.com/4113567798/ > > > Configuration management in TripleO CI >

Re: [openstack-dev] [nova] [placement] placement api request analysis

On Thu, 26 Jan 2017, Chris Dent wrote: On Wed, 25 Jan 2017, Chris Dent wrote: #B3 The new GET to /placement/allocations is happening when the resource tracker calls _update_usage_from_instance, which is always being called becuause is_new_instance is always true in that method, even when the

Re: [openstack-dev] [trove] status of the gate

The issues plaguing the gate have been addressed with the help of Andrey Kurilin, Jian Song and Tin Lam. Thanks y'all for your patches which were merged and helped unblock the gate[1]. As noted in the commit message there, this change includes some low quality band-aid which needs to be redone

[openstack-dev] [trove][tc][stable] trove core team coverage this week

Over the next couple of days, some members of the trove core team will be traveling and others have commitments that may cause brief periods when there is no one around immediately to respond on IRC. For anything that needs urgent attention, please email me directly and I will try to get back to

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 5)

In the spirit of "better late than never", here's a summary of our CI Squad meeting. Time: Thursdays, 15:30-16:30 UTC Place: https://bluejeans.com/4113567798/ Configuration management in TripleO CI == There was a design meeting organized by Gabrielle

Re: [openstack-dev] [OpenStack][Dev] Changes coming to Product WG & Enterprise WG

On 28/01/2017 02:56, Barrett, Carol L wrote: After 35+ yrs in the Technology Industry, I have decided it’s time for a change. I will be retiring from Intel on February 2^nd . OpenStack has been a highlight of my career and I owe much of that to you all. It’s been a pleasure knowing and

[openstack-dev] [nova] How to use resource_providers for shared disk resources (NFS)

Hi nova devs, How can I use placement api's if my instance path is mounted on shared storage server (e.g. NFS)? I am trying to set multinode setup with NFS shared storage for all nodes to share disk resources along with placement services. As of now it is creating resource providers for each

[openstack-dev] [charms] minutes from todays IRC meeting

Hi All Here are the links from todays Charms IRC meeting: Agenda: https://etherpad.openstack.org/p/openstack-charms-weekly-meeting-20170129 Minutes: http://eavesdrop.openstack.org/meetings/charms/2017/charms.2017-01-30-10.03.html Minutes (text):

Re: [openstack-dev] [openstack-ansible] Proposing Amy Marrich for core

Hello, Ofc it’s a +1! Thanks Amy for all the work :) Best regards, JP From: Alexandra Settle Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Friday, 27 January 2017 at 14:29 To: "OpenStack Development

Re: [openstack-dev] [Requirements] Freeze

Hello Matthew, I see that you have frozen my CR https://review.openstack.org/#/c/425132/ , but it is for stable/newton. Should not freeze apply to master only? Thanks, Dmitry On Wed, Jan 25, 2017 at 12:22 AM, Matthew Thode wrote: > We are going to be freezing

Re: [openstack-dev] [ux] Future of the OpenStack UX team

> On Jan 30, 2017, at 5:51 AM, Lana Brindley wrote: > > Hi Thierry, > > Sorry for not noticing this thread and replying earlier. > > I've now reviewed the minutes from the meeting, and I support thingee's > suggestion of having a UX working group. This way, UX

Re: [openstack-dev] [all][elections] PTL nomination period is now over

Yes, I replied on the other thread. Thanks :) L On 30/01/17 16:48, Kendall Nelson wrote: > Yes of course :) Did you want to schedule a meeting or just discuss here > more? > > I've seen some discussion about making UX to a working group? > > -Kendall (diablo_rojo) > > On Sun, Jan 29,