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

2015-12-07 Thread Steve Martinelli
... re-adding the operators mailing list. sounds like we should document how to do this, with the assertion that it is not tested with our CI. with that said, we should try to have a job that sets up keystone with nginx that is run periodically (similar to our eventlet job at the moment). steve

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

2015-12-07 Thread Matthew Treinish
On Mon, Dec 07, 2015 at 06:18:04PM -0500, Steve Martinelli wrote: > > ... re-adding the operators mailing list. > > sounds like we should document how to do this, with the assertion that it > is not tested with our CI. > > with that said, we should try to have a job that sets up keystone with >

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

2015-12-07 Thread Thomas Goirand
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 > constrained by Apache. > - uWSGI could help to support multiple web servers. > > M

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

2015-12-07 Thread Adam Young
On 12/07/2015 06:53 PM, 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 constrained by Apache. - uWSGI could help to

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

2015-12-07 Thread Rich Megginson
On 12/07/2015 07:49 PM, Adam Young wrote: On 12/07/2015 06:53 PM, 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

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

2015-12-07 Thread Jamie Lennox
On 8 December 2015 at 07:53, 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 > > constrained by Apac

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

2015-12-09 Thread Thomas Goirand
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 w

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

2015-12-09 Thread Thomas Goirand
On 12/08/2015 06:39 AM, Jamie Lennox wrote: > The main problem I see with running Keystone (or any other service) in a > web server, is that *I* (as a package maintainer) will loose the control > over when the service is started. Let me explain why that is important > for me. > >