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

On Thu, Sep 27, 2018 at 11:45 PM Zane Bitter wrote: > On 26/09/18 10:27 PM, Qiming Teng wrote: > > Heat still has a *lot* of users running very important stuff on Heat > scaling group code which, as you know, is burdened by a lot of technical > debt. > > Though I agree that a common library

Re: [openstack-dev] [nova][cinder][glance][osc][sdk] Image Encryption for OpenStack (proposal)

+1 to Julia's suggestion, Cinder should also have a spec to discuss the detail about how to implement the creation of volume from an encrypted image. Julia Kreger 于2018年9月28日周五 上午9:39写道： > > Greetings! > > I suspect the avenue of at least three different specs is likely going > to be the best

Re: [openstack-dev] [nova][cinder][glance][osc][sdk] Image Encryption for OpenStack (proposal)

Greetings! I suspect the avenue of at least three different specs is likely going to be the best path forward and likely what will be required for each project to fully understand how/what/why. From my point of view, I'm quite interested in this from a Nova point of view because that is the

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

On 27/09/18 7:00 PM, Duc Truong wrote: On Thu, Sep 27, 2018 at 11:14 AM Zane Bitter wrote: and we will gradually fade out the existing 'AutoScalingGroup' and related resource types in Heat. That's almost impossible to do without breaking existing users. One approach would be to switch

Re: [openstack-dev] [all][tc][elections] Stein TC Election Results

Congrats all! And for those of you who ran and we’re not elected thank you for all you do in the community! Amy (spotz) Sent from my iPhone > On Sep 27, 2018, at 6:56 PM, Emmet Hikory wrote: > > Please join me in congratulating the 6 newly elected members of the > Technical Committee (TC): >

Re: [openstack-dev] [all][tc][elections] Stein TC Election Results

On 2018-09-27 20:00:42 -0400 (-0400), Mohammed Naser wrote: [...] > A big thank you to our election team who oversees all of this as > well :) [...] I wholeheartedly concur! And an even bigger thank you to the 5 candidates who were not elected this term; please run again in the next election if

Re: [openstack-dev] [all][tc][elections] Stein TC Election Results

On Thu, Sep 27, 2018 at 7:57 PM Emmet Hikory wrote: > > Please join me in congratulating the 6 newly elected members of the > Technical Committee (TC): > > - Doug Hellmann (dhellmann) > - Julia Kreger (TheJulia) > - Jeremy Stanley (fungi) Welcome back! > - Jean-Philippe Evrard

[openstack-dev] [all][tc][elections] Stein TC Election Results

Please join me in congratulating the 6 newly elected members of the Technical Committee (TC): - Doug Hellmann (dhellmann) - Julia Kreger (TheJulia) - Jeremy Stanley (fungi) - Jean-Philippe Evrard (evrardjp) - Lance Bragstad (lbragstad) - Ghanshyam Mann (gmann) Full Results:

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On 09/27/2018 06:23 PM, Matt Riedemann wrote: On 9/27/2018 3:02 PM, Jay Pipes wrote: A great example of this would be the proposed "deploy template" from [2]. This is nothing more than abusing the placement traits API in order to allow passthrough of instance configuration data from the nova

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

On Thu, Sep 27, 2018 at 11:14 AM Zane Bitter wrote: > > > and we will gradually fade out the existing 'AutoScalingGroup' > > and related resource types in Heat. > > That's almost impossible to do without breaking existing users. One approach would be to switch the underlying Heat

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Thu, 27 Sep 2018 17:23:26 -0500, Matt Riedemann wrote: On 9/27/2018 3:02 PM, Jay Pipes wrote: A great example of this would be the proposed "deploy template" from [2]. This is nothing more than abusing the placement traits API in order to allow passthrough of instance configuration data from

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On 9/27/2018 3:02 PM, Jay Pipes wrote: A great example of this would be the proposed "deploy template" from [2]. This is nothing more than abusing the placement traits API in order to allow passthrough of instance configuration data from the nova flavor extra spec directly into the

