Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

On 2018-08-16 07:38, Tony Breeds wrote: > On Thu, Aug 16, 2018 at 06:27:39AM +0200, Andreas Jaeger wrote: > >> Ocata should be retired by now ;) Let's drop it... > > *cough* extended maintenance *cough* ;P Ah, forget about that. > So we don't need the Ocata docs to be rebuilt with this

[openstack-dev] [docs][nova] about update flavor

Hi,all I find it is supported that we can update the flavor name, VCPUs, RAM, root disk, ephemeral disk and so on in doc.openstack.org[1].But only can change the flavor propertity in fact.Is the document wrong?Can you tell me more about this ?Thank you very much.

[openstack-dev] [docs] Retire rst2bash

The rst2bash repo is dead and unused. It was created to help us with Install Guide testing - and this implementation was not finished and the Install Guide looks completely different now. I propose to retire it, see https://review.openstack.org/#/q/topic:retire-rst2bash for changes, Andreas --

[openstack-dev] [Nova] A multi-cell instance-list performance test

Hi, Nova As the Cells v2 architecture is getting mature, and CERN used it and seems worked well, *Huawei *is also willing to consider using this in our Public Cloud deployments. As we still have concerns about the performance when doing multi-cell listing, recently *Yikun Jiang* and I have done a

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On Wed, Aug 15, 2018 at 10:48 PM, Jay Pipes wrote: > On 08/15/2018 04:01 PM, Emilien Macchi wrote: >> >> On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi > > wrote: >> >> More seriously here: there is an ongoing effort to converge the >> tools around

Re: [openstack-dev] [docs][nova] about update flavor

I mean this https://review.openstack.org/#/c/491442/ and the related ML http://lists.openstack.org/pipermail/openstack-dev/2017-August/120540.html On Thu, Aug 16, 2018 at 4:30 PM Rambo wrote: > Sorry,I don't understand what has been removed,the docs about the update > the flavor's

Re: [openstack-dev] [Nova] A multi-cell instance-list performance test

Some more information: *1. How did we record the time when listing?* you can see all our changes in: http://paste.openstack.org/show/728162/ Total cost: L26 Construct view: L43 Data gather per cell cost: L152 Data gather all cells cost: L174 Merge Sort cost: L198 *2. Why it is not parallel in

Re: [openstack-dev] [docs][nova] about update flavor

We only allow update flavor descriptions(added in microversion 2.55) in Nova and what the horizon did was just delete the old one and create a new one, and I think it has been removed in last year. On Thu, Aug 16, 2018 at 3:19 PM Rambo wrote: > Hi,all > > I find it is supported that we

[openstack-dev] QA work

Hi Everybody, Does anybody wants some QA/testing work to be done on their modules? -Regards, Ameet __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [docs][nova] about update flavor

Sorry,I don't understand what has been removed,the docs about the update the flavor's cpu?Otherwise,why we don't consider to add the function that we can update the flavor's cpu? -- Original -- From: "Zhenyu Zheng"; Date: 2018年8月16日(星期四) 下午3:56 To: "OpenStack

[openstack-dev] [release][qa] QA Rocky release status

Hi All, QA has lot of sub-projects and this mail is to track their release status for Rocky cycle. I will be on vacation from coming Monday for next 2 weeks (visiting India) but will be online to complete the below IN-PROGRESS items and update the status here. IN-PROGRESS: 1.

[openstack-dev] [Openstack-operators][nova] ask deployment question

Hi,all I have some questions about deploy the large scale openstack cloud.Such as 1.Only in one region situation,How many physical machines are the biggest deployment scale in our community? Can you tell me more about these combined with own practice? Would you give me

[openstack-dev] [publiccloud-wg] Meeting this afternoon for Public Cloud WG

Hi folks, Time for a new meeting for the Public Cloud WG. Agenda draft can be found at https://etherpad.openstack.org/p/publiccloud-wg, feel free to add items to that list. See you all later this afternoon at IRC 1400 UTC in #openstack-publiccloud Cheers, Tobias -- Tobias Rydberg Senior

Re: [openstack-dev] [freezer][tc] removing freezer from governance

