That sounds like reason enough to bump the removal of it to Queens or later. This was also discussed in IRC today [0]. We've decided to move forward with the following steps:
- Deprecate the ability to have file-backed domain configuration since removing the ability to upload domains via keystone-manage makes file-backed domain configs less useful - Bump the removal date of domain configuration uploads via keystone-manage - Remove both pieces together in a subsequent release Thanks for the input! [0] http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2017-06-28.log.html#t2017-06-28T18:10:06 On 06/28/2017 04:43 AM, Juan Antonio Osorio wrote: > On the TripleO side we use the file based approach. Using the API > would have been easier to orchestrate (no need for reloads/restarts) > but it's not available yet in puppet-keystone. > > On Wed, Jun 28, 2017 at 2:00 AM, Lance Bragstad <lbrags...@gmail.com > <mailto:lbrags...@gmail.com>> wrote: > > Hi all, > > Keystone has deprecated the domain configuration upload capability > provided through `keystone-manage`. We discussed it's removal in > today's meeting [0] and wanted to send a quick note to the > operator list. The ability to upload a domain config into keystone > was done as a stop-gap until the API was marked as stable [1]. It > seems as though file-based domain configuration was only a > band-aid until full support was done. > > Of the operators using the domain config API in keystone, how many > are backing their configurations with actual configuration files > versus the API? > > > [0] > > http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-06-27-18.00.log.html#l-167 > > <http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-06-27-18.00.log.html#l-167> > [1] > > https://github.com/openstack/keystone/commit/a5c5f5bce812fad3c6c88a23203bd6c00451e7b3 > > <https://github.com/openstack/keystone/commit/a5c5f5bce812fad3c6c88a23203bd6c00451e7b3> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > > > -- > Juan Antonio Osorio R. > e-mail: jaosor...@gmail.com <mailto:jaosor...@gmail.com> > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
signature.asc
Description: OpenPGP digital signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