Re: [openstack-dev] [StoryBoard] PTG Summary

Updates! On Thu, Sep 20, 2018 at 2:15 PM Kendall Nelson wrote: > Hello Lovers of Task Tracking! > > So! We talked about a lot of things, and I went to a lot of rooms to talk > about StoryBoard related things and it was already a week ago so bear with > me. > > We had a lot of good discussions

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

Its the commons problem again. Either we encourage folks to contribute a little bit to the commons (review a few other peoples noncompute cli thingies. in doing so, you learn how to better do the cli in the generic/user friendly ways), to further their own project goals (get easier access to

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On 9/27/2018 2:33 PM, Fox, Kevin M wrote: If the project plugins were maintained by the OSC project still, maybe there would be incentive for the various other projects to join the OSC project, scaling things up? Sure, I don't really care about governance. But I also don't really care about

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

If the project plugins were maintained by the OSC project still, maybe there would be incentive for the various other projects to join the OSC project, scaling things up? Thanks, Kevin From: Matt Riedemann [mriede...@gmail.com] Sent: Thursday, September

Re: [openstack-dev] [cinder][puppet][kolla][helm][ansible] Change in Cinder backup driver naming

Thanks for the email Sean. https://review.openstack.org/605846 Fix Cinder backup to use full paths I think this should cover us, please let me know if we did things right. FYI: the docs all still seem to point at the old paths..

Re: [openstack-dev] [oslo][castellan] Time for a 1.0 release?

On Tue, 2018-09-25 at 16:30 -0500, Ben Nemec wrote: > Doug pointed out on a recent Oslo release review that castellan is > still > not officially 1.0. Given the age of the project and the fact that > we're > asking people to deploy a Castellan-compatible keystore as one of > the > base

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On 9/27/2018 10:13 AM, Dean Troyer wrote: On Thu, Sep 27, 2018 at 9:10 AM, Doug Hellmann wrote: Monty Taylor writes: Main difference is making sure these new deconstructed plugin teams understand the client support lifecycle - which is that we don't drop support for old versions of services

[openstack-dev] [horizon][plugins] npm jobs fail due to new XStatic-jQuery release (was: Horizon gates are broken)

Hi, Unfortunately, this issue affects some of the plugins too :(. At least gates for the magnum-ui, senlin-dashboard, zaqar-ui and zun-ui are broken now. I'm working both with project teams to fix it asap. Let's wait if [5] helps for senlin-dashboard and fix all the rest of plugins. [5]

[openstack-dev] [Cyborg] Stein PTG summary

I've written up a high-level summary of the discussions we had at the PTG -- please feel free to reply to this thread to fill in anything I've missed. Sorry about the delay, I was really tied up after the PTG We used our PTG etherpad: https://etherpad.openstack.org/p/cyborg-ptg-stein Cyborg

[openstack-dev] [cinder][puppet][kolla][helm][ansible] Change in Cinder backup driver naming

This probably applies to all deployment tools, so hopefully this reaches the right folks. In Havana, Cinder deprecated the use of specifying the module for configuring backup drivers. Patch https://review.openstack.org/#/c/595372/ finally removed the backwards compatibility handling for configs

[openstack-dev] [ironic][neutron] SmartNics with Ironic

Greetings everyone, Now that the PTG is over, I would like to go ahead and get the specification that was proposed to ironic-specs updated to represent the discussions that took place at the PTG. A few highlights from my recollection: * Ironic being the source of truth for the hardware

Re: [openstack-dev] [nova] Stein PTG summary

On 09/27/2018 11:15 AM, Eric Fried wrote: On 09/27/2018 07:37 AM, Matt Riedemann wrote: On 9/27/2018 5:23 AM, Sylvain Bauza wrote: On Thu, Sep 27, 2018 at 2:46 AM Matt Riedemann mailto:mriede...@gmail.com>> wrote:     On 9/26/2018 5:30 PM, Sylvain Bauza wrote: > So, during this day,

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

On 26/09/18 10:27 PM, Qiming Teng wrote: Hi, Due to many reasons, I cannot join you on this event, but I do like to leave some comments here for references. On Tue, Sep 18, 2018 at 11:27:29AM +0800, Rico Lin wrote: *TL;DR* *How about a forum in Berlin for discussing autoscaling integration

[openstack-dev] [congress] 4AM UTC meeting today 9/28

Hi all, the Congress team meeting is transitioning to Fridays 4AM UTC on even weeks (starting 10/5). During this week's transition, we'll have a special transition meeting today Friday at 4AM UTC (instead of previous 2:30AM UTC) even though it's an odd week. Thank you! Eric Kao

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Ack - thanks for the clarification, Tim. On Thu, Sep 27, 2018 at 12:10 PM Tim Bell wrote: > > > Lance, > > > > The comment regarding ‘readers’ is more to explain that the distinction > between ‘admin’ and ‘user’ commands is gradually reducing, where OSC has > been prioritising ‘user’ commands.

[openstack-dev] [nova][cinder][glance][osc][sdk] Image Encryption for OpenStack (proposal)

Dear OpenStack developers, we would like to propose the introduction of an encrypted image format in OpenStack. We already created a basic implementation involving Nova, Cinder, OSC and Glance, which we'd like to contribute. We originally created a full spec document but since the official

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

Lance, The comment regarding ‘readers’ is more to explain that the distinction between ‘admin’ and ‘user’ commands is gradually reducing, where OSC has been prioritising ‘user’ commands. As an example, we give the CERN security team view-only access to many parts of the cloud. This allows

[openstack-dev] [k8s][tc] List of OpenStack and K8s Community Updates

In the last year the SIG-K8s/SIG-OpenStack group has facilitated quite a bit of discussion between the OpenStack and Kubernetes communities. In doing this work we've delivered a number of presentations and held several working sessions. I've created an etherpad that contains links to these

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

Greetings OpenStack community, This week's meeting was mostly ceremonial, with the main topic of discussion being the office hours for the SIG. If you have not heard the news about the API-SIG, we are converting from a regular weekly meeting time to a set of scheduled office hours. This change

Re: [openstack-dev] [python3-first] support in stable branches

On 9/27/18 10:36 AM, Doug Hellmann wrote: Dariusz Krol writes: Hello Champions :) I work on the Trove project and we are wondering if python3 should be supported in previous releases as well? Actually this question was asked by Alan Pevec from the stable branch maintainers list. I saw

Re: [openstack-dev] [python3-first] support in stable branches

Dariusz Krol writes: > Hello Champions :) > > > I work on the Trove project and we are wondering if python3 should be > supported in previous releases as well? > > Actually this question was asked by Alan Pevec from the stable branch > maintainers list. > > I saw you added releases up to ocata