Hi Rog, If your company uses Freezer in production clouds, maybe you can help the community with supporting it? I know, that it could be a long and not easy decision but it's the only way you can be sure that the project is alive. Regards, Ivan Kolodyazhny, http://blog.e0ne.info/ On Sat, Aug

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 15.8.2018 11:32, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon, precisely the lack of a socket allowing to send commands and get a "computer formatted output" (like JSON

[openstack-dev] [tripleo] network isolation!!! do we still need to configure VLAN , CIDR, ... in network-environment.yaml

Hi, In ocata we used network environment file to configure network parameters as following InternalApiNetCidr: '172.16.2.0/24' TenantNetCidr: '172.16.0.0/24' ExternalNetCidr: '192.168.204.0/24' # Customize the VLAN IDs to match the local environment InternalApiNetworkVlanID: 711

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Andreas Jaeger's message of 2018-08-16 08:42:22 +0200: > On 2018-08-16 07:38, Tony Breeds wrote: > > On Thu, Aug 16, 2018 at 06:27:39AM +0200, Andreas Jaeger wrote: > > > >> Ocata should be retired by now ;) Let's drop it... > > > > *cough* extended maintenance *cough* ;P > > Ah,

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 16.8.2018 10:38, Steven Hardy wrote: On Wed, Aug 15, 2018 at 10:48 PM, Jay Pipes wrote: On 08/15/2018 04:01 PM, Emilien Macchi wrote: On Wed, Aug 15, 2018 at 5:31 PM Emilien Macchi mailto:emil...@redhat.com>> wrote: More seriously here: there is an ongoing effort to converge the

[openstack-dev] [sahara] No meeting today

Hi folks, since a couple of our core reviewers are on PTO today we have decided not to host a meeting today. If you have any questions just ping us at #openstack-sahara Thanks, -- TELLES NOBREGA SOFTWARE ENGINEER Red Hat Brasil Av. Brg. Faria Lima, 3900 - 8º

[openstack-dev] [nova] how nova should behave when placement returns consumer generation conflict

Hi, tl;dr: To properly use consumer generation (placement 1.28) in Nova we need to decide how to handle consumer generation conflict from Nova perspective: a) Nova reads the current consumer_generation before the allocation update operation and use that generation in the allocation update

Re: [openstack-dev] [infra][horizon][osc] ClientImpact tag automation

Hi all, Auto-created bugs could help in this effort. Honestly, nobody can say will it work or not before we try it. >From a Horizon's perspective, we need to have some solution which helps us to know about new features that would be good to add them to UI in the future. We started with an

[openstack-dev] [release] Release countdown for week R-1, August 20-24

The end is near! Development Focus - Teams should be working on release critical bugs in preparation of the final release candidate deadline this Thursday the 23rd. Teams attending the PTG should also be preparing for those discussions and capturing information in the etherpads:

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 16.8.2018 07:39, Cédric Jeanneret wrote: On 08/16/2018 12:10 AM, Jason E. Rist wrote: On 08/15/2018 03:32 AM, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon,

Re: [openstack-dev] [tripleo] CI is blocked

On Wed, Aug 15, 2018 at 10:13 PM Wesley Hayutin wrote: > On Wed, Aug 15, 2018 at 7:13 PM Alex Schultz wrote: > >> Please do not approve or recheck anything until further notice. We've >> got a few issues that have basically broken all the jobs. >> >>

Re: [openstack-dev] [tripleo][Edge][FEMDC] Edge clouds and controlplane updates

On Tue, Aug 14, 2018 at 9:20 AM Bogdan Dobrelya wrote: > On 8/13/18 9:47 PM, Giulio Fidente wrote: > > Hello, > > > > I'd like to get some feedback regarding the remaining > > work for the split controlplane spec implementation [1] > > > > Specifically, while for some services like nova-compute

[openstack-dev] User Committee Nominations Closing Soon!

As I write this, there are just over 12 hours left to get in your nominations for the OpenStack User Committee. Nominations close at August 17, 05:59 UTC. If you are an AUC and thinking about running what's stopping you? If you know of someone who would make a great committee member nominate

Re: [openstack-dev] [nova] how nova should behave when placement returns consumer generation conflict

Thanks for this, gibi. TL;DR: a). I didn't look, but I'm pretty sure we're not caching allocations in the report client. Today, nobody outside of nova (specifically the resource tracker via the report client) is supposed to be mucking with instance allocations, right? And given the global lock

