[openstack-dev] [Freezer] Freezer support relational db and osbrick

Hi,Saad Zaher: 1) Implementing Sqlalchemy driver for freezer-api: At present, there is part 1 function in implementing Sqlalchemy driver for freezer-api in https://review.openstack.org/#/c/539077/. Is there part 2 function? If you have an uncommitted patches, can you share it? I'd like

[openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration

*TL;DR* *How about a forum in Berlin for discussing autoscaling integration (as a long-term goal) in OpenStack?* Hi all, as we start to discuss how can we join develop from Heat and Senlin as we originally planned when we decided to fork Senlin from Heat long time ago. IMO the biggest issues we

Re: [openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

On Tue, 18 Sep 2018 09:33:30 +0900 Alex Xu wrote > That only means after 599276 we only have servers API and os-instance-action > API stopped accepting the undefined query parameter. > What I'm thinking about is checking all the APIs, add json-query-param > checking with

Re: [openstack-dev] GUI for Swift object storage

All GUI tools are non open source...need to pay like cyberduck etc. Looking for open source GUI for Swift API access. On Tue, 18 Sep 2018, 06:41 John Dickinson, wrote: > That's a great question. > > A quick google search shows a few like Swift Explorer, Cyberduck, and > Gladinet. But since

Re: [openstack-dev] [Openstack-operators] [tc]Global Reachout Proposal

On Sat, 15 Sep 2018 02:49:40 +0900 Zhipeng Huang wrote > Hi all, > Follow up the diversity discussion we had in the tc session this morning > [0], I've proposed a resolution on facilitating technical community in large > to engage in global reachout for OpenStack more

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Tue, Sep 18, 2018 at 8:06 AM Jeremy Stanley wrote: > This seems to completely miss the reasons I personally reject such > platforms. I don't use proprietary tools or services for interacting > with our community, I avoid relying on products from companies which > attempt to track or share my

Re: [openstack-dev] [Openstack-sigs] Open letter/request to TC candidates (and existing elected officials)

Hope you all safely travel back to home now. Here is the summarize from some discussions (as much as I can trigger or attend) in PTG for SIGs/WGs expose and some idea for action, http://lists.openstack.org/pipermail/openstack-dev/2018-September/134689.html I also like the idea to at least expose

Re: [openstack-dev] GUI for Swift object storage

That's a great question. A quick google search shows a few like Swift Explorer, Cyberduck, and Gladinet. But since Swift supports the S3 API (check with your cluster operator to see if this is enabled, or examine the results of a `GET /info` request), you can use any available S3 GUI client

Re: [openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

That only means after 599276 we only have servers API and os-instance-action API stopped accepting the undefined query parameter. What I'm thinking about is checking all the APIs, add json-query-param checking with additionalProperties=True if the API don't have yet. And using another

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On 2018-09-18 07:27:26 +0800 (+0800), Zhipeng Huang wrote: [...] > On another side note, there has not been a (maybe I missed) good > "no" vote message I was looking for. > > A good quality "no" message could something like this in my > opinion (and this is just one of many possibilities): > >

[openstack-dev] GUI for Swift object storage

Hi - is there any GUI (open source) available for Swift objects storage? Thanks Swa __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

Thanks Anne :) On another side note, there has not been a (maybe I missed) good "no" vote message I was looking for. A good quality "no" message could something like this in my opinion (and this is just one of many possibilities): "Thanks for invitation but no I would not like to use social

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Mon, Sep 17, 2018 at 7:06 PM Anne Bertucio wrote: > I though I remember someone (annabelleB?) saying there were known issues > (technical or otherwise) regarding the official channels spun up by the > Foundation. > > > Two separate issues that perhaps got mashed together :) > > Unofficial

Re: [openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

On 9/17/2018 3:06 PM, Jay Pipes wrote: My vote would be just change additionalProperties to False in the 599276 patch and be done with it. Well, it would be on a microversion boundary so the user would be opting into this stricter validation, but that's the point of microversions. So my

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

> I though I remember someone (annabelleB?) saying there were known issues > (technical or otherwise) regarding the official channels spun up by the > Foundation. Two separate issues that perhaps got mashed together :) Unofficial WeChat channels are limited to ~500 participants and are

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

Would like to see some updates on the foundation's official wechat group up :) On the other note, I would like to point out that this email is merely asking who would be interested. The question about "dividing teams" and such is addressed in https://review.openstack.org/602697 . On Tue, Sep

Re: [openstack-dev] [tc] notes from stein ptg meetings of the technical committee

Excerpts from Jay Pipes's message of 2018-09-17 17:07:43 -0400: > On 09/17/2018 04:50 PM, Doug Hellmann wrote: > > Excerpts from Zane Bitter's message of 2018-09-17 16:12:30 -0400: > >> On 17/09/18 3:06 PM, Jay Pipes wrote: > >>> On 09/17/2018 01:31 PM, Doug Hellmann wrote: > New Project

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Mon, Sep 17, 2018 at 1:42 PM Mohammed Naser wrote: > Hi, > > On that note, is there any way to get an 'invite' onto those channels? > > Any information about the foundation side of things about the > 'official' channels? > I actually have a question about this as well. During the TC

Re: [openstack-dev] [tc] notes from stein ptg meetings of the technical committee

On 09/17/2018 04:50 PM, Doug Hellmann wrote: Excerpts from Zane Bitter's message of 2018-09-17 16:12:30 -0400: On 17/09/18 3:06 PM, Jay Pipes wrote: On 09/17/2018 01:31 PM, Doug Hellmann wrote: New Project Application Process === We wrapped up Sunday with a

Re: [openstack-dev] [tc] notes from stein ptg meetings of the technical committee

Excerpts from Zane Bitter's message of 2018-09-17 16:12:30 -0400: > On 17/09/18 3:06 PM, Jay Pipes wrote: > > On 09/17/2018 01:31 PM, Doug Hellmann wrote: > >> New Project Application Process > >> === > >> > >> We wrapped up Sunday with a discussion of of our process

Re: [openstack-dev] [tc] notes from stein ptg meetings of the technical committee

On 17/09/18 3:06 PM, Jay Pipes wrote: On 09/17/2018 01:31 PM, Doug Hellmann wrote: New Project Application Process === We wrapped up Sunday with a discussion of of our process for reviewing new project applications. Zane and Chris in particular felt the process for

Re: [openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

On 09/17/2018 03:28 PM, Matt Riedemann wrote: This is a question from a change [1] which adds a new changes-before filter to the servers, os-instance-actions and os-migrations APIs. For context, the os-instance-actions API stopped accepting undefined query parameters in 2.58 when we added

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

Hi, On that note, is there any way to get an 'invite' onto those channels? Any information about the foundation side of things about the 'official' channels? Thanks, Mohammed On Mon, Sep 17, 2018 at 3:28 PM Samuel Cassiba wrote: > > On Mon, Sep 17, 2018 at 6:58 AM Sylvain Bauza wrote: > > > >

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On Mon, Sep 17, 2018 at 6:58 AM Sylvain Bauza wrote: > > > > Le lun. 17 sept. 2018 à 15:32, Jeremy Stanley a écrit : >> >> On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote: >> [...] >> > - What is the problem joining Wechat will solve (keeping in mind the >> > language barrier)?

[openstack-dev] [nova] When can/should we change additionalProperties=False in GET /servers(/detail)?

This is a question from a change [1] which adds a new changes-before filter to the servers, os-instance-actions and os-migrations APIs. For context, the os-instance-actions API stopped accepting undefined query parameters in 2.58 when we added paging support. The os-migrations API stopped

Re: [openstack-dev] [tc] notes from stein ptg meetings of the technical committee

On 09/17/2018 01:31 PM, Doug Hellmann wrote: New Project Application Process === We wrapped up Sunday with a discussion of of our process for reviewing new project applications. Zane and Chris in particular felt the process for Adjutant was too painful for the

Re: [openstack-dev] [goals][python3] mixed versions?

Excerpts from Ken Giusti's message of 2018-09-17 13:18:28 -0400: > On Thu, Sep 13, 2018 at 7:39 PM Doug Hellmann wrote: > > Excerpts from Jim Rollenhagen's message of 2018-09-13 12:08:08 -0600: [snip] > > > A specific example brought up in the ironic room was the way we encode > > > exceptions

[openstack-dev] [tc] notes from stein ptg meetings of the technical committee

The TC held meetings on 2 days at the Stein PTG in Denver. On Sunday 9 September, we met for a few hours in the afternoon to discuss introspective topics. On Friday 14 September, we met for a full day to discuss community topics. Below is a summary of my notes. Please let me know if I omitted or

Re: [openstack-dev] [goals][python3] mixed versions?

On Thu, Sep 13, 2018 at 7:39 PM Doug Hellmann wrote: > Excerpts from Jim Rollenhagen's message of 2018-09-13 12:08:08 -0600: > > On Wed, Sep 12, 2018 at 2:28 PM, Doug Hellmann > > wrote: > > > > > Excerpts from Doug Hellmann's message of 2018-09-12 12:04:02 -0600: > > > > Excerpts from Clark

Re: [openstack-dev] [senlin][stable] Nominating chenyb4 to Senlin Stable Maintainers Team

Voting has concluded. Welcome chenyb4 to the Senlin stable review team. On Thu, Sep 13, 2018 at 10:50 PM Qiming Teng wrote: > > +2 from me. > > Thanks. > - Qiming > > On Mon, Sep 10, 2018 at 09:56:10AM -0700, Duc Truong wrote: > > Hi Senlin Stable Team, > > > > I would like to nominate Yuanbin

Re: [openstack-dev] [senlin] Nominations to Senlin Core Team

Voting has concluded. Welcome Jude and Erik to the Senlin Core team. On Thu, Sep 13, 2018 at 12:14 AM x Lyn wrote: > > +1 to both, looking forward to their future contribution. > > > On Sep 11, 2018, at 12:59 AM, Duc Truong wrote: > > > > Hi Senlin Core Team, > > > > I would like to nominate 2

[openstack-dev] Forum Topic Submission Period

Hello Everyone! The Forum Topic Submission session started September 12 and will run through September 26th. Now is the time to wrangle the topics you gathered during your Brainstorming Phase and start pushing forum topics through. Don't rely only on a PTL to make the agenda... step on up

[openstack-dev] [keystone] Rocky Retrospective

This is typically something we do in-person during the PTG, but due to weather and travel approval we didn't have great representation last week. That said, let's try to do an asynchronous retrospective to gather feedback regarding the last cycle. Afterwords we can try and meet to go through

Re: [openstack-dev] [cinder][infra] Remove driverfixes/ocata branch

On Mon, Sep 17, 2018, at 8:53 AM, Jay S Bryant wrote: > > > On 9/17/2018 10:46 AM, Sean McGinnis wrote: > >>> Plan > >>> > >>> We would now like to have the driverfixes/ocata branch deleted so there > >>> is no > >>> confusion about where backports should go and we don't accidentally get

Re: [openstack-dev] [cinder][infra] Remove driverfixes/ocata branch

On 9/17/2018 10:46 AM, Sean McGinnis wrote: Plan We would now like to have the driverfixes/ocata branch deleted so there is no confusion about where backports should go and we don't accidentally get these out of sync again. Infra team, please delete this branch or let me know if there is

Re: [openstack-dev] [TripleO] Regarding dropping Ocata related jobs from TripleO

Hi, >From the upgrades/updates point of view it should be ok dropping the Ocata jobs. The only one covering Ocata to Pike upgrade in upstream CI is running in RDO cloud as a non voting one, and it is failing at the moment. Thanks, Jose Luis On Fri, Sep 14, 2018 at 6:33 PM Alex Schultz wrote:

Re: [openstack-dev] [cinder][infra] Remove driverfixes/ocata branch

> > > > Plan > > > > We would now like to have the driverfixes/ocata branch deleted so there is > > no > > confusion about where backports should go and we don't accidentally get > > these > > out of sync again. > > > > Infra team, please delete this branch or let me know if there is a

Re: [openstack-dev] [cinder][infra] Remove driverfixes/ocata branch

On Mon, Sep 17, 2018, at 8:00 AM, Sean McGinnis wrote: > Hello Cinder and Infra teams. Cinder needs some help from infra or some > pointers on how to proceed. > > tl;dr - The openstack/cinder repo had a driverfixes/ocata branch created for > fixes that no longer met the more restrictive phase II

[openstack-dev] [cinder][infra] Remove driverfixes/ocata branch

Hello Cinder and Infra teams. Cinder needs some help from infra or some pointers on how to proceed. tl;dr - The openstack/cinder repo had a driverfixes/ocata branch created for fixes that no longer met the more restrictive phase II stable policy criteria. Extended maintenance has changed that and

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

Le lun. 17 sept. 2018 à 15:32, Jeremy Stanley a écrit : > On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote: > [...] > > - What is the problem joining Wechat will solve (keeping in mind the > > language barrier)? > > As I understand it, the suggestion is that mere presence of

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

> > > I also have technical questions about 'wechat' (like how do you > > use it without a smartphone?) and the relevance of tools we > > currently use, but this will open Pandora's box, and I'd rather > > not spend my energy on closing that box right now :D > > Not that I was planning on

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

Thanks Giblet, Will review this afternoon. Best, -jay On 09/17/2018 09:10 AM, Balázs Gibizer wrote: Hi, Reworked and rebased the series based on this thread. The series starts here https://review.openstack.org/#/c/591597 Cheers, gibi

Re: [openstack-dev] [election][tc]Question for candidates about global reachout

On 2018-09-16 14:14:41 +0200 (+0200), Jean-philippe Evrard wrote: [...] > - What is the problem joining Wechat will solve (keeping in mind the > language barrier)? As I understand it, the suggestion is that mere presence of project leadership in venues where this emerging subset of our community

[openstack-dev] [neutron] bug deputy report week Sep 10 - 12

Hi, I was the bug deputy for neutron last week. The last week was really quiet, but all of them are gate failures and need attentions. grenade-dvr-multinode job fails https://bugs.launchpad.net/neutron/+bug/1791989 This continuously happens last week with high failure rate.

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

Hi, Reworked and rebased the series based on this thread. The series starts here https://review.openstack.org/#/c/591597 Cheers, gibi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] About microversion setting to enable nested resource provider

On Mon, Sep 17, 2018 at 6:43 AM, Jay Pipes wrote: > On 09/16/2018 09:28 PM, Naichuan Sun wrote: > >> Hi, Sylvain, >> >> In truth I’m worrying about the old root rp which include the vgpu >> inventory. There is no field in the inventory which can display which >> GPU/GPUG it belong to, right?

Re: [openstack-dev] [puppet] [placement]

On Mon, Sep 17, 2018 at 5:29 AM Lee Yarwood wrote: > FWIW I've also started work on the RDO packaging front [1] and would be > happy to help with this puppet extraction. > Good to know, thanks. Once we have the repo in place, here is a plan proposal: * Populate the repo with cookiecutter &

Re: [openstack-dev] About microversion setting to enable nested resource provider

On 09/16/2018 09:28 PM, Naichuan Sun wrote: Hi, Sylvain, In truth I’m worrying about the old root rp which include the vgpu inventory. There is no field in the inventory which can display which GPU/GPUG it belong to, right? Anyway,  will discuss it after you come back. As Sylvain mentions

Re: [openstack-dev] [kolla] Committing proprietary plugins to OpenStack

Hi Shyam, We offer methods [0] to allow users add their plugins during build time through template overrides. This allows extends dockerfiles with custom content as may be your use case. Also we offer a method to add an external directory into the buildable list of Dockerfiles with

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possibledeprecation of Nova's legacy notification interface

Hi gibi, Thank for the info. Searchlight team is working on a patch to support the versioned Nova. Hopefully, it will be released in Stein-1. Bests, *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com | *W:* *www.edlab.xyz *

Re: [openstack-dev] [nova][searchlight][designate][telemetry][mistral][blazar][watcher][masakari]Possibledeprecation of Nova's legacy notification interface

Hi, On the Stein PTG the nova team agreed to deprecate the legacy, unversioned notification interface of nova. We also agreed that we will not try to remove the legacy notification sending from the code any time soon. So this deprecation means the following: * by default configuration nova

Re: [openstack-dev] [puppet] [placement]

Sounds great, thanks for pushing this Emilien! Best regards Tobias On 09/15/2018 07:48 PM, Emilien Macchi wrote: I'm currently taking care of creating puppet-placement: https://review.openstack.org/#/c/602870/ https://review.openstack.org/#/c/602871/ https://review.openstack.org/#/c/602869/

Re: [openstack-dev] [puppet] [placement]

On 15-09-18 11:42:37, Emilien Macchi wrote: > I'm currently taking care of creating puppet-placement: > https://review.openstack.org/#/c/602870/ > https://review.openstack.org/#/c/602871/ > https://review.openstack.org/#/c/602869/ > > Once these merge, we'll use cookiecutter, and move things from