[Openstack-operators] [keystone] federated performance feedback

Hey all, We've had a topic come up a few times about making it so IDs can be specified in the API request when creating a project [0]. This has come up over several releases, including the Queens release and in today's keystone meeting [1]. The proposal is meant to solve spanning keystone in

Re: [Openstack-operators] Mixed service version CI testing

it makes sense and it is very valuable ! thanks Saverio Il 19 dic 2017 4:59 PM, "Matt Riedemann" ha scritto: > During discussion in the TC channel today [1], we got talking about how > there is a perception that you must upgrade all of the services together > for anything

[Openstack-operators] Mixed service version CI testing

During discussion in the TC channel today [1], we got talking about how there is a perception that you must upgrade all of the services together for anything to work, at least the 'core' services like keystone/nova/cinder/neutron/glance - although maybe that's really just nova/cinder/neutron?

[Openstack-operators] [openstack-dev] [all] TL; DR: Switching to longer dev cycles

Hey everyone, There was some discussion about this in the operator community, so I just wanted to make sure folks were aware of this recap that Thierry did. I think it nicely captures and summarizes some of the issues brought up in the long thread in openstack-dev. Thanks, Sean - Forwarded

[Openstack-operators] Problems chaning access list for flavors using the dashboard

Dear Operators I have a Mitaka openstack installation and in such deployment I am able to modify the access list of flavors using the dashboard without problems. I am even able to modify a public flavor to a private one (specifying, using the dashboard, the list of projects allowed to use the