Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 21/06/17 02:08, Jay Pipes wrote: On 06/20/2017 09:42 AM, Doug Hellmann wrote: Does "service VM" need to be a first-class thing? Akanda creates them, using a service user. The VMs are tied to a "router" which is the billable resource that the user understands and interacts with through the

[openstack-dev] [neutron][horizon][fwaas][vpnaas] fwaas/vpnaas dashboard split out

Hi neutron and horizon teams (especially fwaas and vpnaas folks), As we discussed so far, I prepared separate git repositories for FWaaS and VPNaaS dashboards. http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/ http://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/ All

Re: [openstack-dev] [Zun] Propose addition of Zun core team and removal notice

+1 from me as well. Thanks Dims and Yanyan for you contribution to Zun ☺ Regards, Madhuri From: Kevin Zhao [mailto:kevin.z...@linaro.org] Sent: Wednesday, June 21, 2017 6:37 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [Keystone][Mistral][Devstack] Confusion between auth_url and auth_uri in keystone middleware

On 16 June 2017 at 00:44, Mikhail Fedosin wrote: > Thanks György! > > On Thu, Jun 15, 2017 at 1:55 PM, Gyorgy Szombathelyi doclerholding.com> wrote: > >> Hi Mikhail, >> >> (I'm not from the Keystone team, but did some patches for using >>

Re: [openstack-dev] [Zun] Propose addition of Zun core team and removal notice

+1 for me. Thx! On 20 June 2017 at 13:50, Pradeep Singh wrote: > +1 from me, > Thanks Shunli for your great work :) > > On Tue, Jun 20, 2017 at 10:02 AM, Hongbin Lu > wrote: > >> Hi all, >> >> >> >> I would like to propose the following change to

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On 06/20/2017 09:51 AM, Eric Fried wrote: Nice Stephen! For those who aren't aware, the rendered version (pretty, so pretty) can be accessed via the gate-nova-docs-ubuntu-xenial jenkins job:

Re: [openstack-dev] [neutron] [nova] [os-vif] OVS plugin assumes an incorrect datapath_type in os-vif

vif_details has always been a bag of goodies for mech drivers to pack in information relevant to wiring up the vif_type. This sounds like a pretty standard addition so I don't see any blockers. On Tue, Jun 20, 2017 at 9:16 AM, Alonso Hernandez, Rodolfo < rodolfo.alonso.hernan...@intel.com> wrote:

Re: [openstack-dev] [all] Policy rules for APIs based on "domain_id"

Domain support hasn't really been adopted across various OpenStack projects, yet. Ocata was the first release where we had a v3-only jenkins job set up for projects to run against (domains are a v3-only concept in keystone and don't really exist in v2.0). I think it would be great to push on some

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 20/06/17 11:45, Jay Pipes wrote: Good discussion, Zane. Comments inline. ++ On 06/20/2017 11:01 AM, Zane Bitter wrote: On 20/06/17 10:08, Jay Pipes wrote: On 06/20/2017 09:42 AM, Doug Hellmann wrote: Does "service VM" need to be a first-class thing? Akanda creates them, using a

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Excerpts from Jay Pipes's message of 2017-06-20 10:08:54 -0400: > On 06/20/2017 09:42 AM, Doug Hellmann wrote: > > Does "service VM" need to be a first-class thing? Akanda creates > > them, using a service user. The VMs are tied to a "router" which > > is the billable resource that the user

Re: [openstack-dev] [kuryr][Release-job-failures] Release of openstack/kuryr-tempest-plugin failed

Looks like kuryr-tempest-plugin doesn’t have a voting docs job for regular commits. I’ve added https://review.openstack.org/#/c/475901/ and  https://review.openstack.org/#/c/475904/ to fix the issue. Regards, Kirill On 20 June 2017 at 21:51:49, Doug Hellmann (d...@doughellmann.com) wrote: It

[openstack-dev] [keystone] New Office Hours Proposal

Greetings All, We would like to foster a more interactive community within Keystone focused on fixing bugs on a regular basis! On a regular datetime (to be voted upon) we will have "office hours"[1] where Keystone cores will be available specifically to advise, help and review your efforts in

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 06/20/2017 11:45 AM, Jay Pipes wrote: Good discussion, Zane. Comments inline. On 06/20/2017 11:01 AM, Zane Bitter wrote: 2) The database VMs are created in a project belonging to the operator of the service. They're connected to the user's network through , and isolated from other

Re: [openstack-dev] [nova] How to handle nova show --minimal with embedded flavors

