Open Stack

I apologize for using the "baremetal/VM" name, but I wanted to get an
etherpad rolling sooner rather than later [0], since we're likely going
to have to decide on a new name in person. I ported the initial ideas
Colleen mentioned when she started this thread, added links to previous
etherpads from Boston and Denver, and ported some topics from the Boston
etherpads.

Please feel free to add ideas to the list or elaborate on existing ones.
Next week we'll start working through them and figure out what we want
to accomplish for the session. Once we have an official room for the
discussion, I'll add the etherpad to the list in the wiki.

[0] https://etherpad.openstack.org/p/baremetal-vm-rocky-ptg


On 02/02/2018 11:10 AM, Zane Bitter wrote:
> On 30/01/18 10:33, Colleen Murphy wrote:
>> 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?
>
> +1, I would definitely attend this too.
>
> - ZB
>
>>  From a keystone perspective, some things we'd like to talk about with
>> the BM/VM teams are:
>>
>> - Unified limits[2]: we now have a basic REST API for registering
>> limits in keystone. Next steps are building out libraries that can
>> consume this API and calculate quota usage and limit allocation, and
>> developing models for quotas in project hierarchies. Input from other
>> projects is essential here.
>> - RBAC: we've introduced "system scope"[3] to fix the admin-ness
>> problem, and we'd like to guide other projects through the migration.
>> - Application credentials[4]: this main part of this work is largely
>> done, next steps are implementing better access control for it, which
>> is largely just a keystone team problem but we could also use this
>> time for feedback on the implementation so far
>>
>> There's likely some non-keystone-related things that might be at home
>> in a dedicated BM/VM room too. Do we want to have a dedicated day or
>> two for these projects? Or perhaps not dedicated days, but
>> planned-in-advance meeting time? Or should we wait and schedule it
>> ad-hoc if we feel like we need it?
>>
>> Colleen
>>
>> [1]
>> https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid=1374855307&single=true
>> [2]
>> http://specs.openstack.org/openstack/keystone-specs/specs/keystone/queens/limits-api.html
>> [3]
>> http://specs.openstack.org/openstack/keystone-specs/specs/keystone/queens/system-scope.html
>> [4]
>> http://specs.openstack.org/openstack/keystone-specs/specs/keystone/queens/application-credentials.html
>>
>> __________________________________________________________________________
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __________________________________________________________________________
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180202/1d24e4ae/attachment.sig>