Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

On Thu, Jan 19, 2017 at 8:29 PM, Joshua Harlow wrote: > Corey Bryant wrote: > >> >> Added [nova] and [oslo] to the subject. This is also affecting nova and >> oslo.middleware. I know Sean's initial response on the thread was that >> this shouldn't be a priority for ocata

Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

Corey Bryant wrote: Added [nova] and [oslo] to the subject. This is also affecting nova and oslo.middleware. I know Sean's initial response on the thread was that this shouldn't be a priority for ocata but we're completely blocked by it. Would those teams be able to prioritize a fix for

Re: [openstack-dev] [keystone] [nova] [glance] [oslo] webob 1.7

>> Reply: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org> >> Date: January 19, 2017 at 08:52:25 >> To: OpenStack Development Mailing List (not for usage questions) >> <openstack-dev@lists.openstack.org>

[openstack-dev] [keystone] [ptl] PTL candidacy for Pike

Greetings, I want to run for keystone PTL to facilitate an environment for others to grow and make meaningful changes so that we continue to build keystone into a more stable, scalable and performant project [0]. January marks my fifth anniversary working with OpenStack. In that time I've had

Re: [openstack-dev] [keystone] webob 1.7

> Date: January 19, 2017 at 08:52:25 > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [keystone] webob 1.7 > > > On Wed, Jan 18, 2017 at 9:08 AM, Ian Cordasco > > wrote: > >

Re: [openstack-dev] [keystone] webob 1.7

