[kolla] Support for removing previously enabled services..

Laurent Dumont laurentfdumont at gmail.com
Sun Oct 13 01:01:57 UTC 2019


Not a problem - it's a big rabbit hole and I get why it's really not easy
to implement. It's easy to clean up containers but as you mentioned, all
the rest of the bits and pieces is a tough fit.


On Sat, Oct 12, 2019 at 9:27 AM Radosław Piliszek <
radoslaw.piliszek at gmail.com> wrote:

> Hi Laurent,
> Unfortunately Kolla Ansible does not provide this functionality at the
> moment.
> On the other hand, we would welcome such functionality gladly.
> It needs some discussion regarding how it would work to suit operators'
> needs.
> The interesting part is the real clean-up - e.g. removing leftovers,
> databases, rabbitmq objects...
> PS: bacon rlz
> Kind regards,
> Radek
> On Fri, Oct 11, 2019, 19:12 Laurent Dumont <laurentfdumont at gmail.com>
> wrote:
>> Hey everyone,
>> I'm pretty sure I know the answer but are there any support within Kolla
>> itself to disable Services that we're previously enabled.
>> For example, I was testing the Skydive Agent/Analyzer combo till I
>> realized that it was using about 90-100% of the CPUs or computes and
>> controllers.
>> Re-running Kolla with reconfigure but with Service set to "No" didn't
>> remove the containers. I had to remove the containers after the reconfigure
>> finished.
>> This is Kolla 8.0.1 with a Stein install.
>> Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191012/bf76f750/attachment.html>

More information about the openstack-discuss mailing list