Re: [openstack-dev] [nova][cinder] about unified limits

://review.openstack.org/#/q/project:openstack/oslo.limit+status:open On Tue, Sep 11, 2018 at 8:10 AM Lance Bragstad wrote: > Extra eyes on the API would be appreciated. We're also close to the point > where we can start incorporating oslo.limit into services, so preparing > those changes might be us

[openstack-dev] [keystone] No meeting 13 Nov 2018

Just a reminder that we won't be holding a weekly meeting for keystone next week due to the OpenStack Summit in Berlin. Meetings will resume on the 20th of November. Thanks, Lance __ OpenStack Development Mailing List (not

[openstack-dev] [keystone] Berlin Forum Sessions & Talks

Hey all, Here is what's on my radar for keystone-specific sessions and talks next week: *Tuesday* - Change ownership of resources [0] - Keystone Project Update [1] - OpenStack Policy 101 [2] - Keystone Project Onboarding [3] - Gaps between OpenStack and business logic with Adjutant [4]

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On Wed, Oct 24, 2018 at 2:49 PM Jay Pipes wrote: > On 10/24/2018 02:57 PM, Matt Riedemann wrote: > > On 10/24/2018 10:10 AM, Jay Pipes wrote: > >> I'd like to propose deprecating this API and getting rid of this > >> functionality since it conflicts with the new Keystone /limits > >> endpoint,

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

, Oct 13, 2018 at 6:07 AM Ghanshyam Mann wrote: > On Sat, 13 Oct 2018 01:45:17 +0900 Lance Bragstad < > lbrags...@gmail.com> wrote > > Sending a follow up here quick. > > The reviewers actively participating in [0] are nearing a conclusion. > Ultimate

Re: [openstack-dev] [glance][upgrade-checkers] Question about glance rocky upgrade release note

I haven't implemented any checks, but I did take a shot at laying down the scaffolding for implementing upgrade checks in glance [0]. Anyone who is more familiar with glance should be able to build off of that commit by implementing specific checks in glance/cmd/status.py [0]

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

On Mon, Oct 15, 2018 at 8:52 AM Ed Leafe wrote: > On Oct 15, 2018, at 7:40 AM, Chris Dent wrote: > > > > I'd like some input from the community on how we'd like this to go. > > I would say it depends on the long-term plans for paste. Are we planning > on weaning ourselves off of paste, and

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

://review.openstack.org/#/c/606214/ On Mon, Oct 8, 2018 at 8:49 AM Lance Bragstad wrote: > > On Mon, Oct 1, 2018 at 8:13 AM Ghanshyam Mann > wrote: > >> On Sat, 29 Sep 2018 03:54:01 +0900 Lance Bragstad < >> lbrags...@gmail.com> wrote >> > >> &g

Re: [openstack-dev] [oslo][glance][cinder][keystone][requirements] blocking oslo.messaging 9.0.0

On Tue, Oct 9, 2018 at 10:56 AM Doug Hellmann wrote: > Matthew Thode writes: > > > On 18-10-09 11:12:30, Doug Hellmann wrote: > >> Matthew Thode writes: > >> > >> > several projects have had problems with the new release, some have > ways > >> > of working around it, and some do not. I'm

Re: [openstack-dev] [oslo][glance][cinder][keystone][requirements] blocking oslo.messaging 9.0.0

On Tue, Oct 9, 2018 at 10:31 AM Ben Nemec wrote: > > > On 10/9/18 9:06 AM, Lance Bragstad wrote: > > Keystone is failing because it's missing a fix from oslo.messaging [0]. > > That said, keystone is also relying on an internal implementation detail > > in oslo.messa

Re: [openstack-dev] [oslo][glance][cinder][keystone][requirements] blocking oslo.messaging 9.0.0

Keystone is failing because it's missing a fix from oslo.messaging [0]. That said, keystone is also relying on an internal implementation detail in oslo.messaging by mocking it in tests [1]. The notification work has been around in keystone for a *long* time, but it's apparent that we should

Re: [openstack-dev] [tc] assigning new liaisons to projects

On Mon, Oct 8, 2018 at 9:27 AM Doug Hellmann wrote: > TC members, > > Since we are starting a new term, and have several new members, we need > to decide how we want to rotate the liaisons attached to each our > project teams, SIGs, and working groups [1]. > > Last term we went through a period