Re: [openstack-dev] [oslo] Proposing Zane Bitter as oslo.service core

On 15/08/18 16:34, Ben Nemec wrote: Since there were no objections, I've added Zane to the oslo.service core team.  Thanks and welcome, Zane! Thanks team! I'll try not to mess it up :) On 08/03/2018 11:58 AM, Ben Nemec wrote: Hi, Zane has been doing some good work in oslo.service recently

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

Greetings OpenStack community, Another cozy meeting today, as conferences and summer holidays reduced our attendees. We mainly focused on the agenda [7] for the upcoming Denver PTG [8]. One item we added was consideration of a spec for common healthcheck middleware across projects [9]. This

[openstack-dev] [nova] nova-specs is open for Stein

Hey all, Just wanted to give a quick heads up that the nova-specs repo [1] is now open for Stein spec proposals. Here's a link to the docs on the spec process: https://specs.openstack.org/openstack/nova-specs/readme.html Cheers, -melanie [1] https://github.com/openstack/nova-specs

[openstack-dev] [community][Rocky] Save the Date: Community Meeting: Rocky + project updates

Hi all, Save the date for an OpenStack community meeting on August 30 at 3pm UTC. This is the evolution of the “Marketing Community Release Preview” meeting that we’ve had each cycle. While that meeting has always been open to all, we wanted to expand the topics and encourage anyone who was

Re: [openstack-dev] [puppet] migrating to storyboard

Hey :) I created all the puppet openstack repos in the storyboard-dev envrionment and made a project group[1]. I am struggling a bit with finding all of your launchpad projects to perform the migrations through, can you share a list of all of them? -Kendall (diablo_rojo) [1]

Re: [openstack-dev] [puppet] migrating to storyboard

Hey, Well, the attachments are one of the things holding us up along with reduced participation in the project and a number of other challenges.  Getting the time to prepare for the move has been difficult. I am planning to take some time before the PTG to look at how Ironic has been using

Re: [openstack-dev] [puppet] migrating to storyboard

We can definitely add that to our PTG discussion agenda if you want to come by with feedback. Octavia wrote up and Etherpad and passed that along to us. Either way works. Once the PTG bot is ready to go I plan to reserve a day or part of a day dedicated to StoryBoard. -Kendall On Thu, Aug 16,

Re: [openstack-dev] [puppet] migrating to storyboard

Hello :) On Thu, Aug 16, 2018 at 12:47 PM Jay S Bryant wrote: > Hey, > > Well, the attachments are one of the things holding us up along with > reduced participation in the project and a number of other challenges. > Getting the time to prepare for the move has been difficult. > > I wouldn't

[openstack-dev] [all] Personal tool patterns in .gitignore cookiecutter

In response to some recent but misguided proposals from well-meaning contributors in various projects, I've submitted a change[*] for the openstack-dev/cookiecutter .gitignore template inserting a comment which recommends against including patterns related to personal choices of tooling (arbitrary

[openstack-dev] [all][tc] Technical Vision statement: feedback sought

The TC has undertaken to attempt to write a technical vision statement for OpenStack that documents the community's consensus on what we're trying to build. To date the only thing we've had to guide us is the mission statement[1], which is exactly one sentence long and uses undefined terms

Re: [openstack-dev] [barbican][oslo][release] FFE request for castellan

The backport has merged and I've proposed the release here: https://review.openstack.org/592746 On 08/15/2018 11:58 AM, Ade Lee wrote: Done. https://review.openstack.org/#/c/592154/ Thanks, Ade On Wed, 2018-08-15 at 09:20 -0500, Ben Nemec wrote: On 08/14/2018 01:56 PM, Sean McGinnis

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

On 2018-08-17 06:56:11 +1000 (+1000), Tony Breeds wrote: [...] > How terrible would it be to branch openstackdocstheme and backport > the fix without the pbr changes? It might also be possible, > though I'm not sure how we'd land it, to branch (stable/ocata) > openstackdocstheme today and just

[openstack-dev] [tripleo] deployements fails when using custom nic config

Hi, I'm using the attached file for controller nic configuration and I'm referencing to it as following resource_registry: # Network Interface templates to use (these files must exist). You can # override these by including one of the net-*.yaml environment files, # such as

Re: [openstack-dev] [puppet] migrating to storyboard

