[openstack-dev] [publiccloud-wg]New Meeting Time Starting This Week

2018-07-24 Thread Zhipeng Huang
Hi Folks, As indicated in https://review.openstack.org/#/c/584389/, PCWG is moving towards a tick-tock meeting arrangements to better accommodate participants along the globe. For even weeks starting this Wed, we will have a new meeting time on UTC0700. For odd weeks we will remain for the UTC140

Re: [openstack-dev] [tripleo] [tripleo-validations] using using top-level fact vars will deprecated in future Ansible versions

2018-07-24 Thread Bogdan Dobrelya
On 7/23/18 9:33 PM, Emilien Macchi wrote: But it seems like, starting with Ansible 2.5 (what we already have in Rocky and beyond), we should encourage the usage of ansible_facts dictionary. Example: var=hostvars[inventory_hostname].ansible_facts.hostname instead of: var=ansible_hostname If th

Re: [openstack-dev] [sig][upgrades][ansible][charms][tripleo][kolla][airship] reboot or poweroff?

2018-07-24 Thread Paul Bourke
Hi James, Sorry to hear about the lack of participation. I for one am guilty of not taking part, there just seems to be never enough time in the day to cram in all the moving parts that a project like OpenStack requires. That being said, this effort is definitely one of the most important to

[openstack-dev] [cinder] about block device driver

2018-07-24 Thread Rambo
Hi,all In the Cinder repository, I noticed that the BlockDeviceDriver driver is being deprecated, and was eventually be removed with the Queens release. https://github.com/openstack/cinder/blob/stable/ocata/cinder/volume/drivers/block_device.py However,I want to use it out of tre

Re: [openstack-dev] [cinder][nova] Proper behavior for os-force_detach

2018-07-24 Thread Lee Yarwood
On 20-07-18 08:10:37, Erlon Cruz wrote: > Nice, good to know. Thanks all for the feedback. We will fix that in our > drivers. FWIW Nova does not and AFAICT never has called os-force_detach. We previously used os-terminate_connection with v2 where the connector was optional. Even then we always pr

Re: [openstack-dev] [sig][upgrades][ansible][charms][tripleo][kolla][airship] reboot or poweroff?

2018-07-24 Thread Jean-Philippe Evrard
Sorry about the lack of participation too. Monthly sounds good. Regards, JP On July 24, 2018 9:34:56 AM UTC, Paul Bourke wrote: >Hi James, > >Sorry to hear about the lack of participation. I for one am guilty of >not taking part, there just seems to be never enough time in the day to > >cram i

Re: [openstack-dev] [qa] [tempest] [patrole] Service client duplication between Tempest and Tempest plugins

2018-07-24 Thread Graham Hayes
On 23/07/2018 20:22, MONTEIRO, FELIPE C wrote: Hi, ** Intention ** Intention is to expand Patrole testing to some service clients that already exist in some Tempest plugins, for core services only. What exact projects does Patrole consider "core", and how are you making that decision? Is it

Re: [openstack-dev] [cinder] about block device driver

2018-07-24 Thread Sean McGinnis
On Tue, Jul 24, 2018 at 06:07:24PM +0800, Rambo wrote: > Hi,all > > > In the Cinder repository, I noticed that the BlockDeviceDriver driver is > being deprecated, and was eventually be removed with the Queens release. > > > https://github.com/openstack/cinder/blob/stable/ocata/cinder/volu

[openstack-dev] [tc] [all] TC Report 18-30

2018-07-24 Thread Chris Dent
HTML: https://anticdent.org/tc-report-18-30.html Yet another slow week at TC office hours. This is part of the normal ebb and flow of work, especially with feature freeze looming, but for some reason it bothers me. It reinforces my fears that the TC is either not particularly relevant or looking

[openstack-dev] OpenStack Summit Berlin - Community Voting Open

2018-07-24 Thread Ashlee Ferguson
Hi everyone, Session voting is now open for the November 2018 OpenStack Summit in Berlin! VOTE HERE Hurry, voting closes Thursday, July 26 at 11:59pm Pacific Time (Friday, July 27 at 6:59 UTC). The Programming Committees will ult

[openstack-dev] [Ironic][Octavia][Congress] The usage of Neutron API

2018-07-24 Thread Hongbin Lu
Hi folks, Neutron has landed a patch to enable strict validation on query parameters when listing resources [1]. I tested the Neutorn's change in your project's gate and the result suggested that your projects would need the fixes [2][3][4] to keep the gate functioning. Please feel free to rea