Re: [openstack-dev] [tc] bringing back formal TC meetings

On Mon, Oct 8, 2018 at 9:08 AM Doug Hellmann wrote: > Based on the conversation in the other branch of this thread, I have > filed [1] to start monthly meetings on November 1 at 1400 UTC. It may > take a while before that actually shows up on the calendar, because it > required adding a feature

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

On Mon, Oct 1, 2018 at 8:13 AM Ghanshyam Mann wrote: > On Sat, 29 Sep 2018 03:54:01 +0900 Lance Bragstad < > lbrags...@gmail.com> wrote > > > > On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki > wrote: > > On Fri, Sep 28, 2018 at 1:5

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

28, 2018 at 3:33 PM Sean McGinnis wrote: > On Fri, Sep 28, 2018 at 01:54:01PM -0500, Lance Bragstad wrote: > > On Fri, Sep 28, 2018 at 1:03 PM Harry Rybacki > wrote: > > > > > On Fri, Sep 28, 2018 at 1:57 PM Morgan Fainberg > > > wrote: > > > > &g

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

resources are always singular Thanks to all for sticking through this tedious discussion. I appreciate it. > > /R > > Harry > > > > On Fri, Sep 28, 2018 at 6:49 AM Lance Bragstad > wrote: > >> > >> Bumping this thread again and proposing two c

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

Adding the operator list back in. On Fri, Sep 28, 2018 at 8:48 AM Lance Bragstad wrote: > Bumping this thread again and proposing two conventions based on the > discussion here. I propose we decide on one of the two following > conventions: > > *::* > >

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

Lance Bragstad wrote: > > On Fri, Sep 21, 2018 at 2:10 AM Ghanshyam Mann > wrote: > >> On Thu, 20 Sep 2018 18:43:00 +0900 John Garbutt < >> j...@johngarbutt.com> wrote >> > tl;dr+1 consistent names >> > I would make the names mirror the A

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

but more of a question of which subcommands we should aim to support in OSC. > > > > The *-manage commands such as nova-manage, I would consider, out of scope > for OSC. Only admins would be migrating between versions or DB schemas. > > > > Tim > > > > *Fr

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] [cinder][glance][ironic][keystone][neutron][nova][edge] PTG summary on edge discussions

For those who may be following along and are not familiar with what we mean by federated auto-provisioning [0]. [0] https://docs.openstack.org/keystone/latest/advanced-topics/federation/federated_identity.html#auto-provisioning On Wed, Sep 26, 2018 at 9:06 AM Morgan Fainberg wrote: > This

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

On Mon, Sep 24, 2018 at 9:31 AM Colleen Murphy wrote: > On Mon, Sep 24, 2018, at 4:16 PM, Lance Bragstad wrote: > > On Mon, Sep 24, 2018 at 7:00 AM Colleen Murphy > wrote: > > > > > This is in regard to https://launchpad.net/bugs/1641625 and the &

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

On Mon, Sep 24, 2018 at 7:00 AM Colleen Murphy wrote: > This is in regard to https://launchpad.net/bugs/1641625 and the proposed > patch https://review.openstack.org/588211 for it. Thanks Vishakha for > getting the ball rolling. > > tl;dr: Keystone as an IdP should support sending >

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

the API, not the codeIgnore the crazy names in Nova, I certainly > hate them > > Big +1 on consistent naming which will help operator as well as developer > to maintain those. > > > > > Lance Bragstad wrote: > > > I'm curious if anyone has context on the "

Re: [openstack-dev] [Openstack-sigs] [all][tc] We're combining the lists! (was: Bringing the community together...)

On Thu, Sep 20, 2018 at 7:19 PM Sean McGinnis wrote: > On Thu, Sep 20, 2018 at 03:46:43PM -0600, Doug Hellmann wrote: > > Excerpts from Jeremy Stanley's message of 2018-09-20 16:32:49 +: > > > tl;dr: The openstack, openstack-dev, openstack-sigs and > > > openstack-operators mailing lists (to

Re: [openstack-dev] [keystone] noop role in openstack

On Thu, Sep 20, 2018 at 12:22 AM Adrian Turjak wrote: > For Adam's benefit continuing this a bit in email: > > regarding the noop role: > > > http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-09-20.log.html#t2018-09-20T04:13:43 > > The first benefit of such

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