Re: [openstack-dev] [nova] Stein PTG summary

On 09/27/2018 07:37 AM, Matt Riedemann wrote: > On 9/27/2018 5:23 AM, Sylvain Bauza wrote: >> >> >> On Thu, Sep 27, 2018 at 2:46 AM Matt Riedemann > > wrote: >> >>     On 9/26/2018 5:30 PM, Sylvain Bauza wrote: >> > So, during this day, we also discussed about

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On Thu, Sep 27, 2018 at 9:10 AM, Doug Hellmann wrote: > Monty Taylor writes: >> Main difference is making sure these new deconstructed plugin teams >> understand the client support lifecycle - which is that we don't drop >> support for old versions of services in OSC (or SDK). It's a shift from

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

On Thu, Sep 27, 2018 at 9:06 AM, Doug Hellmann wrote: > I definitely think having details about the gaps would be a prerequisite > for approving a goal, but I wonder if that's something 1 person could > even do alone. Is this an area where a small team is needed? Maybe, but it does break down

[openstack-dev] [goals][python3] switching python package jobs

I think we are ready to go ahead and switch all of the python packaging jobs to the new set defined in the publish-to-pypi-python3 template [1]. We still have some cleanup patches for projects that have not completed their zuul migration, but there are only a few and rebasing those will be easy