Re: [openstack-dev] [tripleo] Proposing Jose Luis Franco for TripleO core reviewer on Upgrade bits

2018-07-24 Thread Sergii Golovatiuk
++1 On Mon, Jul 23, 2018 at 6:50 PM, Jiří Stránský wrote: > +1! > > > On 20.7.2018 10:07, Carlos Camacho Gonzalez wrote: >> >> Hi!!! >> >> I'll like to propose Jose Luis Franco [1][2] for core reviewer in all the >> TripleO upgrades bits. He shows a constant and active involvement in >> improving

[openstack-dev] [opentack-dev][kuryr][ptl] PTL Candidacy for Kuryr - Stein

2018-07-24 Thread Daniel Mellado Area
Dear all, I'd like to announce my candidacy for Kuryr's PTL for the Stein cycle. In case you don't know me, I was fortunate to work as PTL on Kuryr and its related projects for the Rocky cycle where I'm happy to say that we've achieved most of the milestones we set. I would be honoured to continu

[openstack-dev] [kuryr] PTL on vacation

2018-07-24 Thread Daniel Mellado Area
Hi all, I'll be on vacation until July 31st, without easy access to email and computer. During that time Antoni Segura Puimedon (apuimedo) will be acting as my deputy (thanks in advance!) Best! Daniel __ OpenStack Developmen

Re: [openstack-dev] [tripleo] [tripleo-validations] using using top-level fact vars will deprecated in future Ansible versions

2018-07-24 Thread Matt Young
I've captured this as a point of discussion for the TripleO CI Team's planning session(s). Matt On Tue, Jul 24, 2018 at 4:59 AM Bogdan Dobrelya wrote: > > On 7/23/18 9:33 PM, Emilien Macchi wrote: > > But it seems like, starting with Ansible 2.5 (what we already have in > > Rocky and beyond), we

[openstack-dev] [infra][nova] Running NFV tests in CI

2018-07-24 Thread Artom Lifshitz
Hey all, tl;dr Humbly requesting a handful of nodes to run NFV tests in CI Intel has their NFV tests tempest plugin [1] and manages a third party CI for Nova. Two of the cores on that project (Stephen Finucane and Sean Mooney) have now moved to Red Hat, but the point still stands that there's a n

Re: [openstack-dev] [magnum] New temporary meeting on Thursdays 1700UTC

2018-07-24 Thread Spyros Trigazis
Hello list, After trial and error this is the new layout of the magnum meetings plus office hours. 1. The meeting moves to Tuesdays 2100 UTC starting today 2.1 Office hours for strigazi Tuesdays: 1300 to 1400 UTC 2.2 Office hours for flwang Wednesdays : 2200 to 2300 UTC Cheers, Spyros [0] https

Re: [openstack-dev] [infra][nova] Running NFV tests in CI

2018-07-24 Thread Clark Boylan
On Tue, Jul 24, 2018, at 9:23 AM, Artom Lifshitz wrote: > Hey all, > > tl;dr Humbly requesting a handful of nodes to run NFV tests in CI > > Intel has their NFV tests tempest plugin [1] and manages a third party > CI for Nova. Two of the cores on that project (Stephen Finucane and > Sean Mooney)

Re: [openstack-dev] [infra][nova] Running NFV tests in CI

2018-07-24 Thread Artom Lifshitz
On Tue, Jul 24, 2018 at 12:30 PM, Clark Boylan wrote: > On Tue, Jul 24, 2018, at 9:23 AM, Artom Lifshitz wrote: >> Hey all, >> >> tl;dr Humbly requesting a handful of nodes to run NFV tests in CI >> >> Intel has their NFV tests tempest plugin [1] and manages a third party >> CI for Nova. Two of th

Re: [openstack-dev] [infra][nova] Running NFV tests in CI

2018-07-24 Thread Clark Boylan
On Tue, Jul 24, 2018, at 10:21 AM, Artom Lifshitz wrote: > On Tue, Jul 24, 2018 at 12:30 PM, Clark Boylan wrote: > > On Tue, Jul 24, 2018, at 9:23 AM, Artom Lifshitz wrote: > >> Hey all, > >> > >> tl;dr Humbly requesting a handful of nodes to run NFV tests in CI > >> > >> Intel has their NFV tests

Re: [openstack-dev] [infra][nova] Running NFV tests in CI

