Re: [openstack-dev] [mistral] [release] [stable] Cherry-pick migration to stable/rocky

> Backporting a migration like that is OK as long as you don't skip > migrations, that is to say revision '030' of the database should be the > same on all branches. Given we've only just released rocky I expect > that will be the case here. > > You absolutely must have a release note and call

[openstack-dev] [neutron] Pep8 job failures

Hi, Recently bump of eventlet to 0.24.0 was merged in requirements repo [1]. That caused issue in Neutron and pep8 job is now failing. See [2]. So if You have pep8 failed in Your patch with error like in [3] please don’t recheck job - it will not help :) Patch to fix that is already proposed

Re: [openstack-dev] [stable][keystone] python3 goal progress and tox_install.sh removal

On Thu, Sep 06, 2018 at 03:01:01PM -0500, Lance Bragstad wrote: > I'm noticing some odd cases with respect to the python 3 community goal > [0]. So far my findings are specific to keystone repositories, but I can > imagine this affecting other projects. > > Doug generated the python 3 reviews for

[openstack-dev] [placement] update 18-36

HTML: https://anticdent.org/placement-update-18-36.html Welcome back to the placement update. The last one was [5 weeks ago](https://anticdent.org/placement-update-18-31.html). I took a break to focus on some other things for a while. I plan to make it a regular thing again, but will be

[openstack-dev] [cinder][placement] Room Scheduled for Cinder Placement Discussion ...

All, The results of the Doodle poll suggested that the end of the day Tuesday was the best option for us all to get together. [1] I have scheduled the Big Thompson Room on Tuesday from 15:15 to 17:00. I hope we can all get together there and then to have a good discussion. Thanks! Jay [1]

Re: [openstack-dev] [election] [tc] TC candidacy

On 09/07/2018 11:19 AM, Samuel Cassiba wrote: On Fri, Sep 7, 2018 at 8:55 AM, Samuel Cassiba wrote: On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: On 9/5/2018 2:49 PM, Samuel Cassiba wrote: Though my hands-on experience goes back several releases, I still view things from the

Re: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

On 09/07/2018 11:17 AM, Dan Smith wrote: The other obvious thing is the database. The placement repo code as-is today still has the check for whether or not it should use the placement database but falls back to using the nova_api database [5]. So technically you could point the extracted

Re: [openstack-dev] [nova][cinder] about unified limits

That would be great! I can break down the work a little bit to help describe where we are at with different parts of the initiative. Hopefully it will be useful for your colleagues in case they haven't been closely following the effort. # keystone Based on the initial note in this thread, I'm

Re: [openstack-dev] [stable][keystone] python3 goal progress and tox_install.sh removal

Thanks for all the help, everyone. Updating the status of reach repository and branch with respect to the python3 goal and which reviews are needed in order to get things squared away. Note that the linked python3 review is just the one to port the zuul job definitions, and not all patches

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 8:55 AM, Samuel Cassiba wrote: > On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: >> On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >>> >>> Though my hands-on experience goes back several releases, I still view >>> things from the outside-looking-in perspective. Having

Re: [openstack-dev] [election][tc] Announcing candidacy

On Fri, Sep 7, 2018 at 9:21 PM Matt Riedemann wrote: > On 9/6/2018 1:49 PM, Rico Lin wrote: > > * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV) > > Are there some specific initiatives or deliverables you have in mind > here, or just general open communication channels? It's very

Re: [openstack-dev] [election] [tc] TC candidacy

On Fri, Sep 7, 2018 at 6:22 AM, Matt Riedemann wrote: > On 9/5/2018 2:49 PM, Samuel Cassiba wrote: >> >> Though my hands-on experience goes back several releases, I still view >> things from the outside-looking-in perspective. Having the outsider >> lens is crucial in the long-term for any

[openstack-dev] [cinder][ptg] Topics scheduled for next week ...

Team, I have created an etherpad for each of the days of the PTG and split out the proposed topics from the planning etherpad into the individual days for discussion: [1] [2] [3] If you want to add an additional topic please add it to Friday or find some time on one of the other days. I