naming convention? [0] https://service-types.openstack.org/service-types.json [1] https://gist.github.com/lbragstad/5000b46f27342589701371c88262c35b#file-policy-names-yaml On Sun, Sep 16, 2018 at 9:47 PM Lance Bragstad wrote: > If we consider dropping "os", should we entertain drop

Re: [openstack-dev] [Openstack-sigs] [tc][uc]Community Wide Long Term Goals

On Tue, Sep 18, 2018 at 12:17 PM Doug Hellmann wrote: > Excerpts from Lance Bragstad's message of 2018-09-18 11:56:22 -0500: > > On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann > > wrote: > > > > > Excerpts from Zhipeng Huang's message of 2018-09-14 18:51:40 -0600: > > > > Hi, > > > > > > > >

Re: [openstack-dev] [Openstack-sigs] [tc][uc]Community Wide Long Term Goals

On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann wrote: > Excerpts from Zhipeng Huang's message of 2018-09-14 18:51:40 -0600: > > Hi, > > > > Based upon the discussion we had at the TC session in the afternoon, I'm > > starting to draft a patch to add long term goal mechanism into > governance. >

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

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

[openstack-dev] [keystone] Rocky Retrospective

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

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

rg wrote: > I am generally opposed to needlessly prefixing things with "os". > > I would advocate to drop it. > > > On Fri, Sep 14, 2018, 20:17 Lance Bragstad wrote: > >> Ok - yeah, I'm not sure what the history behind that is either... >> >> I'm mainly cur

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

rowing this from existing code examples[0]. > > [0] > http://specs.openstack.org/openstack/nova-specs/specs/newton/implemented/policy-in-code.html > > Michael > On Fri, Sep 14, 2018 at 8:46 AM Lance Bragstad > wrote: > > > > > > > > On Thu, Sep 13, 2018

Re: [openstack-dev] [Openstack-operators] [all] Consistent policy names

cer > > Michael > On Wed, Sep 12, 2018 at 12:52 PM Tim Bell wrote: > > > > So +1 > > > > > > > > Tim > > > > > > > > From: Lance Bragstad > > Reply-To: "OpenStack Development Mailing List (not for usage quest

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

On Wed, Sep 12, 2018 at 3:55 PM Jeremy Stanley wrote: > On 2018-09-12 09:47:27 -0600 (-0600), Matt Riedemann wrote: > [...] > > So I encourage all elected TC members to work directly with the > > various SIGs to figure out their top issue and then work on > > managing those deliverables across

[openstack-dev] [all] Consistent policy names

The topic of having consistent policy names has popped up a few times this week. Ultimately, if we are to move forward with this, we'll need a convention. To help with that a little bit I started an etherpad [0] that includes links to policy references, basic conventions *within* that service, and

Re: [openstack-dev] [nova][cinder] about unified limits

rst we should the keystone unified limits api really ok or > something else ? > > Lance Bragstad 于2018年9月8日周六 上午2:35写道： > > > > That would be great! I can break down the work a little bit to help > describe where we are at with different parts of the initiative. Hopefull

Re: [openstack-dev] [election][tc] Opinion about 'PTL' tooling

I agree in that it's dependent on what metrics you think accurately showcase project health. Is it the number of contributions? The number of unique contributors? Diversity across participating organizations? Completion ratios of blueprints or committed fixes over bugs opened? I imagine different

[openstack-dev] [keystone] Keystone Team Update - Week of 3 September 2018

-keystoneclient:Undecided) opened by ChenWu https://bugs.launchpad.net/python-keystoneclient/+bug/1790423 - Bug #1790931 (oslo.limit:Medium) opened by Lance Bragstad https://bugs.launchpad.net/oslo.limit/+bug/1790931 - Bug #1790954 (oslo.limit:Medium) opened by Lance Bragstad https://bugs.launchpad.net

Re: [openstack-dev] [nova][cinder] about unified limits

/rocky/strict-two-level-enforcement-model.html [4] https://review.openstack.org/#/q/project:openstack/oslo.limit+status:open [5] https://review.openstack.org/#/c/600265/ [6] http://logs.openstack.org/65/600265/3/check/openstack-tox-docs/a6bcf38/html/user/usage.html On Thu, Sep 6, 2018 at 8:56 PM Jaze Lee w

Re: [openstack-dev] [stable][keystone] python3 goal progress and tox_install.sh removal