[openstack-dev] [python3-first] support in stable branches

Hello Champions :) I work on the Trove project and we are wondering if python3 should be supported in previous releases as well? Actually this question was asked by Alan Pevec from the stable branch maintainers list. I saw you added releases up to ocata to support python3 and there are

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

Monty Taylor writes: > Main difference is making sure these new deconstructed plugin teams > understand the client support lifecycle - which is that we don't drop > support for old versions of services in OSC (or SDK). It's a shift from > the support lifecycle and POV of python-*client, but

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

Dean Troyer writes: > On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote: >> I started documenting the compute API gaps in OSC last release [1]. It's a >> big gap and needs a lot of work, even for existing CLIs (the cold/live >> migration CLIs in OSC are a mess, and you can't even boot from

Re: [openstack-dev] [storyboard] Prioritization?

On 9/27/18 4:17 AM, Thierry Carrez wrote: Ben Nemec wrote: On 9/25/18 3:29 AM, Thierry Carrez wrote: Absence of priorities was an initial design choice[1] based on the fact that in an open collaboration every group, team, organization has their own views on what the priority of a story is,

Re: [openstack-dev] [vitrage] I would like to know how to link vitrage and prometheus.

Hello Ifat, Thank you for your help! I really appreciate it. Thanks again! Best Regards, Won 2018년 9월 27일 (목) 오후 10:00, Ifat Afek 님이 작성: > Hi, > > You can use the Prometheus datasource in Vitrage starting from Rocky > release. > > In order to use it, follow these steps: > > 1. Add 'prometheus'

Re: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T series

On Wed, Sep 26, 2018 at 1:56 PM Tim Bell wrote: > > Doug, > > Thanks for raising this. I'd like to highlight the goal "Finish moving > legacy python-*client CLIs to python-openstackclient" from the etherpad and > propose this for a T/U series goal. > > To give it some context and the motivation:

Re: [openstack-dev] [keystone] Domain-namespaced user attributes in SAML assertions from Keystone IdPs

Using the domain name + group name pairing also allows for things like: JSON:{"group_name": "C", "domain_name": "X"} JSON:{"group_name": "C", "domain_name": "Y"} To showcase how we solve the ambiguity in group names by namespacing them with domains. On Thu, Sep 27, 2018 at 3:11 AM

Re: [openstack-dev] [vitrage] I would like to know how to link vitrage and prometheus.

Hi, You can use the Prometheus datasource in Vitrage starting from Rocky release. In order to use it, follow these steps: 1. Add 'prometheus' to 'types' configuration under /etc/vitrage/vitrage.conf 2. In alertmanager.yml add a receiver as follows: - name: ** webhook_configs: - url: **

Re: [openstack-dev] [nova] Stein PTG summary

On 9/27/2018 5:23 AM, Sylvain Bauza wrote: On Thu, Sep 27, 2018 at 2:46 AM Matt Riedemann > wrote: On 9/26/2018 5:30 PM, Sylvain Bauza wrote: > So, during this day, we also discussed about NUMA affinity and we said > that we could possibly use

[openstack-dev] [vitrage] I would like to know how to link vitrage and prometheus.

I would like to know how to link vitrage and prometheus. Is there a way to receive alert information from vitrage that occurred in prometheus and Alert manager like zabbix-vitrage? I wonder ,if i can, receive prometheus's alert and place it on the entity graph in vitrage.

[openstack-dev] [vitrage] I would like to know how to link vitrage and prometheus.

I would like to know how to link vitrage and prometheus. Is there a way to receive alert information from vitrage that occurred in prometheus and Alert manager like zabbix-vitrage? I wonder ,if i can, receive prometheus's alert and place it on the entity graph in vitrage.

Re: [openstack-dev] [nova] Stein PTG summary

