Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hi Jay, Thanks your reply. As we know, we can automatically generate API Documents, different language of Clients(SDK), cloud tool adapters for OpenStack based on Open API 3.0 Schema. About the other self-defined development for 3rd party developers, based on the Open API 3.0 schema, developers

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Hi Ed Leafe, Thanks your reply. Open API defines a standard interface description for REST APIs. Open API 3.0 can make a description(schema) for current OpenStack REST API. It will not change current OpenStack API. I am not a GraphQL expert. I look up something about GraphQL. In my understanding,

Re: [openstack-dev] [Freezer] Reactivate the team

Hi Geng, We would like to have a team meeting today at 2:00 UTC on #openstack-meeting-alt channel. The purpose is to move Freezer forward. Attendees are you, Saad Zaher (the last PTL), and me. Bests, *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrin...@gmail.com

Re: [openstack-dev] [nova][neutron] numa aware vswitch

Hi, Stephen, Sean It worked as expected. Thanks, -Ruijing -Original Message- From: Stephen Finucane [mailto:sfinu...@redhat.com] Sent: Monday, August 27, 2018 5:37 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [nova][neutron] numa

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Doug Hellmann's message of 2018-08-29 17:49:28 -0400: > Excerpts from Nate Johnston's message of 2018-08-29 17:14:11 -0400: > > On Tue, Aug 28, 2018 at 05:46:09PM -0400, Doug Hellmann wrote: > > > Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300: > > > > On Mon,

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Doug Hellmann's message of 2018-08-29 15:22:56 -0400: > Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400: > > On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote: > > > > > Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400: > > > > Excerpts from

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

On Wed, 29 Aug 2018 13:59:26 +0300, Radoslav Gerganov wrote: On 23.08.2018 23:27, melanie witt wrote: So, I think we could add something to the launchpad bug template to link to a doc that explains tips about reporting VMware related bugs. I suggest linking to a doc because the bug template

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Nate Johnston's message of 2018-08-29 17:14:11 -0400: > On Tue, Aug 28, 2018 at 05:46:09PM -0400, Doug Hellmann wrote: > > Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300: > > > On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann > > > wrote: > > > > > > > > > > >

Re: [openstack-dev] [Openstack-operators] [nova][cinder][neutron] Cross-cell cold migration

On 8/29/2018 3:21 PM, Tim Bell wrote: Sounds like a good topic for PTG/Forum? Yeah it's already on the PTG agenda [1][2]. I started the thread because I wanted to get the ball rolling as early as possible, and with people that won't attend the PTG and/or the Forum, to weigh in on not only

[openstack-dev] [neutron][python3] Neutron and stadium - python 3 community goal changes coming soon

Neutrinos and contributors to stadium projects, As part of the "Run under Python 3 by default" community goal [1] for OpenStack in the Stein cycle, a group of goal champions has assembled and have been programmatically generating changes to help projects with the process of migrating to a python

Re: [openstack-dev] [goal][python3] week 3 update

On Tue, Aug 28, 2018 at 05:46:09PM -0400, Doug Hellmann wrote: > Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300: > > On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann > > wrote: > > > > > > > > If your team is ready to have your zuul settings migrated, please > > > let us

Re: [openstack-dev] [neutron] Rocky PTG retrospective etherpad

Here's the etherpad: https://etherpad.openstack.org/p/neutron-rocky-retrospective On Wed, Aug 29, 2018 at 3:24 PM, Miguel Lavalle wrote: > Dear Neutrinos, > > In preparation for our PTG in Denver, I have started an etherpad to gather > feedback for our retrospective session. Please add your

[openstack-dev] [neutron] Rocky PTG retrospective etherpad

Dear Neutrinos, In preparation for our PTG in Denver, I have started an etherpad to gather feedback for our retrospective session. Please add your comments there Best regards Miguel __ OpenStack Development Mailing List

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Lance Bragstad's message of 2018-08-29 11:21:05 -0500: > The keystone team is ready. Just FYI - there are pre-existing patches > proposed to our repositories, but they weren't initiated by one of the goal > champions [0]. > > I can help work through issues on our end. > > [0] >

Re: [openstack-dev] Stepping down as keystone core

Samuel, Thanks for all the dedication and hard work upstream. I'm relieved that you won't be too far away and that you're still involved with the Outreachy programs. You played an instrumental role in getting keystone involved with that community. As always, we'd be happy to have you back in the

[openstack-dev] Stepping down as keystone core

Hi Stackers! It has been both an honor and privilege to serve this community as a keystone core. I am in a position that does not allow me enough time to devote reviewing code and participating of the development process in keystone. As a consequence, I am stepping down as a core reviewer. A

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400: > On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote: > > > Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400: > > > Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400: > > > > On Mon, Aug 27,

[openstack-dev] Travel Support Deadline Tomorrow

Hi everyone, Reminder that the deadline to apply for Travel Support to the Berlin Summit closes tomorrow, Thursday, August 30 at 11:59pm PT. APPLY HERE The Travel Support Program's aim is to facilitate participation of

