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

2017-10-25 Thread Lance Bragstad
I'm not sure how I didn't include -operators the first time around, but adding them to this thread now. TL;DR We're going through policy/RBAC for other systems to get an idea of how we want to shape OpenStack's policy and RBAC model. We're going to meet next Wednesday at 15:00 UTC. The meeting

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

2017-10-25 Thread Lance Bragstad
I've recapped the notes from today's session and I'll post a follow up with the recording as soon as it's available. All notes can be found in the etherpad (agreement and outcomes are in *bold*)**[0]. Next week at the same time (15:00 UTC) we will continue going through AWS IAM flows. While

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

2017-10-24 Thread Lance Bragstad
Gentle reminder that this will be happening tomorrow. See you then! On 10/20/2017 09:46 AM, Lance Bragstad wrote: > I just sent a calendar invite to everyone who responded to this thread > or voted in the agenda. The session will be recorded if you are unable > to make it. > > Thanks! > > On

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

2017-10-20 Thread Lance Bragstad
I just sent a calendar invite to everyone who responded to this thread or voted in the agenda. The session will be recorded if you are unable to make it. Thanks! On 10/18/2017 10:10 AM, Lance Bragstad wrote: > Now that we have some good feedback on the doodle, it looks like we > have two

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

2017-10-18 Thread Lance Bragstad
Now that we have some good feedback on the doodle, it looks like we have two sessions that will work for everyone. One is October 25th from 15:00 - 16:00 UTC and the other is also the 25th from 16:00 - 17:00. Let's shoot to meet at *15:00 UTC* on *October 25th* and if the meeting goes over, we

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

2017-10-16 Thread Lance Bragstad
Sending out a gentle reminder to vote for time slots that work for you [0]. We'll keep the poll open for a few more days, or until we reach quorum. Thanks! [0] https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu On 10/11/2017 01:48 PM, Lance Bragstad wrote: > Oh - one note about the doodle [0]. All

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

2017-10-11 Thread Lance Bragstad
Oh - one note about the doodle [0]. All proposed times are in UTC, so just keep that in mind when selecting your availability. Thanks! [0] https://beta.doodle.com/poll/ntkpzgmcv3k6v5qu On 10/11/2017 01:44 PM, Lance Bragstad wrote: > In today's policy meeting we went through and started prepping

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

2017-10-11 Thread Lance Bragstad
In today's policy meeting we went through and started prepping for the session. Relevant information has been captured in the etherpad [0]. We're going to hold the meeting using *Google* *Hangouts*. I'll update the etherpad with a link to the hangout once we settle on a date. If you plan on

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

2017-10-09 Thread Lance Bragstad
I've put a scheduling session on the books for the next policy meeting [0][1]. Advertising it here since folks who want to be involved have responded to the thread. Let's use this meeting time to iron out account details and figure out what exactly we want to get out of the session. [0]

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

2017-10-05 Thread Colleen Murphy
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

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

2017-10-04 Thread Fox, Kevin M
Yeah. Very interesting. Thanks for sharing. Kevin From: Adam Heczko [ahec...@mirantis.com] Sent: Wednesday, October 04, 2017 2:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [policy] AWS IAM session Hi Devdatta

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

2017-10-04 Thread Adam Heczko
Hi Devdatta, excellent post on IAM models. Thank you! On Wed, Oct 4, 2017 at 10:59 PM, Devdatta Kulkarni < kulkarni.devda...@gmail.com> wrote: > +1 > > I spent some time recently studying IAM models of AWS and GCP. > Based on this I had created following post comparing and summarizing the > two

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

2017-10-04 Thread Devdatta Kulkarni
+1 I spent some time recently studying IAM models of AWS and GCP. Based on this I had created following post comparing and summarizing the two models at high-level: http://devcentric.io/2017/07/13/comparing-iam-models-of-aws-and-gcp/ Thought of sharing it here as it may help with big-picture

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

2017-10-04 Thread Kristi Nikolla
+1 -- Kristi Nikolla Software Engineer @ massopen.cloud kri...@nikolla.me On Wed, Oct 4, 2017, at 10:08 AM, Zane Bitter wrote: > On 03/10/17 16:08, Lance Bragstad wrote: > > Hey all, > > > > It was mentioned in today's keystone meeting [0] that it would be useful > > to go through AWS

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

2017-10-04 Thread Zane Bitter
On 03/10/17 16:08, 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. The idea would be to

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

2017-10-03 Thread William M Edmonds
+1 Lance Bragstad wrote on 10/03/2017 04:08:31 PM: > 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

[openstack-dev] [policy] AWS IAM session

2017-10-03 Thread Lance Bragstad
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. The idea would be to spend time using a video conference/screen