On Tue, Jun 20, 2017 at 12:07 PM, Chris Friesen wrote: > In the existing novaclient code for show/rebuild, the --minimal option just > skips doing the lookups on the flavor/image as described in the help text. > It doesn't affect the other ~40 fields in the instance.

Re: [openstack-dev] [tripleo][ci] where to find the CI backlog and issues we're tracking

On Tue, Jun 20, 2017 at 12:49 PM, Wesley Hayutin wrote: > Greetings, > > It's become apparent that everyone in the tripleo community may not be aware > of where CI specific work is tracked. > > To find out which CI related features or bug fixes are in progress or to see > the

[openstack-dev] [kuryr][Release-job-failures] Release of openstack/kuryr-tempest-plugin failed

It looks like the kuryr-tempest-plugin repository has a documentation job set up but no documentation. http://logs.openstack.org/1e/1ee40b0f0ee4e92209b8ccff6d74f4980f6234ab/release/kuryr-tempest-plugin-docs-ubuntu-xenial/7f096fd/console.html#_2017-06-20_17_03_00_590629 --- Begin forwarded

Re: [openstack-dev] [glance] nominating Abhishek Kekane for glance core

Wasn't Abhishek a glance core before? What a surprise for me o_O I thought that he was just being modest and did not put -2 on the patches. Undoubtedly, we need to correct this misunderstanding as quickly as possible and invite Abhishek to the core team. On Mon, Jun 19, 2017 at 5:40 PM, Erno

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Tuesday, June 20, 2017 5:59 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [openstack-dev[[nova] Simple question > about sorting CPU topologies > > On 06/20/2017 12:53 PM, Chris Friesen

Re: [openstack-dev] [nova] How to handle nova show --minimal with embedded flavors

On 06/20/2017 07:59 AM, Matt Riedemann wrote: Personally I think that if I specify --minimal I want minimal output, which would just be the flavor's original name after the new microversion, which is closer in behavior to how --minimal works today before the 2.47 microversion. In the existing

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

On 06/20/2017 12:53 PM, Chris Friesen wrote: On 06/20/2017 06:29 AM, Jay Pipes wrote: On 06/19/2017 10:45 PM, Zhenyu Zheng wrote: Sorry, The mail sent accidentally by mis-typing ... My question is, what is the benefit of the above preference? Hi Kevin! I believe the benefit is so that the

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

On 06/20/2017 06:29 AM, Jay Pipes wrote: On 06/19/2017 10:45 PM, Zhenyu Zheng wrote: Sorry, The mail sent accidentally by mis-typing ... My question is, what is the benefit of the above preference? Hi Kevin! I believe the benefit is so that the compute node prefers CPU topologies that do

[openstack-dev] [tripleo][ci] where to find the CI backlog and issues we're tracking

Greetings, It's become apparent that everyone in the tripleo community may not be aware of where CI specific work is tracked. To find out which CI related features or bug fixes are in progress or to see the backlog please consult [1]. To find out what issues have been found in OpenStack via CI

Re: [openstack-dev] realtime kvm cpu affinities

On 06/20/2017 01:48 AM, Henning Schild wrote: Hi, We are using OpenStack for managing realtime guests. We modified it and contributed to discussions on how to model the realtime feature. More recent versions of OpenStack have support for realtime, and there are a few proposals on how to improve

[openstack-dev] [MassivelyDistributed] [FEMDC] IRC Meeting tomorrow 15:00 UTC

Dear all, A gentle reminder for our meeting tomorrow. As usual, the agenda is available at: https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 810) Please feel free to add items. Best, ad_rien_ PS: as you may have seen, we decided during our last meeting to switch

[openstack-dev] [neutron] [nova] [os-vif] OVS plugin assumes an incorrect datapath_type in os-vif

Hello fellows: Currently there is a bug in os-vif [1]. When os-vif tries to plug an OVS interface, the datapath type is hardcoded: -

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

Nice Stephen! For those who aren't aware, the rendered version (pretty, so pretty) can be accessed via the gate-nova-docs-ubuntu-xenial jenkins job: http://docs-draft.openstack.org/10/475810/1/check/gate-nova-docs-ubuntu-xenial/25e5173//doc/build/html/scheduling.html?highlight=scheduling On

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

On 20.06.2017 17:27, Michał Jastrzębski wrote: > On 19 June 2017 at 06:05, Doug Hellmann wrote: >> Excerpts from Michał Jastrzębski's message of 2017-06-16 15:50:54 -0700: >>> So I'm trying to figure out how to actually use it. >>> >>> We (and any other container based

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Good discussion, Zane. Comments inline. On 06/20/2017 11:01 AM, Zane Bitter wrote: On 20/06/17 10:08, Jay Pipes wrote: On 06/20/2017 09:42 AM, Doug Hellmann wrote: Does "service VM" need to be a first-class thing? Akanda creates them, using a service user. The VMs are tied to a "router"

Re: [openstack-dev] [deployment][kolla][openstack-ansible][openstack-helm][tripleo] ansible role to produce oslo.config files for openstack services

On 19 June 2017 at 06:05, Doug Hellmann wrote: > Excerpts from Michał Jastrzębski's message of 2017-06-16 15:50:54 -0700: >> So I'm trying to figure out how to actually use it. >> >> We (and any other container based deploy..) will run into some >> chicken/egg problem - you

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 20/06/17 10:08, Jay Pipes wrote: On 06/20/2017 09:42 AM, Doug Hellmann wrote: Does "service VM" need to be a first-class thing? Akanda creates them, using a service user. The VMs are tied to a "router" which is the billable resource that the user understands and interacts with through the

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 18/06/17 07:35, Amrith Kumar wrote: Trove has evolved rapidly over the past several years, since integration in IceHouse when it only supported single instances of a few databases. Today it supports a dozen databases including clusters and replication. The user survey [1] indicates that

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On 06/20/2017 09:51 AM, Alex Xu wrote: 2017-06-19 22:17 GMT+08:00 Jay Pipes >: * Scheduler then creates a list of N of these data structures, with the first being the data for the selected host, and the the rest being data

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On Mon, 2017-06-19 at 09:36 -0500, Matt Riedemann wrote: > On 6/19/2017 9:17 AM, Jay Pipes wrote: > > On 06/19/2017 09:04 AM, Edward Leafe wrote: > > > Current flow: > > As noted in the nova-scheduler meeting this morning, this should have  > been called "original plan" rather than "current

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 06/20/2017 09:42 AM, Doug Hellmann wrote: Does "service VM" need to be a first-class thing? Akanda creates them, using a service user. The VMs are tied to a "router" which is the billable resource that the user understands and interacts with through the API. Frankly, I believe all of these

[openstack-dev] [nova] How to handle nova show --minimal with embedded flavors

Microversion 2.47 embeds the instance.flavor in the server response body. Chris Friesen is adding support for this microversion to novaclient [1] and a question has come up over how to deal with the --minimal option which before this microversion would just show the flavor id. When --minimal

Re: [openstack-dev] [all] Policy rules for APIs based on "domain_id"

Also, one more additional kind of "feature-request" is to be able to filter each project's entities per domain as well as we can do it with project/tenant now. So, as a result, we will be able to configure different "list" APIs to return objects grouped by either domain or project. Thoughts? On

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On Jun 20, 2017, at 8:38 AM, Jay Pipes wrote: > >>> The example I posted used 3 resource providers. 2 compute nodes with no >>> local disk and a shared storage pool. >> Now I’m even more confused. In the straw man example >> (https://review.openstack.org/#/c/471927/ >>

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

2017-06-19 22:17 GMT+08:00 Jay Pipes : > On 06/19/2017 09:04 AM, Edward Leafe wrote: > >> Current flow: >> * Scheduler gets a req spec from conductor, containing resource >> requirements >> * Scheduler sends those requirements to placement >> * Placement runs a query to

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

Excerpts from Curtis's message of 2017-06-19 18:56:25 -0600: > On Sun, Jun 18, 2017 at 5:35 AM, Amrith Kumar wrote: > > Trove has evolved rapidly over the past several years, since integration in > > IceHouse when it only supported single instances of a few databases.

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On 06/20/2017 08:43 AM, Edward Leafe wrote: On Jun 20, 2017, at 6:54 AM, Jay Pipes > wrote: It was the "per compute host" that I objected to. I guess it would have helped to see an example of the data returned for multiple compute nodes. The

Re: [openstack-dev] [trove][all][tc] A proposal to rearchitect Trove

On 19/06/17 20:56, Curtis wrote: I really think the concept of "service VMs" should be a thing. I'm not sure where the OpenStack community has landed on that, my fault for not paying close attention, but we should be able to create VMs for a tenant that are not managed by the tenant but that

Re: [openstack-dev] [OpenStack-docs] [openstack-docs][dev][all] Documentation repo freeze

On 6/20/17, 2:12 PM, "Anne Gentle" wrote: On Tue, Jun 20, 2017 at 3:13 AM, Alexandra Settle wrote: > > > On 6/19/17, 6:19 PM, "Petr Kovar" wrote: > > On Mon, 19 Jun 2017 15:56:35 + >

Re: [openstack-dev] [openstack-ansible][designate] Recommended way to inject the rndc.key into the designate container when using Bind9

Hi Lawrence, Thanks for providing the feedback! I am using OpenStack Designate with Bind9 as the slave and have managed to > set it up with openstack-ansible in all respect bar one, I am unable to > automatically inject the rndc.key file into the Designate container. > Is there a recognised way

Re: [openstack-dev] [OpenStack-docs] [openstack-docs][dev][all] Documentation repo freeze

On Tue, Jun 20, 2017 at 3:13 AM, Alexandra Settle wrote: > > > On 6/19/17, 6:19 PM, "Petr Kovar" wrote: > > On Mon, 19 Jun 2017 15:56:35 + > Alexandra Settle wrote: > > > Hi everyone, > > > > As of today -

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On Jun 20, 2017, at 6:54 AM, Jay Pipes wrote: > >>> It was the "per compute host" that I objected to. >> I guess it would have helped to see an example of the data returned for >> multiple compute nodes. The straw man example was for a single compute node >> with SR-IOV,

Re: [openstack-dev] [openstack-dev[[nova] Simple question about sorting CPU topologies

On 06/19/2017 10:45 PM, Zhenyu Zheng wrote: Sorry, The mail sent accidentally by mis-typing ... My question is, what is the benefit of the above preference? Hi Kevin! I believe the benefit is so that the compute node prefers CPU topologies that do not have hardware threads over CPU

[openstack-dev] [nova] api.fault notification is never emitted

Hi, I come across a questionable behavior of nova while I tried to use the notify_on_api_faults configuration option [0] while testing the related versioned notification transformation patch [1]. Based on the description of the config option and the code that uses it [2] nova sends and

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On 06/19/2017 09:26 PM, Boris Pavlovic wrote: Hi, Does this look too complicated and and a bit over designed. Is that a question? For example, why we can't store all data in memory of single python application with simple REST API and have simple mechanism for plugins that are filtering.

Re: [openstack-dev] [openstack-ansible][designate][bind9] Looking for ways to limit users to adding hosts within fixed personal domain

On 20/06/17 12:37, Lawrence J. Albinson wrote: > I am trying to find pointers to how I might limit non-privileged users > to a single domain when adding hosts to Designate. > > It is a private OpenStack cloud and each user will have a personal > sub-domain of a common organisational domain, like

Re: [openstack-dev] [nova][scheduler][placement] Trying to understand the proposed direction

On 06/19/2017 08:05 PM, Edward Leafe wrote: On Jun 19, 2017, at 5:27 PM, Jay Pipes > wrote: It was from the straw man example. Replacing the $FOO_UUID with UUIDs, and then stripping out all whitespace resulted in about 1500 bytes. Your example,

[openstack-dev] [openstack-ansible][designate][bind9] Looking for ways to limit users to adding hosts within fixed personal domain

I am trying to find pointers to how I might limit non-privileged users to a single domain when adding hosts to Designate. It is a private OpenStack cloud and each user will have a personal sub-domain of a common organisational domain, like so: fred.organisation.com. and will be able to add

[openstack-dev] [openstack-ansible][designate] Recommended way to inject the rndc.key into the designate container when using Bind9

I am using OpenStack Designate with Bind9 as the slave and have managed to set it up with openstack-ansible in all respect bar one, I am unable to automatically inject the rndc.key file into the Designate container. Is there a recognised way to do this (and similar things elsewhere across the

Re: [openstack-dev] [requirements][ec2-api] How about using boto3instead of boto in requirements

Hi, Thanks! I will try to use botocore instead of boto3 to find out whether the code running or not. jiaopengju mail: jiaopen...@cmss.chinamobile.com 原始邮件 发件人:Andrey pavlovandrey...@gmail.com 收件人:OpenStack Development Mailing List (not for usage questions)openstack-dev@lists.openstack.org;

Re: [openstack-dev] [requirements][ec2-api] How about using boto3 instead of boto in requirements

Hi, We (ec2-api team) now in the middle of some investigations that should lead us to either to remove boto from the code or to change it to botocore as we decided previously. We'll done with it to the middle of July. Regards, Andrey Pavlov. On Tue, Jun 20, 2017 at 10:15 AM, Tony Breeds

Re: [openstack-dev] [glance] Stepping down from core

On 20/06/17 09:31 +1200, feilong wrote: Hi there, I've been a Glance core since 2013 and been involved in the Glance community even longer, so I care deeply about Glance. My situation right now is such that I cannot devote sufficient time to Glance, and while as you've seen elsewhere on the

Re: [openstack-dev] [tc][fuel] Making Fuel a hosted project

Thanks for the initial feedback everyone. I proposed the matching governance change at: https://review.openstack.org/475721 Please comment there if you think it's a good or bad idea. -- Thierry Carrez (ttx) __ OpenStack

Re: [openstack-dev] [all] Policy rules for APIs based on "domain_id"

Hello Valeriy, agree, that would be very useful. I think that this deserves attention and cross project discussion. Maybe a community goal process [2] is a valid path forward in this regard. [2] https://governance.openstack.org/tc/goals/ On Tue, Jun 20, 2017 at 11:15 AM, Valeriy Ponomaryov <

Re: [openstack-dev] [all][tc] Moving away from "big tent" terminology

On 20/06/17 00:33 +, joehuang wrote: I think openstack community provides a flat project market place for infrastructure is good enough: all projects are just some "goods" in the market place, let the cloud operators to select projects from the project market place for his own

[openstack-dev] [all] Policy rules for APIs based on "domain_id"

Hello OpenStackers, Wanted to pay some attention to one of restrictions in OpenStack. It came out, that it is impossible to define policy rules for API services based on "domain_id". As far as I know, only Keystone supports it. So, it is unclear whether it is intended or it is just technical

[openstack-dev] [tricircle]weekly meeting of Jun.21

Hello, team, Agenda of Jun.21 weekly meeting: 1. summary of tricircle demo in OPNFV summit 3. feature implementation review 4. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00. Best

[openstack-dev] [tricircle]weekly meeting of Jun.21

Hello, team, Agenda of Jun.20 weekly meeting: 1. summary of tricircle demo in OPNFV summit 3. feature implementation review 4. Open Discussion How to join: # IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 1:00. Best

Re: [openstack-dev] [Openstack-operators][all][Ironic][Nova] The /service API endpoint

Hi, > 1) create a new API endpoint e.g. 'v1/service' that can report which conductor is managing given node. Additionally it can also report aliveness of all Ironic conductors and on which hosts they are running (similar to nova service-list) > 2) expose conductor_affinity in node-show (but

Re: [openstack-dev] [OpenStack-docs] [openstack-docs][dev][all] Documentation repo freeze

On 6/19/17, 6:19 PM, "Petr Kovar" wrote: On Mon, 19 Jun 2017 15:56:35 + Alexandra Settle wrote: > Hi everyone, > > As of today - Monday, the 19th of June – please do NOT merge any patches into > the openstack-manuals

[openstack-dev] [horizon] Next weekly IRC meeting cancelled

Hey everyone, The next weekly IRC meeting (2017-06-21) is cancelled, as I’m away for a week. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [requirements][ec2-api] How about using boto3 instead of boto in requirements

On Tue, Jun 20, 2017 at 05:15:59PM +1000, Tony Breeds wrote: > On Mon, Jun 19, 2017 at 09:33:02PM +0800, jiaopengju wrote: > > Hi Dims, > > I got response from core member of ec2-api. What do you think about it? > > > > > > -- > > Hi, > > > > > > I don't treat

[openstack-dev] realtime kvm cpu affinities

Hi, We are using OpenStack for managing realtime guests. We modified it and contributed to discussions on how to model the realtime feature. More recent versions of OpenStack have support for realtime, and there are a few proposals on how to improve that further. But there is still no full

Re: [openstack-dev] [neutron] security group OVO change

Does this fix your issue? https://review.openstack.org/#/c/475445/ On Mon, Jun 19, 2017 at 12:21 AM, Gary Kotton wrote: > Sorry for being vague – have been debugging. > > We overwrite the base method: > > > > with db_api.context_manager.writer.using(context): > >

Re: [openstack-dev] [requirements][ec2-api] How about using boto3 instead of boto in requirements

On Mon, Jun 19, 2017 at 09:33:02PM +0800, jiaopengju wrote: > Hi Dims, > I got response from core member of ec2-api. What do you think about it? > > > -- > Hi, > > > I don't treat adding new library as a problem. > > > - I see that you don't remove boto - so

[openstack-dev] [Openstack-operators][all][Ironic][Nova] The /service API endpoint

Hi All, I am working on a bug [1] in Ironic which talks exposing the state of conductor service running in OpenStack environment. There are two ways to do this: 1) create a new API endpoint e.g. 'v1/service' that can report which conductor is managing given node. Additionally it can also