2018-07-24 Thread Chris Friesen
On 07/24/2018 12:47 PM, Clark Boylan wrote: Can you get by with qemu or is nested virt required? Pretty sure that nested virt is needed in order to test CPU pinning. As for hugepages, I've done a quick survey of cpuinfo across our clouds and all seem to have pse available but not all have p

Re: [openstack-dev] [neutron] Please use neutron-lib 1.18.0 for Rocky

2018-07-24 Thread Boden Russell
On 7/23/18 9:46 PM, Sangho Shin wrote: > It applies also to the networking- projects. Right? Yes. It should apply to any project that's using/depending-on neutron/master today. Note that I "think" the neutron-lib version required by neutron will trump the project's required version anyway, bu

[openstack-dev] Lots of slow tests timing out jobs

2018-07-24 Thread Matt Riedemann
While going through our uncategorized gate failures [1] I found that we have a lot of jobs failing (161 in 7 days) due to the tempest run timing out [2]. I originally thought it was just the networking scenario tests, but I was able to identify a handful of API tests that are also taking nearly

[openstack-dev] [tripleo] The Weekly Owl - 26th Edition

2018-07-24 Thread Emilien Macchi
Welcome to the twenty-sixth edition of a weekly update in TripleO world! The goal is to provide a short reading (less than 5 minutes) to learn what's new this week. Any contributions and feedback are welcome. Link to the previous version: http://lists.openstack.org/pipermail/openstack-dev/2018-July

[openstack-dev] [all][election] Nominations for OpenStack PTLs (Project Team Leads) are now open

2018-07-24 Thread Emmet Hikory
Nominations for OpenStack PTLs (Program Team Leads) are now open and will remain open until July 31st, 2018 23:45 UTC. This term is expected to be slightly longer than usual, as the release cycle is expected to adjust to match the Summit schedule. All nominations must be submitted as a text file

Re: [openstack-dev] [all][election] Nominations for OpenStack PTLs (Project Team Leads) are now open

2018-07-24 Thread Jeremy Stanley
On 2018-07-25 08:54:51 +0900 (+0900), Emmet Hikory wrote: [...] > All nominations must be submitted as a text file to the openstack/election > repository as explained at > http://governance.openstack.org/election/#how-to-submit-your-candidacy > > Please make sure to follow the new candidacy file n

Re: [openstack-dev] [qa] [tempest] [patrole] Service client duplication between Tempest and Tempest plugins

2018-07-24 Thread MONTEIRO, FELIPE C
Please see comments inline. > On Tue, 24 Jul 2018 04:22:47 +0900 MONTEIRO, FELIPE C > wrote > > Hi, > > > > ** Intention ** > > Intention is to expand Patrole testing to some service clients that > already > exist in some Tempest plugins, for core services only. > > > >

Re: [openstack-dev] [qa] [tempest] [patrole] Service client duplication between Tempest and Tempest plugins

2018-07-24 Thread Ghanshyam Mann
On Wed, 25 Jul 2018 10:27:26 +0900 MONTEIRO, FELIPE C wrote > Please see comments inline. > > > On Tue, 24 Jul 2018 04:22:47 +0900 MONTEIRO, FELIPE C > > wrote > > > Hi, > > > > > > ** Intention ** > > > Intention is to expand Patrole testing t

Re: [openstack-dev] [qa] [tempest] [patrole] Service client duplication between Tempest and Tempest plugins

2018-07-24 Thread MONTEIRO, FELIPE C
> > Hi, > > > > ** Intention ** > > > > Intention is to expand Patrole testing to some service clients that > > already exist in some Tempest plugins, for core services only. > > What exact projects does Patrole consider "core", and how are you making > that decision? Is it a tag, InterOp, or some

[openstack-dev] [kolla] ptl non candidacy

2018-07-24 Thread Jeffrey Zhang
Hi all, I just wanna to say I am not running PTL for Stein cycle. I have been involved in Kolla project for almost 3 years. And recently my work changes a little, too. So I may not have much time in the community in the future. Kolla is a great project and the community is also awesome. I would en

Re: [openstack-dev] Lots of slow tests timing out jobs

2018-07-24 Thread Ghanshyam Mann
On Wed, 25 Jul 2018 05:15:53 +0900 Matt Riedemann wrote > While going through our uncategorized gate failures [1] I found that we > have a lot of jobs failing (161 in 7 days) due to the tempest run timing > out [2]. I originally thought it was just the networking scenario tests,