Re: [openstack-dev] [zaqar] Not run for PTL

Thanks for your hard working in Zaqar during these years. Glad to know you're still here. ;) 2018-01-23 16:10 GMT+08:00 hao wang : > Thanks Feilong, it's very great to work together with you ! > > 2018-01-23 10:56 GMT+08:00 Fei Long Wang : > > Hi

Re: [openstack-dev] [neutron][neutron-fwaas] Request for inclusion of bug fixes in RC

Thanks An. The team has been working with An to review and validate these changes – we believe we are close to the final version and should be able to merge by tomorrow barring any unforeseen surprises. So pls consider adding these to the RC as they address some critical issues as outlined

[openstack-dev] [neutron][neutron-fwaas] Request for inclusion of bug fixes in RC

Hi, I would like to request inclusion of the following patches which address bugs found in our testing. https://review.openstack.org/#/c/539461/ Addressing: https://bugs.launchpad.net/neutron/+bug/1746404 'auto_associate_default_firewall_group' got an error when new port is created We started

[openstack-dev] [QA][ptl] Quality Assurance PTL Candidacy for Rocky

Hi everyone, I would like to announce my PTL candidacy of the Quality Assurance for Rocky cycle. I am glad and lucky to work in OpenStack community and would like to thank all the contributors who supported me to explore new things and ideas. You might know me as gmann on IRC. I have joined the

[openstack-dev] [heat][ptl] PTL Candidacy for Rocky

Hi All, I would like to nominate myself to take the role of Heat PTL for Rocky release. I'd been involved with the project for two and half years. And it's my privilege to work and learn from this great team and have the honor to serve as Pike and Queens PTL. With last haft year, team achieves

[openstack-dev] [refstack][ptl] PTL Candidacy for Rocky

I am submitting my self nomination to serve as the RefStack PTL for the Rocky development cycle. For the Rocky cycle, I will continue to focus efforts on moving the RefStack Server and Client into maintenance mode. Outstanding tasks include: * Adding funtionality to upload subunit data for

Re: [openstack-dev] [ptg] Dublin PTG schedule up

Sweet thanks Thierry, Only issue is I see what days things are happening, but not what rooms things are in. Unless I'm failing at reading a table. Matt On Fri, Feb 2, 2018 at 8:02 AM, Thierry Carrez wrote: > Hi everyone, > > The schedule for the Dublin PTG is now posted

Re: [openstack-dev] [release][PTL] Cycle highlights reminder

Hi all, With Queens-3 behind us and RC1 coming up, wanted to give a gentle reminder about the cycle-highlights. To get the party started, I added an example highlight for Cinder, Horizon, Ironic and Nova (modify as necessary!): https://review.openstack.org/#/c/540171/

[openstack-dev] [release] Release countdown for week R-3, February 3 - 9

We are already starting on RC week. Time flies when you're having fun. Development Focus - The Release Candidate (RC) deadline is this Thursday, the 8th. Work should be focused on any release-critical bugs and wrapping up and remaining feature work. General Information

Re: [openstack-dev] [requirements] FFE for delayed libraries

On 02/01/2018 01:47 PM, Matthew Thode wrote: On 18-02-01 13:44:19, Sean McGinnis wrote: Due to gate issues and other delays, there's quite a handful of libs that were not released in time for the requirements freeze. We now believe we've gotten all libraries processed for the final Queens

[openstack-dev] [ptg] Dublin PTG schedule up

Hi everyone, The schedule for the Dublin PTG is now posted on the PTG website: https://www.openstack.org/ptg#tab_schedule I'll post on this thread if anything changes, but it's pretty unlikely at this point. Note that we have a lot of available rooms on Monday/Tuesday to discuss additional

Re: [openstack-dev] [api-wg] [api] [cinder] [nova] Support specify action name in request url

On Jan 18, 2018, at 4:07 AM, TommyLike Hu wrote: >Recently We found an issue related to our OpenStack action APIs. We > usually expose our OpenStack APIs by registering them to our API Gateway (for > instance Kong [1]), but it becomes very difficult when regarding to