Hey :) Yes, I know attachments are important to a few projects. They are on our todo list and we plan to talk about how to implement them at the upcoming PTG[1]. Unfortunately, we have had other things that are taking priority over attachments. We would really love to migrate you all, but if

Re: [openstack-dev] [all] Personal tool patterns in .gitignore cookiecutter

On Thu, Aug 16, 2018 at 06:24:22PM +, Jeremy Stanley wrote: > In response to some recent but misguided proposals from well-meaning > contributors in various projects, I've submitted a change[*] for the > openstack-dev/cookiecutter .gitignore template inserting a comment > which recommends

Re: [openstack-dev] [Nova] A multi-cell instance-list performance test

> yes, the DB query was in serial, after some investigation, it seems that we > are unable to perform eventlet.mockey_patch in uWSGI mode, so > Yikun made this fix: > > https://review.openstack.org/#/c/592285/ Cool, good catch :) > > After making this change, we test again, and we got this

Re: [openstack-dev] [puppet] migrating to storyboard

Is there any plan to have a session where the current and future users of storyboard can get together and discuss how it's going? On 08/16/2018 02:47 PM, Jay S Bryant wrote: Hey, Well, the attachments are one of the things holding us up along with reduced participation in the project and a

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

On Thu, Aug 16, 2018 at 10:45:32AM -0400, Doug Hellmann wrote: > Is there any reason we can't uncap pbr, at least within the CI jobs? It might work for the docs builds but jumping a major version of pbr, which if I recall caused problems ate the time (hence the lower-bound) for all octata

Re: [openstack-dev] [requirements][release][docs] FFE for openstackdocstheme 1.21.2

Excerpts from Tony Breeds's message of 2018-08-17 06:56:11 +1000: > On Thu, Aug 16, 2018 at 10:45:32AM -0400, Doug Hellmann wrote: > > > Is there any reason we can't uncap pbr, at least within the CI jobs? > > It might work for the docs builds but jumping a major version of pbr, > which if I

[openstack-dev] [nova][vmware] need help triaging a vmware driver bug

Hello VMware peeps, I've been trying to triage a bug in New status for the VMware driver without success: https://bugs.launchpad.net/nova/+bug/1744182 - can not create instance when using vmware nova driver I tend to think the problem is not related to nova because the instance create

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 15/08/18 21:32, Cédric Jeanneret wrote: Dear Community, As you may know, a move toward Podman as replacement of Docker is starting. One of the issues with podman is the lack of daemon, precisely the lack of a socket allowing to send commands and get a "computer formatted output" (like

Re: [openstack-dev] [Nova] A multi-cell instance-list performance test

Hi, Thanks alot for the reply, for your question #2, we did tests with two kinds of deployments: 1. There is only 1 DB with all 10 cells(also cell0) and it is on the same server with the API; 2. We took 5 of the DBs to another machine on the same rack to test out if it matters, and it turns out

Re: [openstack-dev] [tempest][qa][congress] help with tempest plugin jobs against stable/queens

On Tue, Aug 14, 2018 at 9:34 PM, Ghanshyam Mann wrote: > On Wed, 15 Aug 2018 09:37:18 +0900 Eric K > wrote > > I'm adding jobs [1] to the tempest plugin to run tests against > > congress stable/queens. The job output seems to show stable/queens > > getting checked out [2], but I

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

>> On my side, I would like to push forward the integration of varlink in >> TripleO deployed containers, especially since it will allow the >> following: >> # proper interface with Paunch (via python link) > > "integration of varlink in TripleO deployed containers" sounds like we'd > need to

Re: [openstack-dev] [TripleO] podman: varlink interface for nice API calls

On 08/17/2018 12:25 AM, Steve Baker wrote: > > > On 15/08/18 21:32, Cédric Jeanneret wrote: >> Dear Community, >> >> As you may know, a move toward Podman as replacement of Docker is starting. >> >> One of the issues with podman is the lack of daemon, precisely the lack >> of a socket allowing

Re: [openstack-dev] [nova] how nova should behave when placement returns consumer generation conflict

reformatted for readabiliy, sorry: Hi, tl;dr: To properly use consumer generation (placement 1.28) in Nova we need to decide how to handle consumer generation conflict from Nova perspective: a) Nova reads the current consumer_generation before the allocation update operation and use that