[openstack-dev] [keystone] Keystone Team Update - Week of 29 October 2018

# Keystone Team Update - Week of 29 October 2018 ## News ### Berlin Summit Somewhat quiet week as we've been getting into summit prep mode. We'll have two forum sessions, one for operator feedback[1] and one to discuss Keystone as an IdP Proxy[2]. We'll have our traditional project update[3] a

Re: [openstack-dev] [all]Naming the T release of OpenStack -- Poll open

On Wed, Nov 7, 2018, at 11:12 AM, Lajos Katona wrote: > Hi, > > Maybe I missed something but I got the message: "Already voted > A vote has already been cast using your voter key. > > Poll results will be available only to the following users: > > t...@bakeyournoodle.com

[openstack-dev] [keystone] Keystone Team Update - Week of 5 November 2018

# Keystone Team Update - Week of 5 November 2018 ## News ### Community Goals Status Python3-first[1]: completed Upgrade status check[2]: scaffolding is completed but we don't have actual checks yet Mutable config[3] (goal from last cycle): review in progress but needs work [1] https://governan

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

On Tue, Dec 8, 2015 at 8:49 AM, Emilien Macchi wrote: > Hi, > > Back in "old days", Cody was already core on the modules, when they were > hosted by Puppetlabs namespace. > His contributions [1] are very valuable to the group: > * strong knowledge on Puppet and all dependencies in general. > * ve

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

On Mon, Apr 18, 2016 at 8:37 AM, Sebastien Badia wrote: > Hello here, > > I would like to ask to be removed from the core reviewers team on the > Puppet for OpenStack project. > > I lack dedicated time to contribute on my spare time to the project. And I > don't work anymore on OpenStack deployme

Re: [openstack-dev] [puppet] [neutron] Serious bug in puppet neutron cli json output parsing.

On Wed, Dec 30, 2015 at 8:37 AM, Sofer Athlan-Guyot wrote: > Hi, > > I have added neutron people as they may help to find a solution. > > After banging my head against the wall for a whole afternoon I > discovered a serious bug in puppet neutron module. > > I not going to repeat here the detail o

[openstack-dev] [infra] Nodepool and wiki.openstack.org downtime on 5 January 2016

The site wiki.openstack.org as well as the nodepool service will be offline for 30 minutes starting at 2100 UTC on 5 January 2016 while we update infrastructure management of these services. The nodepool downtime will cause a disruption in the testing infrastructure that will cause jobs to be delay

Re: [openstack-dev] [infra] Nodepool and wiki.openstack.org downtime on 5 January 2016

On Mon, Jan 4, 2016 at 10:46 AM, Colleen Murphy wrote: > The site wiki.openstack.org as well as the nodepool service will be > offline for 30 minutes starting at 2100 UTC on 5 January 2016 while we > update infrastructure management of these services. The nodepool downtime >

Re: [openstack-dev] [OpenStack-Infra] Mitaka Infra Sprint

On Wed, Dec 9, 2015 at 9:17 PM, Joshua Hesketh wrote: > Hi all, > As discussed during the infra-meeting on Tuesday[0], the infra team will > be holding a mid-cycle sprint to focus on infra-cloud[1]. > The sprint is an opportunity to get in a room and really work through as > much code and reviews

Re: [openstack-dev] [puppet] [oslo] Proposal of adding puppet-oslo to OpenStack

On Tue, Jan 19, 2016 at 9:57 AM, Xingchao Yu wrote: > Hi, Emilien: > > Thanks for your efforts on this topic, I didn't attend V release > summit and missed related discussion about puppet-oslo. > > As the reason for not using a unified way to manage oslo_* parameters > is there maybe ex

Re: [openstack-dev] [puppet] Stepping down from Puppet Core

On Wed, Jan 27, 2016 at 12:35 PM, Emilien Macchi wrote: > > > On 01/27/2016 03:13 PM, Mathieu Gagné wrote: > > Hi, > > > > I would like to ask to be removed from the core reviewers team on the > > Puppet for OpenStack project. > > > > My day to day tasks and focus no longer revolve solely around

Re: [openstack-dev] [puppet] Proposing Yanis Guenane core

On Mon, Jul 27, 2015 at 12:06 PM, Emilien Macchi wrote: > Puppet group, > > Yanis has been working in our group for a while now. > He has been involved in a lot of tasks, let me highlight some of them: > > * Many times, involved in improving consistency across our modules. > * Strong focus on dat