Re: [openstack-dev] [goal][python3] week 3 update

On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400: > > Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400: > > > On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann > wrote: > > > > > > > If your team is ready to

Re: [openstack-dev] [Openstack-operators] OpenStack Summit Forum in Berlin: Topic Selection Process

100% correct. Just a random example text that we've been reusing since early 2017. Next time, we will consider lorem ipsum ;) Jim Rollenhagen wrote: On Wed, Aug 29, 2018 at 12:51 PM, Jimmy McArthur > wrote: Examples of typical sessions that make for a great

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

On Wed, Aug 29, 2018 at 1:16 PM Waines, Greg wrote: > Makes sense. > > > > So what is the recommended upstream approach for securely storing user > passwords in keystone ? > Keystone will hash passwords before persisting them in their own table. Encrypted passwords are never stored. > > > Is

Re: [openstack-dev] [kayobe] Kayobe update

Thanks Erik, see you then. Mark On Wed, 29 Aug 2018 at 17:20, Erik McCormick wrote: > Hey Mark, > > Here's the link to the Ops etherpad > > https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018 > > I added a listing for you, and we'll have a schedule out shortly, but > I noted that it

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

Makes sense. So what is the recommended upstream approach for securely storing user passwords in keystone ? Is that what is being described here ? https://docs.openstack.org/keystone/pike/admin/identity-credential-encryption.html Greg. From: Juan Antonio Osorio Robles Reply-To:

Re: [openstack-dev] OpenStack Summit Forum in Berlin: Topic Selection Process

On Wed, Aug 29, 2018 at 12:51 PM, Jimmy McArthur wrote: > Examples of typical sessions that make for a great Forum: > > Strategic, whole-of-community discussions, to think about the big > picture, including beyond just one release cycle and new technologies > > e.g. OpenStack One Platform for

Re: [openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

This is not the case. Barbican requires users and systems that use it to use keystone for authentication. So keystone can't use Barbican for this. Chicken and egg problem. On 08/29/2018 08:08 PM, Waines, Greg wrote: > > My understanding is that Keystone can be configured to use Barbican to >

[openstack-dev] [keystone] [barbican] Keystone's use of Barbican ?

My understanding is that Keystone can be configured to use Barbican to securely store user passwords. Is this true ? If yes, is this the standard / recommended / upstream way to securely store Keystone user passwords ? If yes, I can’t find any descriptions of this is configured ? Can someone

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400: > Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400: > > On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote: > > > > > If your team is ready to have your zuul settings migrated, please > > > let us know by

[openstack-dev] OpenStack Summit Forum in Berlin: Topic Selection Process

Hi all, Welcome to the topic selection process for our Forum in Berlin. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they

Re: [openstack-dev] [goal][python3] week 3 update

On Mon, Aug 27, 2018 at 2:37 PM Doug Hellmann wrote: > This is week 3 of the "Run under Python 3 by default" goal > (https://governance.openstack.org/tc/goals/stein/python3-first.html). > > == What we learned last week == > > We have a few enthusiastic folks who want to contribute to the goal >

Re: [openstack-dev] [kayobe] Kayobe update

Hey Mark, Here's the link to the Ops etherpad https://etherpad.openstack.org/p/ops-meetup-ptg-denver-2018 I added a listing for you, and we'll have a schedule out shortly, but I noted that it should be Tuesday. See you in Denver! Cheers, Erik On Wed, Aug 22, 2018 at 5:01 PM Mark Goddard

[openstack-dev] Aug 30, 1500 UTC: Community Meeting: Come learn what's new in Rocky!

A reminder that there’ll be a community meeting tomorrow August 30, at 1500UTC/8am Pacific, where you can learn about some of the new things in OpenStack Rocky, and get updates on the pilot projects Airship, Kata Containers, StarlingX, and Zuul. We’ll hear from PTLs (Julia Kreger, Ironic;

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

On 8/29/2018 9:31 AM, Naichuan Sun wrote: Thanks, Matt. Should we create a ticket about it? Already done: https://bugs.launchpad.net/nova/+bug/1789654 I'm working on pushing some debug log patches now. -- Thanks, Matt

[openstack-dev] masakari 6.0.0.0rc2 (rocky)

Hello everyone, A new release candidate for masakari for the end of the Rocky cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Thanks, Matt. Should we create a ticket about it? BR. Naichuan Sun -Original Message- From: Matt Riedemann [mailto:mriede...@gmail.com] Sent: Wednesday, August 29, 2018 10:12 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] [placement] XenServer CI failed

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

On 8/29/2018 8:36 AM, Naichuan Sun wrote: Hi, Jay， I have add the configuration and the CI should be OK now. Just interested in the reason:) Thanks. Naichuan Sun zigo is reporting the same thing in the nova channel this morning, this was his inventory for the compute node provider:

Re: [openstack-dev] [goal][python3] week 3 update

Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400: > On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote: > > > If your team is ready to have your zuul settings migrated, please > > let us know by following up to this email. We will start with the > > volunteers, and then work

Re: [openstack-dev] [Freezer] Reactivate the team

On Tue, Aug 28, 2018 at 2:12 PM Trinh Nguyen wrote: > Hi Saad, > > That is the time to migrate Freezer to Storyboard, not the meeting time. :) > *Sorry for my missing understanding * > > Bests, > > > *Trinh Nguyen *| Founder & Chief Architect > > > > *E:*

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Hi, Jay， I have add the configuration and the CI should be OK now. Just interested in the reason :) Thanks. Naichuan Sun -Original Message- From: Jay Pipes [mailto:jaypi...@gmail.com] Sent: Wednesday, August 29, 2018 8:39 PM To: openstack-dev@lists.openstack.org Subject: Re:

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