wrote: > On Thu, Sep 06, 2018 at 03:01:01PM -0500, Lance Bragstad wrote: > > I'm noticing some odd cases with respect to the python 3 community goal > > [0]. So far my findings are specific to keystone repositories, but I can > > imagine this affecting other projects. &

[openstack-dev] [keystone] 2018 User Survey Results

The foundation just gave me a copy of the latest feedback from our users. I wanted to share this with the group so people have time to digest it prior to the PTG next week [0]. Here is the total count based on each response: Federated identity enhancements had *184* responses Performance

[openstack-dev] [stable][keystone] python3 goal progress and tox_install.sh removal

I'm noticing some odd cases with respect to the python 3 community goal [0]. So far my findings are specific to keystone repositories, but I can imagine this affecting other projects. Doug generated the python 3 reviews for keystone repositories, including the ones for stable branches. We noticed

[openstack-dev] [keystone] No meeting or office hours September 11th

I wanted to send out a reminder that we won't be having formal office hours or a team meeting next week due to the PTG. Both will resume on the 18th of September. Thanks, Lance __ OpenStack Development Mailing List (not for

[openstack-dev] [keystone] Stein Forum Brainstorming

I can't believe it's already time to start thinking about forum topics, but it's upon us [0]! I've created an etherpad for us to brainstorm ideas that we want to bring to the forum in Germany [1]. I also linked it to the wiki [2]. Please feel free to throw out ideas. We can go through them as a

Re: [openstack-dev] [nova][cinder] about unified limits

one service? > Is there some methods to move this more fast? > Lance Bragstad 于2018年9月5日周三 下午9:29写道： > > > > Not yet. Keystone worked through a bunch of usability improvements with > the unified limits API last release and created the oslo.limit library. We > have a patch or two

Re: [openstack-dev] [nova][cinder] about unified limits

Not yet. Keystone worked through a bunch of usability improvements with the unified limits API last release and created the oslo.limit library. We have a patch or two left to land in oslo.limit before projects can really start using unified limits [0]. We're hoping to get this working with at

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

Hi all, I'd like to submit my candidacy to be a member of the OpenStack Technical Committee. My involvement with OpenStack began during the Diablo release. Since then I've participated in various parts of the community, in both upstream and downstream roles. Today I mainly focus on

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

# Keystone Team Update - Week of 27 August 2018 ## News Welcome to Stein development! ## Release Status Well, Rocky went out the door. A friendly reminder to keep an eye out for bugs and things we should backport. ## PTG Planning The topics in the PTG etherpad have been worked into a

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