Re: [openstack-dev] [requirements] FFE for delayed libraries

On 18-02-01 13:44:19, Sean McGinnis wrote: > Due to gate issues and other delays, there's quite a handful of libs that were > not released in time for the requirements freeze. > > We now believe we've gotten all libraries processed for the final Queens > releases. In order to reduce the load, we

[openstack-dev] [requirements] FFE for delayed libraries

Due to gate issues and other delays, there's quite a handful of libs that were not released in time for the requirements freeze. We now believe we've gotten all libraries processed for the final Queens releases. In order to reduce the load, we have batches all upper constraints bumps for these

Re: [openstack-dev] [telemetry][heat][mistral][sdk][searchlight][senlin][tacker][tricircle][tripleo] Missing Queens releases

Just confirming and closing things out. We did not receive any negative responses to the plan below, so a little earlier today I approved the mentioned patch and we cut releases and branches for all libs. The next step if for these new versions to pass CI and get FFEs to raise the upper

[openstack-dev] [docs][ptl] PTL candidacy for Docs

Hi all, I'd like to announce my candidacy for PTL of the Docs project for Rocky. I've been the Docs PTL since Queens and besides my work on OpenStack docs, I also contribute to the RDO Project. During the Queens cycle, we mostly finalized our work on project docs migration, we also continued

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

Zane Bitter writes: > Yeah, it's definitely nice to have that flexibility. e.g. here is a > patch that wouldn't merge for 3 months because the thing it was > dependent on also got proposed as a backport: > > https://review.openstack.org/#/c/514761/1 > > From an OpenStack

Re: [openstack-dev] [infra][all] New Zuul Depends-On syntax

On 25/01/18 19:08, James E. Blair wrote: Mathieu Gagné writes: On Thu, Jan 25, 2018 at 3:55 PM, Ben Nemec wrote: I'm curious what this means as far as best practices for inter-patch references. In the past my understanding was the the change id

Re: [openstack-dev] [neutron-lbaas][octavia]Octavia request poll interval not respected

Hi Mihaela, The polling logic that the neutron-lbaas octavia driver uses to update the neutron database is as follows: Once a Create/Update/Delete action is executed against a load balancer using the Octavia driver a polling thread is created. On every request_poll_interval the thread queries

Re: [openstack-dev] [Release-job-failures] [i18n][senlin][release] Tag of openstack/python-senlinclient failed

Excerpts from zuul's message of 2018-02-01 17:03:06 +: > Build failed. > > - publish-openstack-releasenotes > http://logs.openstack.org/f8/f84d8220a3df4421c1cfa7ee7b1e551b57c3505d/tag/publish-openstack-releasenotes/49c0e16/ > : POST_FAILURE in 5m 48s > This failure to build the senlin

[openstack-dev] [docs] Core review stats for February

Hi all, This is more of an FYI for people interested in all things docs that the docs core team agreed on opening up the process for new docs core nominations or removals. Instead of using a private list, this will now be discussed in public, using the openstack-dev list, as documented here:

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Today's meeting was primarily focused on a request for guidance related to action endpoints and on planning topics for the upcoming PTG. Tommy Hu has sent an email to the developer list[7] describing how several types of actions are currently being handled

Re: [openstack-dev] [tripleo]Testing ironic in the overcloud

On Thu, Feb 1, 2018 at 8:05 AM, Derek Higgins wrote: [...] > o Should I create a new tempest test for baremetal as some of the >>> networking stuff is different? >>> >> >> I think we would need to run baremetal tests for this new featureset, see >> existing files for examples.

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

> > Fair point. When the "VM/baremetal workgroup" was originally formed, > the goal was more about building clouds with both types of resources, > making them behave similarly from a user perspective, etc. Somehow > we got into talking applications and these other topics came up, which > seemed

Re: [openstack-dev] [tripleo]Testing ironic in the overcloud

On 1 February 2018 at 15:36, Emilien Macchi wrote: > > > On Thu, Feb 1, 2018 at 6:35 AM, Derek Higgins wrote: > >> Hi All, >>I've been working on a set of patches as a WIP to test ironic in the >> overcloud[1], the approach I've started with is to add

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

