Re: [openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On 12/08/2015 04:09 AM, Dolph Mathews wrote: > In Debian, many services/daemons are run, then their API is used by the > package. In the case of Keystone, for example, it is possible to ask, > via Debconf, that Keystone registers itself in the service catalog. If > we get Keystone

Re: [openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Wed, Dec 9, 2015 at 2:25 AM, Thomas Goirand wrote: > On 12/08/2015 04:09 AM, Dolph Mathews wrote: > > In Debian, many services/daemons are run, then their API is used by > the > > package. In the case of Keystone, for example, it is possible to ask, > > via

Re: [openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Wednesday, December 9, 2015, Ginwala, Aliasgar wrote: > Hi Dolph/team: > > As requested I have outlined most of the files and configs to give more > clear picture @ https://gist.github.com/noah8713/7d5554d78b60cd9a4999: > The number of threads per API your config files

Re: [openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

On Monday, December 7, 2015, Thomas Goirand wrote: > On 12/01/2015 07:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > >

[openstack-dev] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

In the Mitaka release, the keystone team will be removing functionality that was marked for deprecation in Kilo, and marking certain functions as deprecated in Mitaka (that may be removed in at least 2 cycles). removing deprecated functionality = This is not a full list, but