Juan Antonio Osorio Robles < jaosor...@redhat.com> wrote: > FWIW, instead of barbican, castellan could be used as a key manager. > > On 08/30/2018 12:23 PM, Adrian Turjak wrote: > > > On 30/08/18 6:29 AM, Lance Bragstad wrote: > > Is that what is being described here ?

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

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] [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 >

[openstack-dev] [keystone] Stein PTG Schedule

I've worked through the list of topics and organized them into a rough schedule [0]. As it stands right now, Monday is going to be the main cross-project day (similar to the identity-integration track in Dublin). We don't have a room on Tuesday and Wednesday, but we will likely have continued

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

On 08/22/2018 07:49 AM, Lance Bragstad wrote: > > On 08/22/2018 03:23 AM, Adrian Turjak wrote: >> Bah! I saw this while on holiday and didn't get a chance to respond, >> sorry for being late to the conversation. >> >> On 11/08/18 3:46 AM, Colleen Murphy wrote:

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

ack-dev/2018-August/133610.html > > ## Bugs > > This week we opened 4 new bugs and closed 1. > > Bugs opened (4)  > Bug #1788415 (keystone:High) opened by Lance Bragstad > https://bugs.launchpad.net/keystone/+bug/1788415  > Bug #1788694 (keystone:High) op

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

On 08/22/2018 03:23 AM, Adrian Turjak wrote: > Bah! I saw this while on holiday and didn't get a chance to respond, > sorry for being late to the conversation. > > On 11/08/18 3:46 AM, Colleen Murphy wrote: >> ### Self-Service Keystone >> >> At the weekly meeting Adam suggested we make

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

d 3. There don't currently seem to > be any showstopper bugs for Rocky. orange_julius has been chasing a fun, > apparently longstanding bug in ldappool[15], our traditionally low-effort > adopted project. > > Bugs opened (2) > Bug #1786383 (keystone:Undecided) opened by Liyingjun > https://bug

Re: [openstack-dev] [nova][placement][oslo] Excessive WARNING level log messages in placement-api

On 08/09/2018 12:48 PM, Doug Hellmann wrote: > Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500: >> On 8/9/2018 11:47 AM, Doug Hellmann wrote: >>> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400: For evidence, see:

Re: [openstack-dev] [nova][placement][oslo] Excessive WARNING level log messages in placement-api

On 08/09/2018 12:18 PM, Matt Riedemann wrote: > On 8/9/2018 11:47 AM, Doug Hellmann wrote: >> Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400: >>> For evidence, see: >>> >>>

Re: [openstack-dev] Paste unmaintained

On 08/02/2018 09:36 AM, Chris Dent wrote: > On Thu, 2 Aug 2018, Stephen Finucane wrote: > >> Given that multiple projects are using this, we may want to think about >> reaching out to the author and seeing if there's anything we can do to >> at least keep this maintained going forward. I've

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

# Keystone Team Update - Week of 30 July 2018 ## News This week was relatively quiet, but we're working towards RC1 as our next deadline. ## Recently Merged Changes Search query: https://bit.ly/2IACk3F We merged 20 changes this week. Mainly changes to continue moving APIs to flask and we

[openstack-dev] [keystone] Prospective RC1 Bugs

Hey all, I went through all bugs opened during the Rocky release and came up with a list of ones that might be good to fix before next week [0]. The good news is that more than half are in progress and none of them are release blockers, just ones that would be good to get in. Let me know if you

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

# Keystone Team Update - Week of 23 July 2018 ## News This week wrapped up rocky-3, but the majority of the things working through review are refactors that aren't necessarily susceptible to the deadline. ## Recently Merged Changes Search query: https://bit.ly/2IACk3F We merged 32 changes

[openstack-dev] [keystone] PTL Candidacy for the Stein cycle

Hey everyone, I'm writing to submit my self-nomination as keystone's PTL for the Stein release. We've made significant progress tackling some of the major goals we set for keystone in Pike. Now that we're getting close to wrapping up some of those initiatives, I'd like to continue advocating for

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

pened by Pawan Gupta > https://bugs.launchpad.net/keystone/+bug/1781536 > > Bugs closed (0) > > Bugs fixed (4) > Bug #1765193 (keystone:Medium) fixed by wangxiyuan > https://bugs.launchpad.net/keystone/+bug/1765193 > Bug #1780159 (keystone:Medium) fixed by S

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

On 07/13/2018 02:37 PM, Harry Rybacki wrote: > On Fri, Jul 13, 2018 at 3:20 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 &

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

On 07/13/2018 03:37 PM, Johannes Grassler wrote: > Hello, > > On Fri, Jul 13, 2018 at 02:19:35PM -0500, Lance Bragstad wrote: >> *Capability Lists** >> * >> The capability lists involves a lot of work, not just within keystone, >> but also keystonemiddleware, whi

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

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 that we issue a feature freeze exception for this work. Mainly because

[openstack-dev] [keystone] Stein PTG Planning Etherpad

It's getting to be that time of the release (and I'm seeing other etherpads popping up on the mailing list). I've created one specifically for keystone [0]. Same drill as the last two PTGs. We'll start by just getting topics written down and I'll group similar topics into buckets prior to

[openstack-dev] [keystone] Adding Wangxiyuan to keystone core

Hi all, Today we added Wangxiyuan to the keystone core team [0]. He's been doing a bunch of great work over the last couple releases and has become a valuable reviewer [1][2]. He's also been instrumental in pushing forward the unified limits work not only in keystone, but across projects. Thanks

Re: [openstack-dev] [tc] [all] TC Report 18-26

On 06/28/2018 02:09 PM, Fox, Kevin M wrote: > I'll weigh in a bit with my operator hat on as recent experience it pertains > to the current conversation > > Kubernetes has largely succeeded in common distribution tools where OpenStack > has not been able to. > kubeadm was created as a way

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

thub.com/oauthlib/oauthlib/issues/558 [1] https://review.openstack.org/#/c/577974/ > >> Doug >> >>> On 06/25/2018 07:27 PM, Tony Breeds wrote: >>>> On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote: >>>>> Keystone is hitting this, to

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

