Open Stack

Yeah, it has its own sets of problems. The implementation chosen differs from the one chosen by trove. But in a way that's even worse for operators, as each advanced service (trove, magnum, sahara) has to be learned independently by operators on how to secure it, debug it, upgrade it, etc. Adding each one to the cluster increases the cognitive burden significantly so its rare to deploy multiple in an openstack. 

Thanks,
Kevin
________________________________________
From: Luigi Toscano [ltoscano at redhat.com]
Sent: Tuesday, January 22, 2019 12:39 PM
To: openstack-discuss at lists.openstack.org
Cc: Fox, Kevin M; Darek Król; Michael Richardson
Subject: Re: Subject: Re: [Trove] State of the Trove service tenant deployment model

On Tuesday, 22 January 2019 21:24:55 CET Fox, Kevin M wrote:
> We tried to solve it as a cross project issue for a while and then everyone
> gave up. lots of projects have the same problem. trove, sahara, magnum,
> etc.
>

I would say that Sahara does not have the same problem. There was a discussion
to use a loca agent in 2014 but it died out. Sahara communicate with each node
through ssh, so no (ab)use of the message bus.

Ciao
--
Luigi