Subject: Re: [Trove] State of the Trove service tenant deployment model

Lingxian Kong anlin.kong at
Tue Jan 22 23:08:32 UTC 2019

On Wed, Jan 23, 2019 at 9:27 AM Fox, Kevin M <Kevin.Fox at> wrote:

> I'd recommend at this point to maybe just run kubernetes across the vms
> and push the guest agents/workload to them.

This sounds like an overkill to me. Currently, different projects in
openstack are solving this issue in different ways, e.g. Octavia is
using two-way SSL authentication API between the controller service and
amphora(which is the vm running HTTP server inside), Magnum is using
heat-container-agent that is communicating with Heat via API, etc. However,
Trove chooses another option which has brought a lot of discussions over a
long time.

In the current situation, I don't think it's doable for each project
heading to one common solution, but Trove can learn from other projects to
solve its own problem.
Lingxian Kong
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openstack-discuss mailing list