[openstack-dev] [Zun] Removal inactive cores

Hi all, This is an announcement about change of Zun's core team membership. The people below were removed from the Zun's core reviewer team due to their inactiveness at the last 180 days [1]. This change was voted by the existing core team and was unanimously approved. I would like to thanks

Re: [openstack-dev] [openstack-ops][heat][PTG] Heat PTG Summary

On 15/03/18 04:01, Rico Lin wrote: Hi Heat devs and ops It's a great PTG plus SnowpenStack experience. Now Rocky started. We really need all kind of input and effort to make sure we're heading toward the right way. Here is what we been discussed during PTG: * Future strategy for

Re: [openstack-dev] [nova] Review runways this cycle

On Tue, 20 Mar 2018 16:44:57 -0700, Melanie Witt wrote: As mentioned in the earlier "Rocky PTG summary - miscellaneous topics from Friday" email, this cycle we're going to experiment with a "runways" system for focusing review on approved blueprints in time-boxes. The goal here is to use a bit

Re: [openstack-dev] [nova] EC2 cleanup ?

On Mar 23, 2018, at 10:16 AM, Matt Riedemann wrote: > >> seems we have a EC2 implementation in api layer and deprecated since Mitaka, >> maybe eligible to be removed this cycle? > > That is easier said than done. There have been a couple of related attempts > in the past:

[openstack-dev] [keystone] Keystone Team Update - Week of 19 March 2018

# Keystone Team Update - Week of 19 March 2018 ## News ### Spec review meeting During our Tuesday office hours we had a call to discuss some of our open specs. We were able to reduce some of the scope creep that had arisen in the application credentials enhancement spec[1], iron out some

Re: [openstack-dev] [nova] [cyborg] Race condition in the Cyborg/Nova flow