On Thu, Sep 27, 2018 at 2:46 AM Matt Riedemann wrote: > On 9/26/2018 5:30 PM, Sylvain Bauza wrote: > > So, during this day, we also discussed about NUMA affinity and we said > > that we could possibly use nested resource providers for NUMA cells in > > Stein, but given we don't have yet a

[openstack-dev] [placement] Tetsuro Nakamura now core

Since there were no objections and a week has passed, I've made Tetsuro a member of placement-core. Thanks for your willingness and continued help. Use your powers wisely. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting goal selection for T series

First I think that is a great goal, but I want to pick up on Dean's comment: Dean Troyer wrote: [...] The OSC core team is very thin, yes, it seems as though companies don't like to spend money on client-facing things...I'll be in the hall following this thread should anyone want to talk... I

Re: [openstack-dev] [storyboard] Prioritization?

Ben Nemec wrote: On 9/25/18 3:29 AM, Thierry Carrez wrote: Absence of priorities was an initial design choice[1] based on the fact that in an open collaboration every group, team, organization has their own views on what the priority of a story is, so worklist and tags are better ways to

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 On 25/09/18 16:47, Eduardo Gonzalez wrote: Hi, I would like to propose Chason Chan to the kolla-ansible core team. Chason is been working on addition of Vitrage roles, rework VpnaaS service, maintaining documentation as well as fixing many bugs. Voting will be open for 14 days (until

[openstack-dev] [PTG][QA] QA PTG Stein Summary

Hi All, Thanks for joining Stein QA PTG and making it successful. I am writing the QA PTG summary and detailed discussion can be found on main PTG etherpad - https://etherpad.openstack.org/p/qa-stein-ptg We are continuing the 'owner' for each working item so that we have single point of

Re: [openstack-dev] [docs][charms] Updating Deployment Guides indices of published pages

On 27/09/2018 10.04, Frode Nordahl wrote: Hello docs team, What would it take to re-generate the indices for Deployment Guides on the published Queens [0] and Rocky [1] docs pages? In a nutshell: Patience ;) All looks fine, details below: They are regenerated as part of each merge to

Re: [openstack-dev] [keystone] Domain-namespaced user attributes in SAML assertions from Keystone IdPs

On Thu, Sep 27, 2018, at 5:09 AM, vishakha agarwal wrote: > > From : Colleen Murphy > > To : > > Date : Tue, 25 Sep 2018 18:33:30 +0900 > > Subject : Re: [openstack-dev] [keystone] Domain-namespaced user attributes > > in SAML assertions from Keystone IdPs > > Forwarded message

[openstack-dev] [docs][charms] Updating Deployment Guides indices of published pages

Hello docs team, What would it take to re-generate the indices for Deployment Guides on the published Queens [0] and Rocky [1] docs pages? It seems that the charms project has missed the index for those releases due to some issues which now has been resolved [2]. We would love to reclaim our

[openstack-dev] [Searchlight] Team meeting cancellation today

Dear team, Because most of our cores are based in China and South Korea which are in the holiday season, and we had covered most of the things during our vPTG last week, we will cancel the team meeting this week. Next meeting will be held on 11 Oct 2018. Bests, *Trinh Nguyen *| Founder & Chief

Re: [openstack-dev] Ryu integration with Openstack

Hi, Code of app is in https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ovs_ryuapp.py and classes for specific bridge types are in

[openstack-dev] [publiccloud-wg] Reminder weekly meeting Public Cloud WG

Hi everyone, Time for a new meeting for PCWG - today (27th) 1400 UTC in #openstack-publiccloud! Agenda found at https://etherpad.openstack.org/p/publiccloud-wg We will again have a short brief from the PTG for those of you that missed that last week. Also, time to start planning for the

Re: [openstack-dev] [mistral] Extend created(updated)_at by started(finished)_at to clarify the duration of the task

Hi Oleg, I looked at the blueprint. Looks good to me, I understand the motivation behind. The fact that we use created_at and updated_at now to see the duration of the task is often confusing, I agree. So this would be a good addition and it is backward compatible. The only subtle thing is