://review.openstack.org/#/c/577974/ On 06/25/2018 07:27 PM, Tony Breeds wrote: > On Mon, Jun 25, 2018 at 05:42:00PM -0500, Lance Bragstad wrote: >> Keystone is hitting this, too [0]. I attempted the same solution that >> Tony posted, but no luck. I've even gone so far as removing every

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

Keystone is hitting this, too [0]. I attempted the same solution that Tony posted, but no luck. I've even gone so far as removing every comment from the module to see if that helps narrow down the problem area, but sphinx still trips. The output from the error message isn't very descriptive

[openstack-dev] [all] default and implied roles changes

Hi all, Keystone recently took a big step in implementing the default roles work that's been a hot topic over the past year [0][1][2][3][4], and a big piece in making RBAC more robust across OpenStack. We merged a patch [5] that ensures the roles described in the specification [6] exist. This was

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

opened 7 new bugs, closed 5, and fixed 5. Bugs opened (7) Bug #1775094 (keystone:Medium) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1775094 Bug #1774654 (keystone:Undecided) opened by Wyllys Ingersoll https://bugs.launchpad.net/keystone/+bug/1774654 Bug #1774688

[openstack-dev] [keystone] test storyboard environment

Hi all, The StoryBoard team was nice enough to migrate existing content for all keystone-related launchpad projects to a dev environment [0]. This gives us the opportunity to use  StoryBoard with real content. Log in and check it out. I'm curious to know what the rest of the team thinks. [0]

Re: [openstack-dev] Questions about token scopes

It looks like I had a patch up to improve some developer documentation that is relevant to this discussion [0]. [0] https://review.openstack.org/#/c/554727/ On 06/01/2018 08:01 AM, Jens Harbott wrote: > 2018-05-30 20:37 GMT+00:00 Matt Riedemann : >> On 5/30/2018 9:53 AM, Lance Brags

[openstack-dev] [keystone] failing documentation jobs

Hi all, If you've been trying to write documentation patches, you may have noticed them tripping over unrelated errors when building the docs. We have a bug opened detailing why this happened [0] and a fix working its way through the gate [1]. The docs job should be back up and running soon. [0]

Re: [openstack-dev] Questions about token scopes

On 05/31/2018 12:09 AM, Ghanshyam Mann wrote: > On Wed, May 30, 2018 at 11:53 PM, Lance Bragstad wrote: >> >> On 05/30/2018 08:47 AM, Matt Riedemann wrote: >>> I know the keystone team has been doing a lot of work on scoped tokens >>> and Lance has been trying t

Re: [openstack-dev] Questions about token scopes

On 05/30/2018 03:37 PM, Matt Riedemann wrote: > On 5/30/2018 9:53 AM, Lance Bragstad wrote: >> While scope isn't explicitly denoted by an >> attribute, it can be derived from the attributes of the token response. >> > > Yeah, this was confusing to me, which is

Re: [openstack-dev] Questions about token scopes

On 05/30/2018 08:47 AM, Matt Riedemann wrote: > I know the keystone team has been doing a lot of work on scoped tokens > and Lance has been trying to roll that out to other projects (like nova). > > In Rocky the nova team is adding granular policy rules to the > placement API [1] which is a good

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

I remember when I first started contributing upstream, I spent a Saturday sending you internal emails asking about the intricacies of database migrations :) Since then you've give me (or I've stolen) a number of other tools and techniques. Thanks for everything you've done for this community,

Re: [openstack-dev] [keystone] team dinner

://urbansushi.com/ There is also other stuff close by like: http://steamworks.com/brew-pub https://www.cactusclubcafe.com/?utm_source=google-maps_medium=organic_campaign=coal-harbour Or if you've gone to a place you'd like to recommend, suggestions are welcome! On 05/18/2018 08:39 AM, Lance Bragstad

Re: [openstack-dev] [User-committee] [Forum] [all] [Stable] OpenStack is "mature" -- time to get serious on Maintainers -- Session etherpad and food for thought for discussion

Here is the link to the session in case you'd like to add it to your schedule [0]. [0] https://www.openstack.org/summit/vancouver-2018/summit-schedule/events/21759/openstack-is-mature-time-to-get-serious-on-maintainers On 05/17/2018 07:55 PM, Rochelle Grober wrote: > > Folks, > >   > > TL;DR > >