On 2/1/2018 2:56 AM, Saverio Proto wrote: Hello ! thanks for accepting the patch :) It looks like the best is always to send an email and have a short discussion together, when we are not sure about a patch. thank you Cheers, Saverio There is also the #openstack-stable IRC channel if you

[openstack-dev] [keystone] Queens RC review dashboard

Hey all, Just like with feature freeze, I put together a review dashboard that contains patches we need to land in order to cut a release candidate [0]. I'll be adding more patches throughout the day, but so far there are 21 changes there waiting for review. If there is something I missed, please

Re: [openstack-dev] [tripleo]Testing ironic in the overcloud

On Thu, Feb 1, 2018 at 6:35 AM, Derek Higgins wrote: > Hi All, >I've been working on a set of patches as a WIP to test ironic in the > overcloud[1], the approach I've started with is to add ironic into the > overcloud controller in scenario004. Also to run a script on the

[openstack-dev] [tripleo]Testing ironic in the overcloud

Hi All, I've been working on a set of patches as a WIP to test ironic in the overcloud[1], the approach I've started with is to add ironic into the overcloud controller in scenario004. Also to run a script on the controller (as a NodeExtraConfigPost) that sets up a VM with vbmc that can then be

Re: [openstack-dev] [vitrage][ptl] PTL candidacy for Rocky

Sorry for the copy problem in the previous email… Ifat On 01/02/2018, 15:24, "Afek, Ifat (Nokia - IL/Kfar Sava)" wrote: Hi all, I would like to announce my candidacy to continue as Vitrage PTL for the Rocky release. I’ve been the PTL of Vitrage

[openstack-dev] [neutron-lbaas][octavia]Octavia request poll interval not respected

Hello, I have the following setup: Neutron - Newton version Octavia - Ocata version Neutron LBaaS had the following configuration in services_lbaas.conf: [octavia] .. # Interval in seconds to poll octavia when an entity is created, updated, or # deleted. (integer value)

[openstack-dev] [vitrage][ptl] PTL candidacy for Rocky

Hi all, I would like to announce my candidacy to continue as Vitrage PTL for the Rocky release. I’ve been the PTL of Vitrage since the day it started, in the Mitaka release. I think we have made an amazing journey, and we now have a mature, stable and well known project. During the Queens cycle

Re: [openstack-dev] PTG Dublin - Price Increase this Thursday

Reminder: Last hours to pick up your PTG ticket at normal price ! Kendall Waters wrote: > Hi everyone, > > We are four weeks out from the Dublin Project Teams Gathering (February > 26 - March 2nd), and we are expecting the event to sell out! You have > two more days to book your ticket at the

Re: [openstack-dev] [tripleo] opendaylight OpenDaylightConnectionProtocol deprecation issue

> -Original Message- > From: Ben Nemec [mailto:openst...@nemebean.com] > Sent: Wednesday, January 31, 2018 5:10 PM > To: OpenStack Development Mailing List (not for usage questions) > ; Moshe Levi > > Subject: Re: [openstack-dev]

Re: [openstack-dev] [nova] Requesting eyes on fix for bug 1686703

On 31 January 2018 at 16:32, Matt Riedemann wrote: > On 1/31/2018 7:30 AM, Matthew Booth wrote: > >> Could I please have some eyes on this bugfix: >> https://review.openstack.org/#/c/462521/ . I addressed an issue raised >> in August 2017, and it's had no negative feedback

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Hello ! thanks for accepting the patch :) It looks like the best is always to send an email and have a short discussion together, when we are not sure about a patch. thank you Cheers, Saverio __ OpenStack Development

Re: [openstack-dev] [sdk][ptl] PTL Candidacy for Rocky

Big +1 from me :) — Best regards Slawek Kaplonski sla...@kaplonski.pl > Wiadomość napisana przez Monty Taylor w dniu > 31.01.2018, o godz. 16:54: > > Hi everybody! > > I'd like to run for PTL of OpenStackSDK again > > This last cycle was pretty exciting. We merged