[Senlin] Splitting senlin-engine into three services

Erik Olof Gunnar Andersson eandersson at blizzard.com
Sun Nov 10 23:06:16 UTC 2019

We are looking at merging this in a few days if there is no additional feedback.

Also, in case someone has experience with adding new services to a project. Is there a general way of requesting rpms etc to be updated for the next release to support the new services? Especially for the workflows that are handled outside of the official openstack repos.
From: Erik Olof Gunnar Andersson <eandersson at blizzard.com>
Sent: Monday, November 4, 2019 5:11 PM
To: openstack-discuss at lists.openstack.org <openstack-discuss at lists.openstack.org>
Cc: Duc Truong <dtruong at blizzard.com>
Subject: [Senlin] Splitting senlin-engine into three services

We are looking into splitting the senlin-engine into three components (senlin-conductor, senlin-engine and senlin-health-manager) and wanted to get some feedback.

The main goal here is to make the components more resilient and to reduce the number of threads per worker. Each one of the components already had it's own thread
pool and in theory each worker could end up with thousands of thread.

In the current version (Train) the engine process hosts these services.

In my patch we move two our of these out of the engine and into it's own service namespace.

Split engine service into three services

Please feel free to comment on the patch set, or let reply to this email with general feedback or concerns.

 Best Regards, Erik Olof Gunnar Andersson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191110/8f149b55/attachment-0001.html>

More information about the openstack-discuss mailing list