[openstack-dev] [keystone] project onboarding

Hey all, We've started an etherpad in an attempt to capture information prior to the on-boarding session on Monday [0]. If you're looking to get something specific out of the session, please let us know in the etherpad [1]. This will help us come to the session prepared and make the most of the

[openstack-dev] [keystone] team dinner

Hey all, I put together a survey to see if we can plan a night to have supper together [0]. I'll start parsing responses tomorrow and see what we can get lined up. Thanks and safe travels to Vancouver, Lance [0] https://goo.gl/forms/ogNsf9dUno8BHvqu1 signature.asc Description: OpenPGP

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

On 05/14/2018 05:46 PM, Doug Hellmann wrote: > Excerpts from Lance Bragstad's message of 2018-05-14 15:20:42 -0500: >> On 05/14/2018 02:24 PM, Doug Hellmann wrote: >>> Excerpts from Lance Bragstad's message of 2018-05-14 13:13:51 -0500: On 03/19/2018 09:22 AM, Jim Rollenhagen wrote: >

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

On 05/14/2018 02:24 PM, Doug Hellmann wrote: > Excerpts from Lance Bragstad's message of 2018-05-14 13:13:51 -0500: >> On 03/19/2018 09:22 AM, Jim Rollenhagen wrote: >>> On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann >> > wrote: >>> >>>

Re: [openstack-dev] [ALL][PTLs] Community Goals for Rocky: Toggle the debug option at runtime

On 03/19/2018 09:22 AM, Jim Rollenhagen wrote: > > On Sat, Mar 17, 2018 at 9:49 PM, Doug Hellmann > wrote: > > Both of those are good ideas. > > > Agree. I like the socket idea a bit more as I can imagine some > operators don't want

[openstack-dev] [forum] [keystone] default roles etherpad

Hey everyone, I've created an etherpad for the default roles discussion in Vancouver [0]. It currently contains basic context and some session goals. If you have any input or additional session goals, please don't hesitate to add to the etherpad. Thanks and hope to see you there, Lance [0]

[openstack-dev] [forum] [keystone] unified limits etherpad

Hi all, I've created an etherpad for the unified limits session at the forum [0]. I've bootstrapped it with some basic context so that we can spend as much time as possible on the session goals. If you have questions, comments, or additional session goals, please feel free to add them to the

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

On 05/11/2018 02:00 PM, Fox, Kevin M wrote: > Who are your users, what do they need, are you meeting those needs, and what > can you do to better things? > > If that can't be answered, how do you know if you are making progress or > staying relevant? > > Lines of code committed is not a metric

Re: [openstack-dev] [edge][keystone][forum]: Keystone edge brainstorming etherpad

On 05/10/2018 06:30 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote: > > Hi, > >   > > I’ve added some initial text to the Etherpad [1 > ] of > the Possible edge architectures for Keystone Forum session [2 >

Re: [openstack-dev] [tc] [nova] [octavia] [ironic] [keystone] [policy] Spec. Freeze Exception - Default Roles

/2018 03:16 PM, Lance Bragstad wrote: > > On 05/04/2018 02:55 PM, Harry Rybacki wrote: >> Greetings All, >> >> After a discussion in #openstack-tc[1] earlier today, the Keystone >> team is adjusting its approach in proposing default roles[2]. >> Subsequently, I h

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

# Keystone Team Update - Week of 30 April 2018 ## News Most of this week was spent firming up specification details. There were a couple good discussions on unified limits and the default role work we're targeting for the release. ## Open Specs Dashboard: https://tinyurl.com/yagxuyfr We had

Re: [openstack-dev] [tc] [nova] [octavia] [ironic] [keystone] [policy] Spec. Freeze Exception - Default Roles

On 05/04/2018 02:55 PM, Harry Rybacki wrote: > Greetings All, > > After a discussion in #openstack-tc[1] earlier today, the Keystone > team is adjusting its approach in proposing default roles[2]. > Subsequently, I have ported the current default roles specification > from openstack-specs[3] to

[openstack-dev] [keystone] [policy] no policy meeting today

Hi all, I'm going to cancel the policy meeting today since attendance has been waning the last month or two and there are no items on the agenda. We should discuss whether or not we want to continue using this meeting. At this point, most of the policy work is in helping projects consume

  1   2   3   4   5   >