Re: [openstack-dev] [infra][puppet] Keeping common set of file synchronized across puppet modules

On Wed, Jul 29, 2015 at 5:40 AM, Jeremy Stanley wrote: > On 2015-07-29 10:53:38 +0200 (+0200), Yanis Guenane wrote: > > On 07/28/2015 07:13 PM, Andreas Jaeger wrote: > [...] > > > * If there is a proposed change already for a project, reuse that one > > > instead of creating a new one? > > > > I

Re: [openstack-dev] [puppet] hosting developer documentation on http://docs.openstack.org/developer/

On Wed, Sep 2, 2015 at 11:09 AM, Emilien Macchi wrote: > TL;DR, I propose to move our developer documentation from wiki to > something like http://docs.openstack.org/developer/puppet-openstack > > (Look at http://docs.openstack.org/developer/tempest/ for example). > > For now, most of our documen

Re: [openstack-dev] [puppet] weekly meeting #54

On Mon, Oct 5, 2015 at 5:48 AM, Emilien Macchi wrote: > Hello! > > Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC > in #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151006 > > Feel free to add any additional items you'd like to

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin wrote: > Puppetmaster and Fuelers, > > Last week I mentioned that I would like to bring the theme of using native > ruby OpenStack client and use it within the providers. > > Emilien told me that I had already been late and the decision was made >

[openstack-dev] [puppet] Weekly meeting #36

Hi everyone, Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150526 Please add additional items you'd like to discuss. Colleen ___

Re: [openstack-dev] [puppet] Weekly meeting #36

On Mon, May 25, 2015 at 8:17 PM, Matt Fischer wrote: > Emilien, sbadia, and spredzy are out. Given that agenda, should we cancel > since its right after the summit and a holiday? My update (the only other > thing on the agenda) is that the clean-up is done. > Let's go ahead and cancel, as there's

[openstack-dev] [puppet] Weekly meeting #36

Hi everyone, Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150602 Please add additional items you'd like to discuss. Colleen ___

Re: [openstack-dev] [puppet] Weekly meeting #36

On Mon, Jun 1, 2015 at 12:16 PM, Colleen Murphy wrote: > Hi everyone, > > Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in > #openstack-meeting-4: > > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150602 > > Please add a

[openstack-dev] [puppet] Change abandonment policy

In today's meeting we discussed implementing a policy for whether and when core reviewers should abandon old patches whose author's were inactive. (This doesn't apply to authors that want to abandon their own changes, only for core reviewers to abandon other people's changes.) There are a few thing

Re: [openstack-dev] [puppet] openstacklib::db::sync proposal

On Sun, Jun 7, 2015 at 11:48 PM, Yanis Guenane wrote: > > > On 06/03/2015 02:32 PM, Martin Mágr wrote: > > > > On 06/02/2015 07:05 PM, Mathieu Gagné wrote: > >> On 2015-06-02 12:41 PM, Yanis Guenane wrote: > >>> The openstacklib::db::sync[2] is currently only a wrapper around an > >>> exec > >>>

Re: [openstack-dev] [puppet] Change abandonment policy

