ok thanks for the info.
I have written a post install script for now that seems to work which
turns the Keystone eventlet into WSGI and alters Pacemaker accordingly.
For smoother deployment I will wait until the stable branch has this
integrated as my Puppet Fu is also lacking
Regards
Charles
On 23/03/2016 15:48, Adam Young wrote:
On 03/23/2016 11:27 AM, Charles Short wrote:
> Hi,
>
> 'Back in the days' when I was installing Kilo with Packstack I
> noticed that Keystone was running by default as a WSGI process
> instead of a Python eventlet.
> This was due to the Keystone eventlet being deprecated.
> I recently installed Liberty Triple0 on bare metal with three
> controllers (Delorean stable branch) and was surprised to see that
> Keystone was
> running by default as a Python eventlet again!
>
> I have found a related bug here -
>
>
https://bugzilla.redhat.com/show_bug.cgi?id=1264011
>
> I need Keystone running as WSGI as this is a prerequisite for me to
> install a VOMs plugin to federate.
> Can anyone point me to the best (safest) way to change from eventlet
> to WSGI manually (or indeed with templates)
>
> Thanks
>
> Charles
>
>
With Packstack, WSGI is still supported. With Tripleo, you need the
absolute latest out of upstream, as the first take of Tripleo put
Keystone in Eventlet, and getting it out of there required careful
work by people much better at puppet than I am (Hi Emilien).
Sorry about that. But I am now testing Tripleo Federation and it seems
to be OK. The biggest thing is to avoid touching the Puppet managed
files, and to make your changes in separate files, so that a redeploy
does not overwrite your changes.
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
--
Charles Short
Cloud Engineer
Virtualization and Cloud Team
European Bioinformatics Institute (EMBL-EBI)
Tel: +44 (0)1223 494205