t;openstack-dev@lists.openstack.org> Subject:  Re: [openstack-dev] [keystone] webob 1.7 > On Wed, Jan 18, 2017 at 9:08 AM, Ian Cordasco > wrote: > > > -Original Message- > > From: Chuck Short > > Reply: OpenStack Development Mailing List (not for usage question

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

k Development Mailing List (not for usage questions); > openstack-operat...@lists.openstack.org > *Subject:* Re: [openstack-dev] [keystone] 2017-1-11 policy meeting > > > > Looping this into the operator's list, too! > > > > On Wed, Jan 18, 2017 at 2:13 PM, Lance Bragstad <

Re: [openstack-dev] [keystone] webob 1.7

; Date: January 18, 2017 at 08:01:46 > To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [keystone] webob 1.7 > > > Hi > > > > We have been expericing problems with newer versions of webob (webob > 1.7).

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

janvier 2017 23:16 To: OpenStack Development Mailing List (not for usage questions); openstack-operat...@lists.openstack.org Subject: Re: [openstack-dev] [keystone] 2017-1-11 policy meeting Looping this into the operator's list, too! On Wed, Jan 18, 2017 at 2:13 PM, Lance Bragstad <lbr

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Looping this into the operator's list, too! On Wed, Jan 18, 2017 at 2:13 PM, Lance Bragstad wrote: > Thanks to Morgan in today's policy meeting [0], we were able to shed some > light on the reasons for keystone having two policy files. The main reason > a second policy file

Re: [openstack-dev] [keystone] 2017-1-11 policy meeting

Thanks to Morgan in today's policy meeting [0], we were able to shed some light on the reasons for keystone having two policy files. The main reason a second policy file was introduced was to recenter RBAC around concepts introduced in the V3 API. The problem was that the policy file that came

Re: [openstack-dev] [keystone] webob 1.7

; Date: January 18, 2017 at 08:01:46 > To: OpenStack Development Mailing List > <openstack-dev@lists.openstack.org > <mailto:openstack-dev@lists.openstack.org>> > Subject: [openstack-dev] [keystone] webob 1.7 > > > Hi > > &g

Re: [openstack-dev] [keystone] webob 1.7

lists.openstack.org> > Date: January 18, 2017 at 08:01:46 > To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [keystone] webob 1.7 > > > Hi > > > > We have been expericing problems with newer versions of webob (w

Re: [openstack-dev] [keystone] webob 1.7

On 18-Jan 08:59, Chuck Short wrote: > Hi > > We have been expericing problems with newer versions of webob (webob 1.7). > Reading the changelog, it seems that the upstream developers have > introduced some backwards incompatibility with previous versions of webob > that seems to be hitting

Re: [openstack-dev] [keystone] webob 1.7

ck.org> Subject:  [openstack-dev] [keystone] webob 1.7 > Hi > > We have been expericing problems with newer versions of webob (webob 1.7). > Reading the changelog, it seems that the upstream developers have > introduced some backwards incompatibility with previous versions of webob &g

[openstack-dev] [keystone] webob 1.7

Hi We have been expericing problems with newer versions of webob (webob 1.7). Reading the changelog, it seems that the upstream developers have introduced some backwards incompatibility with previous versions of webob that seems to be hitting keystone and possibly other projects as well

[openstack-dev] [keystone] 2017-1-11 policy meeting

Hey folks, In case you missed the policy meeting today, we had a good discussion [0] around incorporating keystone's policy into code using the Nova approach. Keystone is in a little bit of a unique position since we maintain two different policy files [1] [2], and there were a lot of questions

[openstack-dev] [keystone] etherpad for ptg

keystoners, here is the link to the etherpad for the ptg: https://etherpad.openstack.org/p/keystone-pike-ptg here is a link to other project etherpads: https://wiki.openstack.org/wiki/PTG/Pike/Etherpads I'll announce this in our meeting today also. - steve

Re: [openstack-dev] [keystone] office hours starting January 6th

Heads up folks! Just sending out a friendly reminder that tomorrow will be our first office hour session of the new year. See everyone in #openstack-keystone tomorrow! On Wed, Dec 21, 2016 at 5:32 PM, Rodrigo Duarte wrote: > Thanks for the initiative! This is something

[openstack-dev] [keystone] documenting policy guidelines

We had another healthy discussion about policy today [0] and most of it revolved around documenting policy guidelines. The question of the day was where should these guidelines live? To answer that we highlighted the following criteria: - Guidelines should be proposed and reviewed in small

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

I quite like Boris' last suggestion, with a minor tweak: "In your opinion, what keystone feature(s) requires more attention (select all that apply): "federation", "performance", "policy", "scaling out", "backend support", "ldap"." Unless someone has another suggestion I'll stick to the above.

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

++ to the suggestions Boris threw out. Answers to any of those would be valuable. In addition to that, I'd find any information about policy useful. Maybe something along the lines of "what changes to the policy files are you making, if any". This could be something that is asked OpenStack-wide

Re: [openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

"What were you trying to accomplish with keystone but failed" "What functionality in keystone did you try to use but it wasn't good enough" "In your opinion, what in keystone requires most attention" with choices "federation", "performance", "policy", "backend support" and some other options. On

[openstack-dev] [keystone] Feedback for upcoming user survey questionnaire

We have the opportunity to ask one question on the upcoming user survey and we get to decide the audience to which we serve the question. Our audience options are: USING, TESTING, or INTERESTED in Keystone (I think we should aim for USING or TESTING) The question can take one of several

[openstack-dev] [keystone] reminder: no meeting today

see everyone next week, happy holidays! stevemar __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [keystone] office hours starting January 6th

Thanks for the initiative! This is something that both keystone and the community will benefit! :) On Wed, Dec 21, 2016 at 4:22 PM, Steve Martinelli wrote: > Thanks for setting this up Lance! > > You can count on me to join and smash some bugs. > > On Wed, Dec 21, 2016

Re: [openstack-dev] [keystone] office hours starting January 6th

Thanks for setting this up Lance! You can count on me to join and smash some bugs. On Wed, Dec 21, 2016 at 1:06 PM, Lance Bragstad wrote: > Hi folks! > > If you remember, last year we started a weekly bug day [0]. The idea was > to dedicate one day a week to managing

[openstack-dev] [keystone] office hours starting January 6th

Hi folks! If you remember, last year we started a weekly bug day [0]. The idea was to dedicate one day a week to managing keystone's bug queue by triaging, fixing, and reviewing bugs. This was otherwise known as keystone's office hours. I'd like to remind everyone that we are starting up this

[openstack-dev] [keystone] 2016-12-21 policy meeting

Sending a note to summarize the policy meeting we had today [0]. Also to remind folks that our next policy meeting will be Wednesday, January 4th. Hope everyone has a safe and happy holiday season! [0] http://eavesdrop.openstack.org/meetings/policy/2016/policy.2016-12-21-16.01.log.html

Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone Hi, I think one of the issues we're trying to solve here is duplication reducing. Quotas in OpenStack commonly contain two parts: limits management and limits enforcement. If we're talking about library (delimiter

Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

__ > From: Jay Pipes [jaypi...@gmail.com] > Sent: 13 December 2016 18:55:14 > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [keystone][nova]Quotas: Store resources and > limits in the Keystone > > On 12/13/2016 08:09 AM

Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

On 12/13/2016 11:27 AM, Sajeesh Cimson Sasi wrote: Hi, There was an ongoing project of delimiter for Cross Project Quota Management. But I don't know the current status. Kindly have a look at it. https://review.openstack.org/#/c/284454/ More discussions are required on

Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

Subject: Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone On 12/13/2016 08:09 AM, Kseniya Tychkova wrote: > Hi, > I would like to share a spec [1] with you. > The main idea of this spec is to start a discussion about quota > management in the OpenStack

Re: [openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

On 12/13/2016 08:09 AM, Kseniya Tychkova wrote: Hi, I would like to share a spec [1] with you. The main idea of this spec is to start a discussion about quota management in the OpenStack. Quotas are scattered across OpenStack services. Each service defines it's own model and API for managing

[openstack-dev] [keystone][nova]Quotas: Store resources and limits in the Keystone

Hi, I would like to share a spec [1] with you. The main idea of this spec is to start a discussion about quota management in the OpenStack. Quotas are scattered across OpenStack services. Each service defines it's own model and API for managing resource's limits. Because of that, there are

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

> > >> >> I'm surprised any AD administrator let Keystone write to it. I've always >> hear the inverse that AD admins never would allow keystone to write to it, >> therefore it was never used for Projects or Assignments. Users were >> likewise read-only when AD was involved. >> >> I have seen

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

> > > > I'm surprised any AD administrator let Keystone write to it. I've always > hear the inverse that AD admins never would allow keystone to write to it, > therefore it was never used for Projects or Assignments. Users were > likewise read-only when AD was involved. > > I have seen normal LDAP

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

m: Andrey Grebennikov <agrebenni...@mirantis.com> >>>> Reply: OpenStack Development Mailing List (not for usage questions) >>>> <openstack-dev@lists.openstack.org> >>>> Date: December 5, 2016 at 12:22:09 >>>> To: openstack-dev@lists.openstac

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

On 06/12/16 12:15, Andrey Grebennikov wrote: > > Just to clarify, the reason you want custom project IDs is so that > when you create a project in one region, you can create it again > with the same ID in another? Isn't that just manual replication > though? > > What happens

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

sage questions) >>> <openstack-dev@lists.openstack.org> >>> Date: December 5, 2016 at 12:22:09 >>> To: openstack-dev@lists.openstack.org <openstack-dev@lists.openstack.org >>> > >>> Subject: [openstack-dev] [keystone] Custom Proje

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

On 12/06/2016 01:46 AM, Andrey Grebennikov wrote: > Hi, > > On 12/05/2016 09:20 PM, Andrey Grebennikov wrote: > > Hi keystoners, > > I'd like to open the discussion about the little feature which I'm > > trying to push forward for a while but I need some > >

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

> > Just to clarify, the reason you want custom project IDs is so that when > you create a project in one region, you can create it again with the same > ID in another? Isn't that just manual replication though? > > What happens when there are projects in only one region? Or if that isn't > meant

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

Just to clarify, the reason you want custom project IDs is so that when you create a project in one region, you can create it again with the same ID in another? Isn't that just manual replication though? What happens when there are projects in only one region? Or if that isn't meant to happen,

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

ack-dev@lists.openstack.org> >> Date: December 5, 2016 at 12:22:09 >> To: openstack-dev@lists.openstack.org <openstack-dev@lists.openstack.org> >> Subject: [openstack-dev] [keystone] Custom ProjectID upon creation >> >> > Hi keystoners, >> >&

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

> > Hi, > > On 12/05/2016 09:20 PM, Andrey Grebennikov wrote: > > Hi keystoners, > > I'd like to open the discussion about the little feature which I'm > > trying to push forward for a while but I need some > > feedbacks/opinions/concerns regarding this. > > Here is the review I'm talking > >

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

ists.openstack.org <openstack-dev@lists.openstack.org> > Subject: [openstack-dev] [keystone] Custom ProjectID upon creation > > > Hi keystoners, > > I'm not a keystoner, but I hope youu don't mind my replying. > > I'd like to open the discussion about the little feature w

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

On 05-Dec 15:14, Lance Bragstad wrote: > I put myself in Boris' camp on this one. This can open up the opportunity > for negative user-experience, purely based on where I authenticate and > which token I happen to authenticate with. A token would no longer be > something I can assume to be

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

tack-dev@lists.openstack.org> > Subject: [openstack-dev] [keystone] Custom ProjectID upon creation > > > Hi keystoners, > > I'm not a keystoner, but I hope youu don't mind my replying. > > > I'd like to open the discussion about the little feature which I'm trying > &

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

s.openstack.org> Subject:  [openstack-dev] [keystone] Custom ProjectID upon creation > Hi keystoners, I'm not a keystoner, but I hope youu don't mind my replying. > I'd like to open the discussion about the little feature which I'm trying > to push forward for a while but I need some

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

Hi, On 12/05/2016 09:20 PM, Andrey Grebennikov wrote: > Hi keystoners, > I'd like to open the discussion about the little feature which I'm > trying to push forward for a while but I need some > feedbacks/opinions/concerns regarding this. > Here is the review I'm talking > about

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

The ability to specify IDs at project creation time was proposed as a specification last summer [0]. The common theme from the discussion in that thread was to use shadow mapping [1] to solve that problem. [0] https://review.openstack.org/#/c/323499/ [1]

Re: [openstack-dev] [keystone] Custom ProjectID upon creation

I'm OK with the agreed approach in the patch, we restrict the ID being specified to 32 character UUID4 string. And it only works on project create, not update. On Mon, Dec 5, 2016 at 1:20 PM, Andrey Grebennikov < agrebenni...@mirantis.com> wrote: > Hi keystoners, > I'd like to open the

[openstack-dev] [keystone] Custom ProjectID upon creation

Hi keystoners, I'd like to open the discussion about the little feature which I'm trying to push forward for a while but I need some feedbacks/opinions/concerns regarding this. Here is the review I'm talking about https://review. openstack.org/#/c/403866/ What I'm trying to cover is multi-region

[openstack-dev] [keystone]

Hi keystoners, I'd like to open the discussion about the little feature which I'm trying to push forward for a while but I need some feedbacks/opinions/concerns regarding this. Here is the review I'm talking about https://review.openstack.org/#/c/403866/ What I'm trying to cover is multi-region

Re: [openstack-dev] [keystone] Pike PTL

---11/23/2016 11:08:25 AM---Steve, It’s been a pleasure working with > you as PTL - an excellent tenure. Enjoy taking some time ba > > From: Henry Nash <henryna...@mac.com> > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.open

Re: [openstack-dev] [keystone] team logo (initial draft)

Hi Morgan, I don’t know if the illustrator meant to hide a keystone in the illustration, or if you just saw one, but either way that’s brilliant! And don’t worry - these will definitely get color, but right now we’re submitting gray versions for review because it speeds the process (gets it

Re: [openstack-dev] [keystone] team logo (initial draft)

Looks good! Commented on the Form, but the "grey section" might be even better if there was a little color to it. As it is, It might be too "stark" a contrast as it is to a black laptop/background (white alone tends to be) if the white sections are opaque, and it might fade into a "white" or

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

On Thu, Dec 1, 2016 at 7:39 PM, Morgan Fainberg wrote: > On Dec 1, 2016 8:25 AM, "Andrey Kurilin" wrote: > > > > As I replied at IRC, please do not mix two separate issues! > > Yes, we have several scenarios which are not support keystone v3

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

On Dec 1, 2016 8:25 AM, "Andrey Kurilin" wrote: > > As I replied at IRC, please do not mix two separate issues! > Yes, we have several scenarios which are not support keystone v3 yet. It is an issue, but it is unrelated issue to described in the first mail. > We have a job

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

As I replied at IRC, please do not mix two separate issues! Yes, we have several scenarios which are not support keystone v3 yet. It is an issue, but it is unrelated issue to described in the first mail. We have a job which is configured with proper IDENTITY_API_VERSION flag and should be launched

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

FWIW - i'm seeing a common error in several of the rally failures [0] [1] [2] [3]. Dims also pointed out a few bugs in rally for keystone v3 support [4]. I checked with the folks in #openstack-containers to see if they were experiencing anymore fallout, but it looks like the magnum gate is under

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

I think for magnum we are OK. This job [1] finished using keystone v3 [2] Spyros [1] http://logs.openstack.org/93/400593/9/check/gate-functional-dsvm-magnum-api/93e8c14/ [2]

Re: [openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

It has taken years to get here with a lot of work from many folks. -1 for Any revert! https://etherpad.openstack.org/p/v3-only-devstack http://markmail.org/message/aqq7itdom36omnf6 https://review.openstack.org/#/q/status:merged+project:openstack-dev/devstack+branch:master+topic:bp/keystonev3

[openstack-dev] [keystone][devstack][rally][python-novaclient][magnum] switching to keystone v3 by default

Hi folks! Today devstack team decided to switch to keystone v3 by default[0]. Imo, it is important thing, but it was made in silent, so other project was unable to prepare to that change. Also, proposed way to select Keystone API version via devstack configuration doesn't

Re: [openstack-dev] [keystone] Pike PTL

e questions)" <openstack-dev@lists.openstack.org> Date: 11/23/2016 11:08 AM Subject: Re: [openstack-dev] [keystone] Pike PTL Steve, It’s been a pleasure working with you as PTL - an excellent tenure. Enjoy taking some time back! Henry On 21 Nov 2016, at 19:38, Steve

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

16 9:54 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone" We have ensured that the both UDP a

Re: [openstack-dev] [keystone] Pike PTL

You were an awesome PTL! thanks for all the work. BR On Wed, Nov 23, 2016 at 6:04 PM, Henry Nash wrote: > Steve, > > It’s been a pleasure working with you as PTL - an excellent tenure. Enjoy > taking some time back! > > Henry > > On 21 Nov 2016, at 19:38, Steve Martinelli

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

Thanks for everything Marek, good times when we debugged federation issues! :) On Wed, Nov 23, 2016 at 1:05 PM, Henry Nash wrote: > Echoing the comments of others. - thanks for all your hard work and > expertise. > > Henry > > On 23 Nov 2016, at 15:05, Lance Bragstad

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

@mysite-ceilometer-7:~$ nc 10.0.4.4 1048 Hello How is the connection? Good -Original Message- From: gordon chung [mailto:g...@live.ca] Sent: Wednesday, November 23, 2016 8:22 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

On 23/11/16 09:16 PM, Srikanth Vavilapalli wrote: > Yes, I agree, this issue is not related to ceilometer. We have verified that > none of the keystone commands (keystone endpoint-list, keystone catalog, > keystone user-list) are working in that VM2, they all stuck in getting the > token-get

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

ceilometer-api? Thanks for ur help... Thanks Srikanth -Original Message- From: gordon chung [mailto:g...@live.ca] Sent: Wednesday, November 23, 2016 4:20 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "M

Re: [openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

i would probably just try to get a token from vm2 and see if that's even possible. seems unrelated to ceilometerclient. that said, i'm going to throw in obligatory: "ceilometer api is deprecated and has been unmaintained for over a year. i suggest you switch to another storage solution whether

[openstack-dev] [keystone][ceilometer] 'ceilometer -d meter-list' hangs in "Making authentication request to keystone"

Hi We are facing few issues with keystone access in our setups. We have a setup which has three VMs. VM1 and VM3 are on same compute host whereas VM2 is on a different compute host. - VM1 (mysite-ceilometer-6): Running Mitaka Ceilometer service + Keystone (v2) service - VM2

[openstack-dev] [keystone] 2016-11-23 policy meeting summary

We had a useful discussion today [0]. I attempted to summarize the meeting in the etherpad [1], crossed off things we accomplished, and documented our action items to complete by next week, which I'll echo below: *ACTION ITEM:* group to review https://review.openstack.org/#/c/391624/ and continue

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

Echoing the comments of others. - thanks for all your hard work and expertise. Henry > On 23 Nov 2016, at 15:05, Lance Bragstad wrote: > > Thanks for all your hard work, Marek. It's been a pleasure working with you. > Best of luck and hopefully our paths cross in the

Re: [openstack-dev] [keystone] Pike PTL

Steve, It’s been a pleasure working with you as PTL - an excellent tenure. Enjoy taking some time back! Henry > On 21 Nov 2016, at 19:38, Steve Martinelli wrote: > > one of these days i'll learn how to spell :) > > On Mon, Nov 21, 2016 at 12:52 PM, Steve Martinelli

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

Thanks for all your hard work, Marek. It's been a pleasure working with you. Best of luck and hopefully our paths cross in the future! On Tue, Nov 22, 2016 at 7:57 PM, Steve Martinelli wrote: > Marek, thanks for everything you've done in Keystone. It was loads of fun >

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

Marek, thanks for everything you've done in Keystone. It was loads of fun to develop some of the early federation work with you back in the Icehouse release! Good luck in whatever the future holds for you! On Tue, Nov 22, 2016 at 5:18 PM, Marek Denis < marek.denis+openst...@gmail.com> wrote: >

Re: [openstack-dev] [keystone] Pike PTL

ns) < > openstack-dev@lists.openstack.org> > *Subject:* Re: [openstack-dev] [keystone] Pike PTL > > > > Steve, thanks for all the hard work and dedication over the last 3 cycles. > I hope you have a nice break and I look forward to working with you on Pike! > > >

[openstack-dev] [keystone] Stepping down from keystone core

Hi, Due to my current responsibilities I cannot serve as keystone core anymore. I also feel I should make some space for others who will surely bring new quality to the OpenStack Identity Program. It's been a great journey, I surely learned a lot and improved both my technical and soft skills. I

Re: [openstack-dev] [keystone] Pike PTL

ubject: Re: [openstack-dev] [keystone] Pike PTL Steve, thanks for all the hard work and dedication over the last 3 cycles. I hope you have a nice break and I look forward to working with you on Pike! Enjoy you're evenings :) On Mon, Nov 21, 2016 at 1:38 PM, Steve Martinelli <s.martine...@

Re: [openstack-dev] [keystone] Pike PTL

On Mon, Nov 21, 2016 at 5:22 PM, Lance Bragstad wrote: > Steve, thanks for all the hard work and dedication over the last 3 cycles. > I hope you have a nice break and I look forward to working with you on Pike! > I could not say better! Thanks for everything Steve. > >

Re: [openstack-dev] [keystone] Pike PTL

Steve, thanks for all the hard work and dedication over the last 3 cycles. I hope you have a nice break and I look forward to working with you on Pike! Enjoy you're evenings :) On Mon, Nov 21, 2016 at 1:38 PM, Steve Martinelli wrote: > one of these days i'll learn how

Re: [openstack-dev] [keystone] Pike PTL

one of these days i'll learn how to spell :) On Mon, Nov 21, 2016 at 12:52 PM, Steve Martinelli wrote: > Keystoners, > > I do not intend to run for the PTL position of the Pike development cycle. > I'm sending this out early so I can work with folks interested in the

Re: [openstack-dev] [keystone] Weekly Policy Meeting

May I could suggest another action item? I think we need clear use cases. What policy and authorization capabilities are users expecting keystone to have? What are the short-comings of the implementation we have today? On Wed, Nov 16, 2016 at 1:06 PM, Lance Bragstad wrote:

Re: [openstack-dev] [keystone] Weekly Policy Meeting

We had some issues using Hangouts because we hit the maximum limit of attendees. To make it so that everyone could participate equally, we moved the meeting to #openstack-keystone [0]. I have an action item to propose an official meeting to the irc-meetings repository. Patch for the meeting is

Re: [openstack-dev] [keystone] meeting format poll

On 2016-11-16 09:33:54 -0500 (-0500), Steve Martinelli wrote: [...] > As silly as it sounds, not having to log in has > made a noticeable difference -- it's not just me (or another ptl) setting > the agenda) Not silly at all, and in fact very useful feedback! I still hold out hope that once we

Re: [openstack-dev] [keystone] Weekly Policy Meeting

Just sending out a reminder that we'll be having our first meeting in 90 minutes. You can find all information about our agenda in the etherpad [0] as well as a link to the hangout [1]. See you there! [0] https://etherpad.openstack.org/p/keystone-policy-meeting [1]

Re: [openstack-dev] [keystone] meeting format poll

On Wed, Nov 16, 2016 at 9:10 AM, Jeremy Stanley wrote: > On 2016-11-15 17:23:49 -0500 (-0500), Steve Martinelli wrote: > > I don't bother with the time slider, the meeting agenda is never deleted > > from the etherpad, we just keep tacking on > > Oh, I see, using it as an

Re: [openstack-dev] [keystone] meeting format poll

On 2016-11-15 17:23:49 -0500 (-0500), Steve Martinelli wrote: > I don't bother with the time slider, the meeting agenda is never deleted > from the etherpad, we just keep tacking on Oh, I see, using it as an append-only log (and hope nobody erases anything or the pad doesn't spontaneously

Re: [openstack-dev] [keystone] meeting format poll

On Tue, Nov 15, 2016 at 4:53 PM, Jeremy Stanley wrote: > On 2016-11-15 15:31:40 -0500 (-0500), Steve Martinelli wrote: > > I really like the etherpad approach, its nice to see the history from > > previous meetings > > Strange, I personally find it way easier to navigate the

Re: [openstack-dev] [keystone] meeting format poll

On 2016-11-15 15:31:40 -0500 (-0500), Steve Martinelli wrote: > I really like the etherpad approach, its nice to see the history from > previous meetings Strange, I personally find it way easier to navigate the change history for a MediaWiki page than use the time slider in Etherpad:

Re: [openstack-dev] [keystone] meeting format poll

I agree with Steve. I just want to highlight that the wiki is viable again if we wanted to change. The move to etherpad was a necessity, now we have options we should be sure eveyrone is still happy with it. On Tue, Nov 15, 2016 at 12:31 PM, Steve Martinelli wrote: > I

Re: [openstack-dev] [keystone] meeting format poll

I really like the etherpad approach, its nice to see the history from previous meetings On Tue, Nov 15, 2016 at 2:39 PM, Lance Bragstad wrote: > Hey folks, > > In today's keystone meeting, Morgan mentioned that we had the ability to > go back to using OpenStack Wikis for

[openstack-dev] [keystone] meeting format poll

Hey folks, In today's keystone meeting, Morgan mentioned that we had the ability to go back to using OpenStack Wikis for meeting agendas. I created a poll to get feedback [0]. Let's keep it open for the week and look at the results as a team at our next meeting. Thanks! [0]

[openstack-dev] [Keystone][Horizon] Additional MFA option: per user ip address rules

Hello Keystone Devs, I've been playing with an interesting idea in regards to the authentications plugins in Keystone as I was curious if I could achieve per user IP rules for authentication with the existing setup we have. In short, yes, and here is an example plugin that seems to work:

Re: [openstack-dev] [keystone][tripleo][ansible][puppet][all] changing default token format

Its been a few days now, and I think we're OK. We are not seeing the tempest failures related to race conditions like we saw before. No major CI breaks, there seems be an uptick in failures, but those look like they are timeouts and not related (i hope!). Thanks to everyone who worked on this! On

Re: [openstack-dev] [keystone] Weekly Policy Meeting

I've added some initial content to the etherpad [0], to get things rolling. Since this is going to be a recurring thing, I'd like our first meeting to level set the playing field for everyone. Let's spend some time getting familiar with policy concepts, understand exactly how OpenStack policy

Re: [openstack-dev] [keystone] Weekly Policy Meeting

Thanks for taking the initiative Lance! It'll be great to hear some ideas that are capable of making policy more fine grained, and keeping things backwards compatible. On Thu, Nov 10, 2016 at 3:30 PM, Lance Bragstad wrote: > Hi folks, > > After hearing the recaps from the

[openstack-dev] [keystone] Weekly Policy Meeting

Hi folks, After hearing the recaps from the summit, it sounds like policy was a hot topic (per usual). This is also reinforced by the fact every release we have specifications proposed to re-do policy in some way. It's no doubt policy in OpenStack needs work. Let's dedicate an hour a week to

<    2   3   4   5   6   7   8   9   10   11   >