On Aug 29, 2018, at 1:36 AM, Edison Xiang wrote: > > As we know, Open API 3.0 was released on July, 2017, it is about one year ago. > Open API 3.0 support some new features like anyof, oneof and allof than Open > API 2.0(Swagger 2.0). > Now OpenStack projects do not support Open API. > Also I

Re: [openstack-dev] [neutron] tox-siblings alternative for local testing

On 8/29/18 12:06 AM, Takashi Yamamoto wrote: > is there any preferred solution for this? > i guess the simplest solution is to make an intermediate release of neutron > and publish it on pypi. i wonder if it's acceptable or not. What we've been doing to date is adding tox target(s) to the

Re: [openstack-dev] [goal][python3] week 3 update

On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote: > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. > TripleO team is ready to participate. I'll

Re: [openstack-dev] [goal][python3] goal champion tools

Excerpts from Nguyễn Trí Hải's message of 2018-08-29 12:02:12 +0900: > For dealing with this problem, I turn off all the Timeline events in > Preferences. Nice tip! I didn't realize that was something I could control. Thanks, Doug > > On Wed, Aug 29, 2018 at 6:58 AM Doug Hellmann wrote: > >

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

I think the immediate solution would be to just set cpu_allocation_ratio to 16.0 in the nova.CONF that your CI system is using. Best, -jay On 08/29/2018 05:26 AM, Naichuan Sun wrote: Hi, Eric and Jay, The VCPU/Disk/RAM allocation ratio are set to 0.0 by default, and resource tracker would

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

On 08/29/2018 02:36 AM, Edison Xiang wrote: Based on Open API 3.0, it can bring lots of benefits for OpenStack Community and does not impact the current features the Community has. 3rd party developers can also do some self-defined development. Hi Edison, Would you mind expanding on what

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

On 23.08.2018 23:27, melanie witt wrote: So, I think we could add something to the launchpad bug template to link to a doc that explains tips about reporting VMware related bugs. I suggest linking to a doc because the bug template is already really long and looks like it would be best to have

Re: [openstack-dev] [api] Open API 3.0 for OpenStack API

Edison, This is definitely a step in the right direction if we can pull it off. Given the previous experiences and the current situation of how and where we store the information currently and how we generate the website for the API(s), can you please outline - what would be the impact to

Re: [openstack-dev] [infra] Retiring some unused repositories

On 2018-08-29 09:08, Andreas Jaeger wrote: > On 2018-08-29 06:43, Andreas Jaeger wrote: >> The infra team plans to retire the following repositories: >>  [...] > > One more repository to retire: > > openstack-infra/pynotedb > Part of storyboard effort but unused and no further interest in it.

Re: [openstack-dev] [nova] [placement] XenServer CI failed frequently because of placement update

Hi, Eric and Jay, The VCPU/Disk/RAM allocation ratio are set to 0.0 by default, and resource tracker would reset it to valid values in https://github.com/openstack/nova/blob/master/nova/objects/compute_node.py#L199. But it looks the value is set back to 0.0 by some function(I'm not sure who

[openstack-dev] [watcher] weekly meeting

Greetings, We’ll have meeting today at 8:00 UTC on #openstack-meeting-3 channel. Best Regards, Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [infra] Retiring some unused repositories

On 2018-08-29 06:43, Andreas Jaeger wrote: > The infra team plans to retire the following repositories: >  [...] One more repository to retire: openstack-infra/pynotedb Part of storyboard effort but unused and no further interest in it. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org}

[openstack-dev] [api] Open API 3.0 for OpenStack API

Hi team, As we know, Open API 3.0 was released on July, 2017, it is about one year ago. Open API 3.0 support some new features like anyof, oneof and allof than Open API 2.0(Swagger 2.0). Now OpenStack projects do not support Open API. Also I found some old emails in the Mail List about supporting

[openstack-dev] [neutron] tox-siblings alternative for local testing

hi, after a recent change [1] , neutron-fwaas' unit tests need an unreleased version of neutron. (the one including the corresponding change [2]) while it's handled by tox-siblings on the gate, it requires extra steps if you want to run the tests locally. is there any preferred solution for