Re: [openstack-dev] [Openstack] OpenStack Rocky for Ubuntu 18.04 LTS

Corey, Awesome! Excited to see Octavia included in the release. Michael On Fri, Sep 7, 2018 at 8:19 AM Corey Bryant wrote: > > The Ubuntu OpenStack team at Canonical is pleased to announce the general > availability of OpenStack Rocky on Ubuntu 18.04 LTS via the Ubuntu Cloud > Archive.

[openstack-dev] [goals][python3][ptl] ptg discussions about python3 goal

Based on some feedback for goal champions from the last PTG, I thought it would be a good idea to be explicit about the best way to reach me in case your team has questions about the python3 goal (unfortunately I'm the only champion for that goal who is able to be at the PTG this time). There is

Re: [openstack-dev] [nova][cinder] about unified limits

I will also note that I had an oslo.limit topic on the Oslo PTG schedule: https://etherpad.openstack.org/p/oslo-stein-ptg-planning I don't know whether anybody from Jaze's team will be there, but if so that would be a good opportunity for some face-to-face discussion. I didn't give it a whole

Re: [openstack-dev] [election][tc] announcing candidacy

On 9/4/2018 7:15 PM, Julia Kreger wrote: The most specific thing that is weighing on my mind is elevating and supporting contributors. While this is not new, I think we as a community need to refocus on it because they are very fibers that make up the fabric of our community and ultimately the

[openstack-dev] [keystone] 2018 User Survey Results

The foundation just gave me a copy of the latest feedback from our users. I wanted to share this with the group so people have time to digest it prior to the PTG next week [0]. Here is the total count based on each response: Federated identity enhancements had *184* responses Performance

[openstack-dev] it may be a bug of swift3 1.7.0 or ?

Hi, Environment: openstack (liberty) swift swift3: 1.7.0 boto: 2.48.0 If bucket name has unicode characters such as Chinese words (`u'\u54e6\u76c6\u65af\u5766'`), boto will return "AccessDenied". See this (https://github.com/boto/boto3/issues/1693) for

Re: [openstack-dev] [election] [tc] TC Candidacy

On 9/5/2018 1:20 PM, Kristi Nikolla wrote: I’m really excited to have the opportunity to take part in the discussion with regards to the technical vision for OpenStack. Regardless of election outcome, this is the first step towards a larger involvement from me in the important discussions (no

Re: [openstack-dev] [election] [tc] thank you

On 9/5/2018 10:03 AM, Anita Kuno wrote: On 2018-09-05 04:01 AM, Thierry Carrez wrote: Emilien Macchi wrote: I personally feel like some rotation needs to happen A very honourable sentiment, Emilien. +1 -- Thanks, Matt

Re: [openstack-dev] [election] [tc] TC candidacy

On 9/5/2018 6:49 PM, Zhipeng Huang wrote: I found that most of my statement for my last ran is still valid today [0][1]. I want to build strong cross-community collaboration, best practices for project level governance and more innovations for OpenStack. As I asked Rico, are there specific

Re: [openstack-dev] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked

On 18-09-07 11:09:15, Julien Danjou wrote: > On Fri, Sep 07 2018, Tony Breeds wrote: > > > On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote: > > > >> I remember that before landing the problematic patch [1] there was some > >> discussion around it. Basically the problem was not

Re: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

> The other obvious thing is the database. The placement repo code as-is > today still has the check for whether or not it should use the > placement database but falls back to using the nova_api database > [5]. So technically you could point the extracted placement at the > same nova_api database

[openstack-dev] [Openstack] OpenStack Rocky for Ubuntu 18.04 LTS

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack Rocky on Ubuntu 18.04 LTS via the Ubuntu Cloud Archive. Details of the Rocky release can be found at: https://www.openstack.org/software/rocky To get access to the Ubuntu Rocky packages: Ubuntu

Re: [openstack-dev] [election][tc] announcing candidacy

On 9/4/2018 7:30 AM, Doug Hellmann wrote: I am announcing my candidacy for a position on the OpenStack Technical Committee. I started contributing to OpenStack in 2012, not long after joining Dreamhost, and I am currently employed by Red Hat to work on OpenStack with a focus on long-term

Re: [openstack-dev] [election] [tc] TC candidacy

On 9/7/2018 8:54 AM, Zhipeng Huang wrote: One is related to the cyborg project where the team is working to build the open heterogenous resource mgmt platform. I would like to extend this mission over to kubernetes, which currently lack of such component and could benefit hugely from our work

Re: [openstack-dev] [election][tc] Announcing candidacy

On 9/6/2018 1:49 PM, Rico Lin wrote: * Cross-community integrations (K8s, CloudFoundry, Ceph, OPNFV) Are there some specific initiatives or deliverables you have in mind here, or just general open communication channels? It's very hard to gauge any kind of progress/success on the latter.

[openstack-dev] [nova][placement] No NovaScheduler meeting during PTG

Our regularly scheduled Monday nova-scheduler meeting will not take place next Monday, Sept 10th. We'll resume the following week. -efried __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Release-job-failures] Release of openstack/networking-ansible failed

Excerpts from zuul's message of 2018-09-07 12:05:20 +: > Build failed. > > - release-openstack-python > http://logs.openstack.org/63/639a3c3590ec20c33b1435e960d5331780298915/release/release-openstack-python/f485e0f/ > : POST_FAILURE in 7m 15s > - announce-release announce-release : SKIPPED

Re: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

On Fri, Sep 7, 2018 at 11:18 AM Dan Smith wrote: > > > The other obvious thing is the database. The placement repo code as-is > > today still has the check for whether or not it should use the > > placement database but falls back to using the nova_api database > > [5]. So technically you could

Re: [openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

Ghanshyam Mann wrote on 09/07/2018 02:18:13 AM: snip.. > neutron-tempest-plugin or other service test you can always avoid to > run with regex. And i do not think compute negative or DB test will > take much time to run. But still if you want to avoid to run then, I > think it is easy to

[openstack-dev] [puppet] Puppet weekly recap - week 35-36

Hello fellow Puppeteers! Welcome to the weekly Puppet recap for week 35 and 36. Because I was away last week I forgot to follow up the progress of week 35. The past two weeks has been quite calm, we have had a lot of changes due to the move away from Zuul config in project-config and the bump

Re: [openstack-dev] [nova][placement][upgrade][qa] Some upgrade-specific news on extraction

On 9/6/2018 8:29 PM, Erik McCormick wrote: We are planning to attend the upgrade sessions on Monday as a group. How about we put it there? I threw it in the upgrades sig ptg etherpad. Where it goes in the agenda on Monday afternoon is up to you guys. -- Thanks, Matt

Re: [openstack-dev] [Kolla] Denver PTG schedule

Looks like the ironic and kolla rooms are next to each other this time, so I can hop between them to help setup the conferencing etc. On Fri, 7 Sep 2018 at 15:21, Mark Goddard wrote: > Thanks for putting that together Eduardo. I've listed the sessions that I > expect to attend below. > Mark > >

Re: [openstack-dev] [nova] [placement] modified devstack using openstack/placement

On 9/6/2018 5:05 AM, Chris Dent wrote: One question I have on the lib/placement changes in devstack: Is it useful to make those changes be guarded by a conditional of the form:    if placement came from its own repo:    do the new stuff    else:    do the old stuff ? I think it

Re: [openstack-dev] [election] [tc] TC candidacy

On 9/5/2018 2:49 PM, Samuel Cassiba wrote: Though my hands-on experience goes back several releases, I still view things from the outside-looking-in perspective. Having the outsider lens is crucial in the long-term for any consensus-driven group, regardless of that consensus. Regardless of the

Re: [openstack-dev] [Kolla] Denver PTG schedule

Thanks for putting that together Eduardo. I've listed the sessions that I expect to attend below. Mark On Thu, 6 Sep 2018 at 17:40, Eduardo Gonzalez wrote: > Hi folks, > This is the schedule for Kolla Denver PTG. If someone have a hard conflict > with any discussion please let me know if we can

Re: [openstack-dev] [election] [tc] TC candidacy

Well nova-cyborg is surely on the top-priority for OpenStack cross-project collaboration. The two initiatives I mentioned is more in the field of cross-community. I think I didn't elaborate on how the TC role fit in this picture. For TC I think it is important to be able to help on the cross

Re: [openstack-dev] [election][tc] TC Candidacy

On 9/6/2018 2:59 AM, Ghanshyam Mann wrote: * Share Project teams work for Common Goals: Every cycle we have TC goals and some future direction where all the projects needs to start working. Projects try to do their best in that but big challenge for them is resource bandwidth. In Current

Re: [openstack-dev] [election] [tc] TC candidacy

Thx Matt, I think as I described in the candidacy patch, there two specific areas that I would like to do the cross-community collaboration. One is related to the cyborg project where the team is working to build the open heterogenous resource mgmt platform. I would like to extend this mission

Re: [openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

Thanks for the confirmation, I agree use internal maintain CI whitelist is a good way, and I confirmed with our CI folks that we already did so and more can be removed per Eric's test result below, so we will compare and remove unnecessary cases to get more bandwidth to run 3rd party CI. thanks

Re: [openstack-dev] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked

On Fri, Sep 07 2018, Tony Breeds wrote: > On Thu, Sep 06, 2018 at 01:33:12PM +0300, Michel Peterson wrote: > >> I remember that before landing the problematic patch [1] there was some >> discussion around it. Basically the problem was not n-odl but ceilometer >> not being in pypi, but we never

Re: [openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

On Fri, 07 Sep 2018 04:41:32 +0900 Eric Fried wrote > Jichen- > > That patch is not ever intended to merge; hope that was clear from the > start :) It was just a proving ground to demonstrate which tests still > pass when there's effectively no compute driver in play. >

Re: [openstack-dev] [tripleo] VFs not configured in SR-IOV role

Not sure which version you are using, but the service "OS::TripleO::Services::NeutronSriovHostConfig" is responsible for setting up VFs. Check if this service is enabled in the deployment. One of the missing place is being fixed - https://review.openstack.org/#/c/597985/ Regards, Saravanan KR On

[openstack-dev] [release] Release countdown for week R-30 and R-29, September 10-21

Here we go again! The Stein cycle will be slightly longer than past cycles. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/stein/schedule.html Development Focus - Focus should be on optimizing the time at

[openstack-dev] [ptls] [user survey] User Survey Privacy

Hi PTLs! A recent question came up regarding public sharing of the Project-Specific feedback questions on the OpenStack User Survey. The short answer is... this is a great idea! This information is meant to help projects improve and the information is not meant to be kept secret. Oddly

Re: [openstack-dev] [election][tc] Announcing candidacy

On 9/7/2018 12:17 PM, Rico Lin wrote: I'm refering on clear communication channels and go from Use cases to real development tasks (As I try to explain in the last section of my candidacy). Sorry, I totally missed the other details in your candidacy email because they came after your

[openstack-dev] [Storyboard] PTG Planning & Upcoming Meeting Cancelled

Hello! With the PTG in just a few days, I wanted to give some info and updates so that you are prepared. 1. This coming week's regular meeting on Wednesday will be cancelled. 2. I am planning on booking Blanca Peak for the whole afternoon on Tuesday for discussions. Just waiting for this patch

[openstack-dev] [First Contact] PTG Planning & Meeting Cancelled

Hello Everyone! I can't believe the PTG is only a few days away! We have our etherpad of discussion topics here[1]. If there is anything else we need to talk about, please add it! We will be meeting Tuesday Morning in Blanca Peak. I don't think we will fill the whole day, so it will be used for

[openstack-dev] [keystone] Keystone Team Update - Week of 3 September 2018

# Keystone Team Update - Week of 3 September 2018 ## News This week was mainly focused on the python3 community goal and ultimately cleaning up a bunch of issues with stable branches that were uncovered in those reviews. Next week is the PTG, which the group is preparing for in addition to

[openstack-dev] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

Hi Training Team, As a couple of us will be at the PTG next week it would be great to get together one of the days maybe for lunch. Wednesday would work the best for Kendall and me, but we can look into other days as well if it would not work for the majority of people around. So my questions

[openstack-dev] [neutron] [router] status bug

Hi neutrinos, I was looking at Bug [1], and noticed that router status stays ACTIVE even after -disable ? -openstack router -set disable router1 /opt/stack/neutron$ openstack router set --disable routerr1 vagrant@allinone:/opt/stack/neutron$ neutron router-show router1 neutron CLI is

Re: [openstack-dev] [os-upstream-institute] Team lunch at the PTG next week - ACTION NEEDED

I'm game! Amy (spotz) On Fri, Sep 7, 2018 at 5:30 PM, Ildiko Vancsa wrote: > Hi Training Team, > > As a couple of us will be at the PTG next week it would be great to get > together one of the days maybe for lunch. > > Wednesday would work the best for Kendall and me, but we can look into >

Re: [openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

On 9/7/2018 10:25 AM, William M Edmonds wrote: The concern that I have with whitelisting in a given CI is that it has to be done independently in every compute driver CI. So while I agree that it won't be easy to maintain tagging for compute driver on the tempest side, at least that's one

Re: [openstack-dev] [all][infra] Moving cover job from post to check pipeline

On 2018-09-06 20:10, Andreas Jaeger wrote: Citing Ian Wienand in [2] "There was a thread some time ago that suggested coverage jobs weren't doing much in the "post" pipeline because nobody looks at them and the change numbers may be difficult to find anyway [1]. This came up again in a

[openstack-dev] [horizon] No meeting next week

Hi team, A lot of us will attend PTG in Denver next week so we skip the meeting on 9/12. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] Nominating Chris Dent for placement-core

After a week with only positive responses, it is my pleasure to add Chris to the placement-core team. Welcome home, Chris. On 08/31/2018 10:45 AM, Eric Fried wrote: > The openstack/placement project [1] and its core team [2] have been > established in gerrit. > > I hereby nominate Chris Dent

Re: [openstack-dev] [Storyboard][Searchlight] Where can I find the project ID on Storyboard?

On 2018-09-08 10:10:37 +0900 (+0900), Trinh Nguyen wrote: > I'm adding Searchlight projects to the Stein deliverables with the > storyboard attribute. Where can I find the Searchlight projects ID? Right > now I can only see the project links. It can be looked up from the API like so:

Re: [openstack-dev] [release] Release countdown for week R-30 and R-29, September 10-21

Hi, Thanks for the summary. I just added Searchlight to the Stein deliverable [1]. One concern is we moved our projects to Storyboard last week, do I have to change the project file to reflect that and how? Thanks, [1] https://review.openstack.org/#/c/600889/ *Trinh Nguyen *| Founder & Chief

[openstack-dev] [Storyboard][Searchlight] Where can I find the project ID on Storyboard?

Hi Storyboard team, I'm adding Searchlight projects to the Stein deliverables with the storyboard attribute. Where can I find the Searchlight projects ID? Right now I can only see the project links. Thanks, *Trinh Nguyen *| Founder & Chief Architect *E:*

[openstack-dev] [masakari] No meeting on next week (9/10)

Hi All, Since most of us in Denver for PTG, there will be not meeting on 9/10. --- Regards, Sampath __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [networking-odl][networking-bgpvpn][Telemetry] all requirement updates are currently blocked

On Fri, Sep 07, 2018 at 11:09:15AM +0200, Julien Danjou wrote: > You can, I've already said +1 on a review a few weeks ago. :) Oh great. I'll dig that up and push forward with that side of things if you don't mind. Yours Tony. signature.asc Description: PGP signature