[kolla] Support for removing previously enabled services..
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. [image: image.png] 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!
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@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!
Hey! 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. Laurent On Sat, Oct 12, 2019 at 9:27 AM Radosław Piliszek < radoslaw.piliszek@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@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!
On Sat, 2019-10-12 at 21:01 -0400, Laurent Dumont wrote:
Hey!
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.
i did add a tiny step in that direction years ago for mainly dev use https://github.com/openstack/kolla-ansible/commit/2ffb35ee5308ece3717263d381... basically the tools/cleanup-containers script takes a regex of the continers to clean up as its first argument. e.g. tools/cleanup-containers "neutron|openvswitch" that is totally a hack but it was so useful for dev. i belive there is already a request to limit kolla-ansible --destroy by tags destroy should in theory be cleanup dbs in addtion to remvoing the contianers but give that currently it just remvoed everything of nothing it not that useful for operator wanting to remvoe a deployed service. my hack when used to be an tiny ansible script that copied that tool to all host then invoked it the relevent regex. anywya if you jsut wasnt to do this for dev or on a small number of hosts it might help but keep in mind that it will not clean up the configs or dbs and it only works if no vms are runnign on the host
Laurent
On Sat, Oct 12, 2019 at 9:27 AM Radosław Piliszek < radoslaw.piliszek@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@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!
On Sun, 13 Oct 2019 at 11:24, Sean Mooney <smooney@redhat.com> wrote:
On Sat, 2019-10-12 at 21:01 -0400, Laurent Dumont wrote:
Hey!
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.
True, although simply removing the containers and load balancer configuration would be a good start.
i did add a tiny step in that direction years ago for mainly dev use https://github.com/openstack/kolla-ansible/commit/2ffb35ee5308ece3717263d381... basically the tools/cleanup-containers script takes a regex of the continers to clean up as its first argument. e.g. tools/cleanup-containers "neutron|openvswitch"
that is totally a hack but it was so useful for dev.
i belive there is already a request to limit kolla-ansible --destroy by tags
Yes - https://review.opendev.org/504592. It will need some work to get it merged.
destroy should in theory be cleanup dbs in addtion to remvoing the contianers but give that currently it just remvoed everything of nothing it not that useful for operator wanting to remvoe a deployed service.
my hack when used to be an tiny ansible script that copied that tool to all host then invoked it the relevent regex.
anywya if you jsut wasnt to do this for dev or on a small number of hosts it might help but keep in mind that it will not clean up the configs or dbs and it only works if no vms are runnign on the host
Laurent
On Sat, Oct 12, 2019 at 9:27 AM Radosław Piliszek < radoslaw.piliszek@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@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!
participants (4)
-
Laurent Dumont
-
Mark Goddard
-
Radosław Piliszek
-
Sean Mooney