Sundar- First thought is to simplify by NOT keeping inventory information in the cyborg db at all. The provider record in the placement service already knows the device (the provider ID, which you can look up in the cyborg db) the host (the root_provider_uuid of the provider representing

[openstack-dev] [tripleo] TripleO CI Sprint end

*Hello,On March 21 we came the end of sprint using our new team structure, and here’s the highlights.Sprint Review:Due the outage in our infra a few weeks ago, we decided to work on the automation on all the servers used in our CI, in this way, in case of a any outage, we are able to teardown all

Re: [openstack-dev] [TripleO] Alternative to empty string for default values in Heat

On 03/23/2018 11:54 AM, Giulio Fidente wrote: On 03/23/2018 05:43 PM, Wojciech Dec wrote: Hi All, I'm converting a few heat service templates that have been working ok with puppet3 modules to run with Puppet 4, and am wondering if there is a way to pass an "undefined" default via heat to

[openstack-dev] [sdk] Repo rename complete

The openstack/python-openstacksdk repo has been renamed to openstack/openstacksdk. The following patch: https://review.openstack.org/#/c/555875 Updates the .gitreview file (and other things) to point at the new repo. You'll want to update your local git remotes to pull from and submit to

Re: [openstack-dev] Following the new PTI for document build, broken local builds

Excerpts from Stephen Finucane's message of 2018-03-23 17:25:42 +: > On Fri, 2018-03-23 at 12:23 -0400, Doug Hellmann wrote: > > Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500: > > > On 03/22/2018 05:43 AM, Stephen Finucane wrote: > > > > > > > > That's unfortunate. What we

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On Fri, 2018-03-23 at 12:23 -0400, Doug Hellmann wrote: > Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500: > > On 03/22/2018 05:43 AM, Stephen Finucane wrote: > > > > > > That's unfortunate. What we really need is a migration path from the > > > 'pbr' way of doing things to

Re: [openstack-dev] [TripleO] Alternative to empty string for default values in Heat

On 03/23/2018 05:43 PM, Wojciech Dec wrote: > Hi All, > > I'm converting a few heat service templates that have been working ok > with puppet3 modules to run with Puppet 4, and am wondering if there is > a way to pass an "undefined" default via heat to allow "default" values > (eg params.pp) of

[openstack-dev] [TripleO] Alternative to empty string for default values in Heat

Hi All, I'm converting a few heat service templates that have been working ok with puppet3 modules to run with Puppet 4, and am wondering if there is a way to pass an "undefined" default via heat to allow "default" values (eg params.pp) of the puppet modules to be used? The previous (puppet 3

Re: [openstack-dev] Following the new PTI for document build, broken local builds

Excerpts from Monty Taylor's message of 2018-03-23 08:03:22 -0500: > On 03/22/2018 05:43 AM, Stephen Finucane wrote: > > > > That's unfortunate. What we really need is a migration path from the > > 'pbr' way of doing things to something else. I see three possible > > avenues at this point in

Re: [openstack-dev] [tripleo] storyboard evaluation

On Thu, Mar 22, 2018 at 12:11 PM, Kendall Nelson wrote: > Sounds like we have fungi set to run the migration of tripleO bugs with > the 'ui' tag for tomorrow after he gets done with the ironic migration. So > excited to have you guys start moving over! > Cool, please let

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 3/21/2018 6:34 AM, 李杰 wrote: So what should we do then about rebuild the volume backed server?Until the cinder could re-image a volume? I've added the spec to the 'stuck reviews' section of the nova meeting agenda so it can at least get some discussion there next week.

Re: [openstack-dev] [nova] EC2 cleanup ?

On 3/22/2018 10:30 PM, Chen CH Ji wrote: seems we have a EC2 implementation in api layer and deprecated since Mitaka, maybe eligible to be removed this cycle? That is easier said than done. There have been a couple of related attempts in the past: https://review.openstack.org/#/c/266425/

Re: [openstack-dev] [nova] about rebuild instance booted from volume

On 3/22/2018 10:47 PM, 李杰 wrote:             This is the spec about  rebuild a instance booted from volume, anyone who is interested in       booted from volume can help to review this. Any suggestion is welcome.Thank you very much!       The link is here.       Re:the rebuild

[openstack-dev] [mistral] [ptl] PTL vacation from March 26 - March 30

I'll be out for the dates in the subject, so all of next week. Renat Akhmerov (rakhmerov on IRC) will be standing in for anything that comes up. Cheers, Dougal __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [nova] [placement] placement update 18-12

Another week, another pile of code and specs to write and review. This week will be a "contract" style update: No new links to code and specs in the listings sections. Next week will be an "expand", when there will be. Perhaps this can help make sure that in progress stuff doesn't get lost in

Re: [openstack-dev] [bifrost][helm][OSA][barbican] Switching from fedora-26 to fedora-27

The failing tests have been addressed in a dependent patch. As soon as that patch merges, we'll merge your patch. Ade On Wed, 2018-03-14 at 18:36 -0400, Paul Belanger wrote: > On Wed, Mar 14, 2018 at 04:44:07PM -0400, Paul Belanger wrote: > > On Wed, Mar 14, 2018 at 03:20:40PM -0400, Paul

Re: [openstack-dev] [nova] Does Cell v2 support for muti-cell deployment in Pike?

> Does Cell v2 support for multi-cell deployment in pike? Is there any > good document about the deployment? In the release notes of Pike: https://docs.openstack.org/releasenotes/nova/pike.html is this under 16.0.0 Prelude: Nova now supports a Cells v2 multi-cell deployment. The default

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On 03/22/2018 05:43 AM, Stephen Finucane wrote: On Wed, 2018-03-21 at 09:57 -0500, Sean McGinnis wrote: On Wed, Mar 21, 2018 at 10:49:02AM +, Stephen Finucane wrote: tl;dr: Make sure you stop using pbr's autodoc feature before converting them to the new PTI for docs. [snip] I've gone

Re: [openstack-dev] Following the new PTI for document build, broken local builds

On 03/22/2018 04:39 PM, Sean McGinnis wrote: That's unfortunate. What we really need is a migration path from the 'pbr' way of doing things to something else. I see three possible avenues at this point in time: 1. Start using 'sphinx.ext.autosummary'. Apparently this can do similar

Re: [openstack-dev] [sdk] git repo rename and storyboard migration

As we talked in #opensatck-sdks channel yesterday, I can help storyboard migration on OSC bugs. Dean and Monty looks fine with the migration. We can migrate OSC bugs to storyboard along with openstack SDK storyboard migration. Thanks, Akihiro 2018-03-23 1:28 GMT+09:00 Kendall Nelson

Re: [openstack-dev] [nova] Refused to connect port 8774.

I would check for: 1) Telnet to controller on port 8774. 2) check if controller service is listening on 8774 Sent from my iPhone > On 23-Mar-2018, at 1:07 PM, __ mango. <935540...@qq.com> wrote: > > > I run the openstack compute service list with the following error: > > # openstack compute

[openstack-dev] [tc] Technical Committee Status update, March 23rd

Hi! This is the weekly summary of Technical Committee initiatives. You can find the full list of currently-considered changes at: https://wiki.openstack.org/wiki/Technical_Committee_Tracker We also track TC objectives for the cycle using StoryBoard at:

[openstack-dev] [nova] Refused to connect port 8774.

I run the openstack compute service list with the following error: # openstack compute service list Unable to establish connection to http://controller:8774/v2.1/os-services: HTTPConnectionPool(host='controller', port=8774): Max retries exceeded with url: /v2.1/os-services (Caused by