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 <lbragstad at 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 [1] https://github.com/openstack/ > keystone/commit/a5c5f5bce812fad3c6c88a23203bd6c00451e7b3 > > __________________________________________________________________________ > 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 > > -- Juan Antonio Osorio R. e-mail: jaosorior at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170628/9997a2a8/attachment.html>