On Tue, Jun 2, 2015 at 11:39 AM, Colleen Murphy wrote: > In today's meeting we discussed implementing a policy for whether and when > core reviewers should abandon old patches whose author's were inactive. > (This doesn't apply to authors that want to abandon their own

[openstack-dev] [puppet] Installing dependent modules in functional testing

Now that we have the basic beaker-rspec framework set up in the modules and working in infra's CI, we need to start making our testing aware of Zuul dependencies. The infra team is facing similar challenges so it would be nice to work together on this. Discussions with jeblair and nibalizer have re

Re: [openstack-dev] [puppet] Installing dependent modules in functional testing

On Thu, Jun 18, 2015 at 2:24 PM, Colleen Murphy wrote: > Now that we have the basic beaker-rspec framework set up in the modules > and working in infra's CI, we need to start making our testing aware of > Zuul dependencies. The infra team is facing similar challenges so it woul

Re: [openstack-dev] [puppet] [infra] issues with beaker/centos7 job

On Thu, Jul 2, 2015 at 11:40 AM, Jeremy Stanley wrote: > On 2015-07-02 16:02:32 +0200 (+0200), Alan Pevec wrote: > > After having a closer look, I see that image has requests 2.7 > > installed from pypi which overwrites python-requests RPM installation > > and wreaks havoc when trying to upgrade

Re: [openstack-dev] [puppet] how to run rspec tests? r10k issue

On Thu, Feb 18, 2016 at 2:26 PM, Matt Fischer wrote: > Is anyone able to share the secret of running spec tests since the r10k > transition? bundle install && bundle exec rake spec have issues because > r10k is not being installed. Since I'm not the only one hopefully this > question will help ot

Re: [openstack-dev] [puppet] Re-schedule Puppet OpenStack meeting

Tuesdays has more votes it makes sense to book that time in #openstack-meeting-4. If there are objections or concerns please voice them here. Colleen (crinkle) On Thu, Mar 12, 2015 at 1:51 PM, Colleen Murphy wrote: > >> >> Forwarded Message >> Subject: [o

[openstack-dev] [puppet] Moving under the "big tent"

This thread is to follow up on our IRC discussion today. In today's meeting we started discussing whether we want to pursue applying to move under the OpenStack namespace and what pros and cons are. One concern that was brought up was that our contributor base, being largely made up of operators wi

Re: [openstack-dev] [puppet] Release management and bug triage

Comments inline. On Tue, Mar 17, 2015 at 12:22 PM, Emilien Macchi wrote: > Hi, > > I wanted to start the discussion here about our bug/release management > system with Launchpad. > > A first question that comes in my mind is: should we continue to manage > every Puppet module in a different Laun

Re: [openstack-dev] [puppet] Re-schedule Puppet OpenStack meeting

uss at the meeting, please add them to the agenda here: https://wiki.openstack.org/wiki/Meetings/PuppetOpenStack#Agenda Colleen (crinkle) On Mon, Mar 16, 2015 at 8:04 AM, Colleen Murphy wrote: > Based on the results of https://doodle.com/wuhsuafq5tibzugg we have two > contenders, in 1st

[openstack-dev] [puppet] Meeting notes 24 March 2015

Our meeting minutes from today are here: http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-03-24-14.59.html We discussed electing a PTL, and will be following up soon to start a deeper discussion on the mailing lists. We'd like to start dedicating time for launc

[openstack-dev] [puppet] Meeting notes for April 7 and PTL update

Hi all, The minutes from today's meeting are here: http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-04-07-15.00.html One outcome of this meeting is that we plan to close the PTL nomination process on April 9, 2015 at 05:59 UTC. If you would like to nominate you

[openstack-dev] [puppet] Puppet PTL

Just to make it official: since we only had one nominee for PTL, we will go ahead and name Emilien Macchi as our new PTL without proceeding with an election process. Thanks, Emilien, for all your hard work and for taking on this responsibility! Colleen (crinkle) ___

Re: [openstack-dev] [puppet] rabbit/kombu settings deprecations

On Thu, Apr 16, 2015 at 7:50 AM, Emilien Macchi wrote: > > > On 04/16/2015 12:26 AM, Matt Fischer wrote: > > Recently a mass of changes was proposed and some merged to move the > > rabbit/kombu settings to avoid a Kilo deprecation. As far as I can tell > > this will break rabbit connectivity for

[openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

I'm cross-posting to the dev list since this conversation should be happening there and is related to another thread there. I'm going to top-post a summary and then respond inline. The summary so far is that puppet-openstacklib provides a way to pass in credentials to an API-driven puppet type via

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

On Tue, May 5, 2015 at 11:36 AM, Rich Megginson wrote: > On 05/05/2015 12:20 PM, Colleen Murphy wrote: > > I'm cross-posting to the dev list since this conversation should be > happening there and is related to another thread there. > > > Ok. I'm not replying p

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On Wed, May 6, 2015 at 4:26 PM, Mike Dorman wrote: > We also run all masterless/puppet apply. And we just populate a bare > bones keystone.conf on any box that does not have keystone installed, but > Puppet needs to be able to create keystone resources. > > Also agreed on avoiding puppetdb, for

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

On Wed, May 6, 2015 at 6:26 PM, Gilles Dubreuil wrote: > It seems ~/.openrc is the only default [...] > The extras module places it at '/root/openrc' [1], so either the extras module should be changed or the providers should look in /root/openrc, either way it should be consistent. Colleen [1]

Re: [openstack-dev] [puppet] Proposal to configure Oslo libraries

On Fri, May 8, 2015 at 9:47 AM, Mike Dorman wrote: > +1 I agree we should do this, etc., etc. > > I don’t have a strong preference for #1 or #2, either. But I do think #1 > is slightly more complicated from a deployer/operator perspective. It’s > another module I have to manage, pull in, etc.

Re: [openstack-dev] [puppet] Proposal to configure Oslo libraries

On Fri, May 8, 2015 at 12:50 PM, Mathieu Gagné wrote: > On 2015-05-07 4:19 PM, Emilien Macchi wrote: > > > > Proposals > > = > > > > #1 Creating puppet-oslo > > ... and having oslo::messaging::rabbitmq, oslo::messaging::qpid, ..., > > oslo::logging, etc. > http://git.openstack.org/cgit/st

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

On Tue, May 16, 2017 at 2:07 AM, Adrian Turjak wrote: > > > Tangentially related to this (because my reasons are different), on our > cloud I'm actually working on something like this, but under the hood all > I'm doing is creating a user with a generated password and enforcing a > username conve

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

On Sun, May 14, 2017 at 6:59 PM, Monty Taylor wrote: > On 05/11/2017 02:32 PM, Lance Bragstad wrote: > >> Hey all, >> >> One of the Baremetal/VM sessions at the summit focused on what we need >> to do to make OpenStack more consumable for application developers [0]. >> As a group we recognized th

Re: [openstack-dev] [all][keystone][product] api keys/application specific passwords

On Wed, May 17, 2017 at 12:21 AM, Monty Taylor wrote: > On 05/16/2017 02:44 PM, Sean Dague wrote: > >> On 05/16/2017 03:40 PM, Monty Taylor wrote: >> >>> On 05/16/2017 10:20 AM, Doug Hellmann wrote: >>> Excerpts from Chris Dent's message of 2017-05-16 15:16:08 +0100: > On Tue, 16 Ma

Re: [openstack-dev] [keystone] removing domain configuration upload via keystone-manage

> > On Wed, Jun 28, 2017 at 2:00 AM, Lance Bragstad > wrote: > >> Hi all, >> >> Keystone has deprecated the domain configuration upload capability >> provided through `keystone-manage`. We discussed it's removal in today's >> meeting [0] and wanted to send a quick note to the operator list. The >>

Re: [openstack-dev] [keystone] deprecating and removing tools/sample_data.sh

On Wed, Jul 5, 2017 at 9:36 PM, Lance Bragstad wrote: > Hi all, > > Keystone has a script to perform some bootstrapping operations [0]. It's > not really tested and its purpose has been superseded by using the > `keystone-manage bootstrap` command. Based on codesearch, only > openstack/rpm-packag

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On Tue, Jul 18, 2017 at 1:39 AM, Zane Bitter wrote: > So the application credentials spec has merged - huge thanks to Monty and > the Keystone team for getting this done: > > https://review.openstack.org/#/c/450415/ > http://specs.openstack.org/openstack/keystone-specs/specs/ > keystone/pike/appl

Re: [openstack-dev] [policy] AWS IAM session

On Tue, Oct 3, 2017 at 10:08 PM, Lance Bragstad wrote: > Hey all, > > It was mentioned in today's keystone meeting [0] that it would be useful > to go through AWS IAM (or even GKE) as a group. With all the recent > policy discussions and work, it seems useful to get our eyes on another > system.

[openstack-dev] [tc][election] TC candidacy

Thank you for your consideration. Colleen Murphy (cmurphy) https://www.openstack.org/community/members/profile/11727/colleen-murphy http://stackalytics.com/?release=all&user_id=krinkle [1] http://superuser.openstack.org/articles

Re: [openstack-dev] [keystone][nova] Persistent application credentials

On Mon, Oct 9, 2017 at 6:39 PM, Zane Bitter wrote: > On 12/09/17 18:58, Colleen Murphy wrote: > >> While it's fresh in our minds, I wanted to write up a short recap of >> where we landed in the Application Credentials discussion in the BM/VM room >> today. F

Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

On Fri, Oct 13, 2017 at 9:21 PM, Zane Bitter wrote: > Replying to myself here, to avoid singling anyone in particular out. I > want to rephrase the question, because people are overwhelmingly either > failing to understand or refusing to answer it in the way I intended it. > > Most of the candida

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

On Fri, Oct 13, 2017 at 2:45 PM, Flavio Percoco wrote: > Greetings, > > Some of you, TC candidates, expressed concerns about diversity and > inclusiveness > (or inclusivity, depending on your taste) in your candidacy. I believe > this is a > broad, and some times ill-used, topic so, I'd like to k

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

partner with the foundation on. Colleen > > Congrats again, > > --diana > > On Sun, Oct 15, 2017 at 3:38 AM, Colleen Murphy > wrote: > > A major problem in the tech world is not just attracting underrepresented > > contributors, but retaining them. They leave th

Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?

On Tue, Oct 24, 2017 at 1:47 PM, Thierry Carrez wrote: > Colleen Murphy wrote: > > On Sat, Oct 21, 2017 at 9:00 AM, Diana Clarke > > mailto:diana.joan.cla...@gmail.com>> > wrote: > > > > Congrats on being elected to the TC, Colleen! > > > >

Re: [openstack-dev] [all] Dublin PTG format

On Mon, Nov 27, 2017 at 11:58 AM, Thierry Carrez wrote: > Hi everyone, > > We are in the final step in the process of signing the contract with the > PTG venue. We should be able to announce the location this week ! > > So it's time to start preparing. We'll have 5 days, like in Denver. One > thin

[openstack-dev] [keystone] Keystone weekly update - Week of 27 November 2017

In the "Making OpenStack More Palatable to Part-Time Contributors" Forum session in Sydney, one barrier to contribution that came up was keeping up with everything happening in OpenStack. The dev mailing list is a firehose and IRC can be just as daunting, especially for contributors in non-Americas

Re: [openstack-dev] [keystone] multiple federated keystones with single Identity Provider

On Thu, Dec 7, 2017 at 5:37 PM, Pavlo Shchelokovskyy wrote: > Hi all, > > We have a following use case - several independent keystones (say KeyA and > KeyB), using fernet tokens and synchronized fernet keys, and single external > IdP for federated auth. > > Is it generally possible to configure bo

[openstack-dev] Keystone Team Update - Week of 4 December 2017

# Keystone Team Update - Week of 4 December 2017 ## News ### Keystone Queens-2 Retrospective We used our meeting time for our milestone-ly team retrospective, which took place on Google Hangouts. We were unfortunately not able to record the session but the Trello board reflects the discussion to

Re: [openstack-dev] Keystone Team Update - Week of 4 December 2017

On Fri, Dec 8, 2017 at 6:58 PM, Jeremy Stanley wrote: > On 2017-12-08 18:48:56 +0100 (+0100), Colleen Murphy wrote: > [...] >> The major hindrance to keystone using Storyboard is its lack of >> support for private bugs, which is a requirement given that >> keystone is a

[openstack-dev] Keystone Team Update - Week of 18 December 2017

# Keystone Team Update - Week of 18 December 2017 ## News ### Unified Limits We accepted the Limits API spec[1] last week, for which we had made a spec freeze exception. ### Allowing control over project ID generation At our weekly meeting, we had a productive conversation[2] about a recurring

[openstack-dev] Keystone Team Update - Weeks of 25 December 2017 and 1 January 2018

# Keystone Team Update - Weeks of 25 December 2017 and 1 January 2018 ## News Happy new year! Things have been slow during the holiday season so not much to report. The policy meeting was short but we talked about starting up our investigations into other RBAC systems again. Lance kicked off a t

[openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

Hi everyone, We have governance review under debate[1] that we need the community's help on. The debate is over what recommendation the TC should make to the Interop team on where the tests it uses for the OpenStack trademark program should be located, specifically those for the new add-on program

[openstack-dev] [keystone] Keystone Team Update - Week of 8 January 2018

# Keystone Team Update - Week of 8 January 2018 ## News ### PTG We're still brainstorming for the PTG. If you have any topic proposals, please add them to the etherpad[1]. We'll need to coordinate with other teams to schedule discussion time on our major cross-project topics, especially unified

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

On Fri, Jan 19, 2018 at 1:52 AM, Ken'ichi Ohmichi wrote: > 2018-01-18 12:36 GMT-08:00 Doug Hellmann : >> >> I feel pretty sure that was discussed in a TC meeting, but I can't >> find that. I do find Matt and Ken'ichi voting +1 on the resolution >> itself. https://review.openstack.org/#/c/312718/.

[openstack-dev] [keystone] Keystone Team Update - Week of 15 January 2018

# Keystone Team Update - Week of 15 January 2018 ## News ### Core team changes We added a new core reviewer! Thanks Gage Hugo for all your hard work and for stepping up to take on more responsibility! We also lost some core members: Boris Bobrov, Steve Martinelli, Brant Knudson and Brad Topol h

Re: [openstack-dev] [keystone] FFE for unified limits

+1 On Thu, Jan 25, 2018 at 10:14 PM, Lance Bragstad wrote: > Hey all, > > The work for unified limits [0] has been up for a while, reviewers are > happy with it being experimental, and it is slowly making it's way > through the gate. I propose we consider a feature freeze exception given > the st

Re: [openstack-dev] [keystone] FFE for application credentials

+1 On Thu, Jan 25, 2018 at 10:15 PM, Lance Bragstad wrote: > Hey all, > > The work for application credentials [0] has been up for a while, > reviewers are happy with it, and it is slowly making it's way through > the gate. I propose we consider a feature freeze exception given the > state of the

Re: [openstack-dev] [keystone] FFE for application credentials

+1 On Thu, Jan 25, 2018 at 10:15 PM, Lance Bragstad wrote: > Hey all, > > The work for system assignments and system scope [0] has been up for a > while, reviewers are happy with it, and it is slowly making it's way > through the gate. I propose we consider a feature freeze exception given > the

[openstack-dev] [keystone] Keystone Team Update - Week of 22 January 2018

# Keystone Team Update - Week of 22 January 2018 ## News ### Feature freeze This week was feature freeze and client freeze. While we approved everything we cared about for this release on time, some CI issues (some unexpected and some predictable) delayed these features being merged. The release

Re: [openstack-dev] [keystone] FFE for application credentials

> On Thu, Jan 25, 2018 at 10:15 PM, Lance Bragstad wrote: >> Hey all, >> >> The work for application credentials [0] has been up for a while, >> reviewers are happy with it, and it is slowly making it's way through >> the gate. I propose we consider a feature freeze exception given the >> state of

Re: [openstack-dev] [puppet] Puppet OpenStack PTL non-candidacy

Emilien, Thank you so much for your incredible work on this project. The deployment tools and OpenStack itself is in a better state because of your work. I'm glad to work with you and call you a friend. Colleen On Fri, Sep 9, 2016 at 9:05 AM, Emilien Macchi wrote: > Hi, > > I wrote a little bl

[openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

At the last PTG we had some time on Monday and Tuesday for cross-project discussions related to baremetal and VM management. We don't currently have that on the schedule for this PTG. There is still some free time available that we can ask for[1]. Should we try to schedule some time for this? From

Re: [openstack-dev] [keystone][nova][ironic][heat] Do we want a BM/VM room at the PTG?

On Wed, Jan 31, 2018 at 6:46 PM, Graham Hayes wrote: > On 31/01/18 17:22, Dmitry Tantsur wrote: >> On 01/31/2018 06:15 PM, Matt Riedemann wrote: >>> On 1/30/2018 9:33 AM, Colleen Murphy wrote: [snip] >>> >>> These all seem like good topics for big cross-proj

[openstack-dev] [keystone] Keystone Team Update - Weeks of 29 January and 5 February 2018

# Keystone Team Update - Weeks of 29 January and 5 February 2018 It's been a busy couple of weeks and I missed the last update, here's an update for the last two weeks. ## News ### RC1 RC1 was cut today[1]. We expect to release an RC2 after branching since we have a translations patch and a cou

Re: [openstack-dev] [all][Kingbird][Heat][Glance]Multi-Region Orchestrator

On Mon, Feb 12, 2018 at 7:44 AM, Goutham Pratapa wrote: > > OUR USE-CASES QUOTA-MANAGEMENT: > > 1. Admin must have a global view of all quotas to all tenants across all the > regions > 2. Admin can periodically balance the quotas (we have a formula using which > we do this balancing ) across regi

[openstack-dev] [keystone] Keystone Team Update - Week of 12 February 2018

# Keystone Team Update - Week of 12 February 2018 ## News Relatively quiet week, the big news is that we're on track for a solid RC2 next week :) ## Recently Merged Changes Search query: https://goo.gl/hdD9Kw We merged 37 changes this week. The most significant of these were Queens backports f

[openstack-dev] [keystone] Keystone Team Update - Week of 5 March 2018

# Keystone Team Update - Week of 5 March 2018 ## News ### PTG Summaries Last week many of us attended the PTG in Dublin and made significant progress on a lot of keystone topics. Here are some recaps: - https://www.lbragstad.com/blog/keystone-rocky-ptg-summary - http://www.gazlene.net/dubl

[openstack-dev] [keystone] Keystone Team Update - Week of 12 March 2018

# Keystone Team Update - Week of 12 March 2018 ## News ### Keystone Admin-ness: the Future At the Denver PTG, while grappling with the concept of admin-ness, we had a moment of clarity when we realized that there were some classes of admin actions that could be described as "global" across key

[openstack-dev] [keystone] Keystone Team Update - Week of 19 March 2018

# Keystone Team Update - Week of 19 March 2018 ## News ### Spec review meeting During our Tuesday office hours we had a call to discuss some of our open specs. We were able to reduce some of the scope creep that had arisen in the application credentials enhancement spec[1], iron out some detai

[openstack-dev] [keystone] Keystone Team Update - Week of 26 March 2018

# Keystone Team Update - Week of 26 March 2018 ## News ### JSON Web Tokens Lance found an interesting article denouncing JWT[1][2] which, in an ironic twist, also advocated fernet as an alternative. We're still plowing forward on the JWT spec[3], but we need to be very precise in our design an

[openstack-dev] [keystone] Keystone Team Update - Week of 2 April 2018

# Keystone Team Update - Week of 2 April 2018 ## News Relatively quiet week. Most of our activity was focused on polishing up specs. ## Open Specs Search query: https://goo.gl/eyTktx No new specs have been proposed since last week. We're getting some good feedback on the cross-project spec to

[openstack-dev] [keystone] Keystone Team Update - Week of 16 April 2018

# Keystone Team Update - Week of 16 April 2018 ## News ### Retrospective scheduled We're planning on having our milestonely team retrospective next week immediately after the weekly meeting[1]. We usually do this as a video conference. Come with your feedback! [1] http://lists.openstack.org/p

Re: [openstack-dev] Summit Forum Schedule

Hi Jimmy, On Wed, Apr 25, 2018, at 11:07 PM, Jimmy McArthur wrote: > Hi everyone - > > Please have a look at the Vancouver Forum schedule: > https://docs.google.com/spreadsheets/d/15hkU0FLJ7yqougCiCQgprwTy867CGnmUvAvKaBjlDAo/edit?usp=sharing > > (also attached as a CSV) The proposed schedule w

[openstack-dev] [keystone] Keystone Team Update - Week of 23 April 2018

# Keystone Team Update - Week of 23 April 2018 ## News ### scope_types in nova We've had some good discussions incorporating scope_types into nova [0]. Thanks to mriedem and jaypipes for helping out. The discussion flushed out some work needed in keystonemiddleware [1] and oslo.context [2], ma

[openstack-dev] [keystone] Keystone Team Update - Week of 7 May 2018

# Keystone Team Update - Week of 7 May 2018 ## News ### Patrole in CI With all the work that has been happening around fixing policy, it would be good to have better policy validation in CI[1]. However, there are some concerns that using Patrole in a voting gate job will lock us in to unwanted

[openstack-dev] [keystone] Keystone Team Update - Week of 14 May 2018

# Keystone Team Update - Week of 14 May 2018 ## News ### WSGI Morgan has been working on converting keystone's core application to use Flask[1], which will help us to stop using paste.deploy and simplify our WSGI middleware and routing. While we're reworking our WSGI application framework, we

Re: [openstack-dev] [StarlingX] StarlingX code followup discussions

On Tue, May 22, 2018, at 10:57 PM, Jay Pipes wrote: > > Are any of the distributions of OpenStack listed at > https://www.openstack.org/marketplace/distros/ hosted on openstack.org > infrastructure? No. And I think that is completely appropriate. Hang on, that's not quite true. From that list I

Re: [openstack-dev] [StarlingX] StarlingX code followup discussions

On Wed, May 23, 2018, at 8:07 PM, Dean Troyer wrote: > On Wed, May 23, 2018 at 11:49 AM, Colleen Murphy wrote: > > It's also important to make the distinction between hosting something on > > openstack.org infrastructure and recognizing it in an official capacity. >

Re: [openstack-dev] [keystone] Signing off

On Wed, May 30, 2018, at 10:45 AM, Henry Nash wrote: > Hi > > It is with a somewhat heavy heart that I have decided that it is time to > hang up my keystone core status. Having been involved since the closing > stages of Folsom, I've had a good run! When I look at how far keystone > has come sinc

[openstack-dev] [keystone] Keystone Team Update - Week of 28 May 2018

# Keystone Team Update - Week of 28 May 2018 ## News ### Summit Recap We had a productive summit last week. Lance has posted a recap[1]. [1] https://www.lbragstad.com/blog/openstack-summit-vancouver-recap ### Quota Models There was a productive discussion at the forum on hierarchical quotas (

[openstack-dev] [keystone] Keystone Team Update - Week of 11 June 2018

# Keystone Team Update - Week of 11 June 2018 ## News ### New Implied Roles in keystone-manage bootstrap We landed one of the first building blocks for Default Roles across OpenStack, which is ensuring they are created during the bootstrap of keystone[1]. Since this is new feature of the boots

[openstack-dev] [keystone] Keystone Team Update - Week of 18 June 2018

# Keystone Team Update - Week of 18 June 2018 ## News ### Default Roles Fallout Our change to automatically create the 'reader' and 'member' roles during bootstrap[1] caused some problems in the CI of other projects[2]. One problem was that projects were manually creating a 'Member' role, and

[openstack-dev] [keystone] Keystone Team Update - Week of 25 June 2018

# Keystone Team Update - Week of 25 June 2018 ## News ### Policy Auditing Auditing the keystone APIs and resolving what roles they need under which scope types is the next step in implementing basic default roles. This was already done for barbican but we still need to go through the exercise

[openstack-dev] [keystone] Keystone Team Update - Week of 2 July 2018

# Keystone Team Update - Week of 2 July 2018 ## News Fairly quiet week due to the holiday in the US. During the weekly meeting[1] we did some brainstorming about how to address the mutable config community goal[2], and extending oslo.policy types in order to be able to make finer-grained rules

[openstack-dev] [keystone] Keystone Team Update - Week of 9 July 2018

# Keystone Team Update - Week of 9 July 2018 ## News ### New Core Reviewer We added a new core reviewer[1]: thanks to XiYuan for stepping up to take this responsibility and for all your hard work on keystone! [1] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132123.html ### Rel

Re: [openstack-dev] [keystone] Feature Status and Exceptions

On Fri, Jul 13, 2018, at 9:19 PM, Lance Bragstad wrote: > Hey all, > > As noted in the weekly report [0], today is feature freeze for > keystone-related specifications. I wanted to elaborate on each > specification so that our plan is clear moving forward. > > *Unified Limits** > ** > *I propose

Re: [openstack-dev] PTG Denver Horns

On Wed, Aug 8, 2018, at 12:18 PM, Adam Spiers wrote: > Matthew Thode wrote: > >On 18-08-07 23:18:26, David Medberry wrote: > >> Requests have finally been made (today, August 7, 2018) to end the horns on > >> the train from Denver to Denver International airport (within the city > >> limits of Den

[openstack-dev] [keystone] Keystone Team Update - Week of 6 August 2018

# Keystone Team Update - Week of 6 August 2018 ## News ### RC1 We released RC1 this week[1]. Please try it out and be on the lookout for critical bugs. As of yet we don't seem to have any showstoppers that would require another RC. [1] https://releases.openstack.org/rocky/index.html#rocky-key

Re: [openstack-dev] [keystone] Keystone Team Update - Week of 6 August 2018

On Sat, Aug 11, 2018, at 11:14 AM, Lance Bragstad wrote: > On Fri, Aug 10, 2018, 23:47 Colleen Murphy wrote: > > > # Keystone Team Update - Week of 6 August 2018 > > > > ## News > > > > ### RC1 > > > > We released RC1 this week[1]. Please try it

[openstack-dev] Keystone Team Update - Week of 13 Auguest 2018

# Keystone Team Update - Week of 13 Auguest 2018 ## News Relatively quiet week with minimal fires. Prepare for the PTG by adding topics to the etherpad[1]. [1] https://etherpad.openstack.org/p/keystone-stein-ptg ## Recently Merged Changes Search query: https://bit.ly/2IACk3F We merged 27 cha

  1   2   >