aboutsummaryrefslogtreecommitdiff
path: root/tools/cleanup-containers
AgeCommit message (Collapse)AuthorFilesLines
2017-01-05Remove kolla-genpwd from setup.cfgPaul Bourke1-29/+0
This is now in kolla-ansible Co-Authored-By: caoyuan <cao.yuan@99cloud.net> Change-Id: I787a8ba7053f55480125dda64737466300bf7357
2016-11-15add new line in cleanup-containerszhubingbing1-0/+1
looks like any other script TrivialFix Change-Id: I00eef0657a4409719214092ca33730a058b9bb28
2016-10-13Cleanup container script improvementliyingjun1-1/+1
Currently, when there are some qemu processes which may be some useful virtual machines running by the operator running on non compute node, the cleanup script will fail the cleanup operation for that node. We need to ignore the qemu process check for non compute nodes. Change-Id: If49a1a30764063935b2a65312de8f3b2357c7fbc Closes-bug: 1633005
2016-09-12move ovs cleanup to tools/cleanup-hostSean Mooney1-5/+0
- One of the usecase supported by tools/cleanup-containers was the ablity to remove container with a regex so that you could redepoloy just that single componet. - By cleaning up ovs in cleanup-containers that is nolonger possible. - This change move the cleanup of ovs from, tools/cleanup-contianers to tools/cleanup-hosts TrivialFix Change-Id: If2001130f4a2400555ce4d9ac5ee506482e4c25e
2016-09-06TrivialFix: Delete virtual bridge artifacts when cleaning hostsluyao1-0/+5
After cleaning hosts by using tools/cleanup_host, some of the ovs bridge devices such as ovs-system still exist. This will result in {{neutron_external_interface}} not working properly because it had been added to the ovs-system bridge. The solution is calling neutron-ovs-cleanup script in neutron_openvswitch_agent container before removing it. TrivialFix Change-Id: Ib3b096d842f2210b8bd223892a3492ef2fcf7c52 Signed-off-by: luyao <lu.yao135@zte.com.cn>
2016-06-14Make cleanup remove restarting/exited containersMichal (inc0) Jastrzebski1-1/+1
If we have bug in contianer or it simplt somehow ended up in Exited state, cleanup doesn't flush it. It also means it doesn't flush volumes and that might cause an dirty env. Closes-Bug: #1587344 Change-Id: Ib5705992500ce7efdc66509df61c381bd33d1954
2016-05-06Make "cleanup-containers" script works dynamicallyCarlos Cesario1-52/+6
Make cleanup-containers works dynamically. The script removes the containers and its volumes dynamically based on label contained in each kolla container, this way is not needed create a big container and volume lists to be deleted. http://paste.openstack.org/show/496357/ Closes-Bug: #1579044 Change-Id: Ie0d8a38ba2cf77c8d5da655958407145f4105bec
2016-05-05Deletes fake containers on cleanupprithiv1-1/+2
Closes-Bug: #1576277 Change-Id: Ie68d1d5da620f26a0aa21aa5c6473bc464994ed8
2016-04-07Add mongodb in cleanup containers scriptMauricio Lima1-0/+1
Change-Id: I0901802e0e349956f2c01dcd86746b4de0cc2382 Closes-Bug: #1567642
2016-04-05Add nova_ssh in cleanup containers scriptMauricio Lima1-1/+1
Closes-Bug: #1566281 Change-Id: I84533a066a2dbc4de282b20785092350607c5971
2016-03-28Remove bootstrap_mariadb with cleanup-containersMauricio Lima1-1/+1
TrivialFix Change-Id: Ic6884d46d8edf2d430f8a9fb8635f7d98d011112
2016-03-15Change libvirt volume name to libvirtdSamYaple1-1/+2
This change is a "futureproofing" thing. It has already been discussed that libvirt should not be a child of nova and should be removed out to the base docker directory (just like openvswitch isn't a child of neutron). That is not going to happen this cycle but when it does we can't change the name of the volume. This updates the volumes to the proper name of libvirtd. This is in contrast with the libvirtlogd volume that will be needed in newton due to libvirt 1.3 Of note, the container can remain named nova_libvirt since we can change that on the fly later without breaking instances. This wont break liberty as named_volumes are not backported yet. TrivialFix Change-Id: I16cf9e1b1dbba9b5a9f5cc883494580e276d4f72
2016-03-09Add cron image and playbookÉric Lemoine1-0/+1
Add cron image and playbook for logrotate. The "common" Ansible playbook includes configuration files for logrotate. At this point the operator cannot customize/override the logrotate configuration. Closes-Bug: #1553244 Change-Id: Ic9fdda9a273c9ccd90502f0acc7614d2c7157dca
2016-03-05Use alphabetical order in cleanup-containersÉric Lemoine1-12/+12
TrivialFix Change-Id: I95f2e6d17ba7960b2f87344f30b7884d621f9ecb
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine1-2/+5
This patch includes changes relative to integrating Heka with Elasticsearch and Kibana. The main change is the addition of an Heka ElasticSearchOutput plugin to make Heka send the logs it collects to Elasticsearch. Since Logstash is not used the enable_elk deploy variable is renamed to enable_central_logging. If enable_central_logging is false then Elasticsearch and Kibana are not started, and Heka won't attempt to send logs to Elasticsearch. By default enable_central_logging is set to false. If enable_central_logging is set to true after deployment then the Heka container needs to be recreated (for Heka to get the new configuration). The Kibana configuration used property names that are deprecated in Kibana 4.2. This is changed to use non-deprecated property names. Previously logs read from files and from Syslog had a different Type in Heka. This is changed to always use "log" for the Type. In this way just one index instead of two is used in Elasticsearch, making things easier to the user on the visualization side. The HAProxy configuration is changed to add entries for Kibana. Kibana server is now accessible via the internal VIP, and also via the external VIP if there's one configured. The HAProxy configuration is changed to add an entry for Elasticsearch. So Elasticsearch is now accessible via the internal VIP. Heka uses that channel for communicating with Elasticsearch. Note that currently the Heka logs include "Plugin elasticsearch_output" errors when Heka starts. This occurs when Heka starts processing logs while Elasticsearch is not yet started. These are transient errors that go away when Elasticsearch is ready. And with buffering enabled on the ElasticSearchOuput plugin logs will be buffered and then retransmitted when Elasticsearch is ready. Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb Implements: blueprint central-logging-service
2016-03-01Merge "Update cleanup-containers to remove ceph containers"Jenkins1-1/+3
2016-03-01Update cleanup-containers to remove ceph containersMauricio Lima1-1/+3
TrivialFix Change-Id: Ia47429a38503d4982049c3fa1fc6fca4a8000fbd
2016-02-29Move ironic-discoverd to ironic-inspectorAllen Gao1-1/+1
Closes-Bug: #1551052 Change-Id: Ic226287bbf1f1e8d5cc2e1d80ce2975448b1f95c
2016-02-23Remove Rsyslog entirelyÉric Lemoine1-2/+0
Partially implements: blueprint heka Change-Id: I1322d2dc870e6f8fe052926995d993e8a08a25db
2016-02-22Merge "Make cleanup-containers remove bootstrap_heka"Jenkins1-1/+1
2016-02-22Make cleanup-containers remove Heka volumesÉric Lemoine1-1/+3
TrivialFix Partially implements: blueprint heka Change-Id: Ie8f393515c464020f079db41c05d023319920136
2016-02-22Make cleanup-containers remove bootstrap_hekaÉric Lemoine1-1/+1
TrivialFix Partially implements: blueprint heka Change-Id: I5f91056590250f2a477018c1773905b412536f24
2016-02-19Add Heka to common roleÉric Lemoine1-0/+1
Partially implements: blueprint heka Change-Id: I9ddad09b3f16b323c7ed535243458b0de6620cdb
2016-02-19Keep consistent with others for ironic containersAllen Gao1-2/+2
Make the containers and volumes names of ironic to be consistent with others. Partially-implements: blueprint ironic-container Change-Id: If78b020c81157a948c5c3283f1410bcb6e5c1e61
2016-02-18Also remove the volumes when cleaning up containersJeffrey Zhang1-0/+18
TrivialFix Change-Id: Ia52451d2c0de09ee9dcf79211389a3b1ce4ae738
2016-02-17Adds support for cleaning up bootstrap containers in theShaun Smekel1-2/+5
toos/cleanup-containers script. Dynamic Ceph OSD bootstrap containers also included. Change-Id: Ifb5b54c5b78a894ed6e8b9980a6eb9919e52364c Closes-Bug: #1515544 Signed-off-by: Shaun Smekel <shaun.smekel@theorem.net.au>
2016-02-14rabbitmq_data container is removedAllen Gao1-1/+1
TrivialFix Change-Id: I5168191182c249df68fd0b5c70a778f223326974
2016-02-09Add all neutron agents to cleanup-containers scriptMartin André1-1/+1
When breaking neutron-agents into thin containers, we forgot to update the cleanup-containers script. TrivialFix Change-Id: Idad2eb73a4de7c66109ad5bffcce3173970e2af9
2016-02-02Rename kolla_ansible to kolla_toolboxSamYaple1-1/+1
This change is needed for clarity. We have a kolla-ansible script. We have a kolla-mesos repo. We plan to have a kolla-ansible repo. Already we have had far too much confusion about whether we are talking about the container or the project. Naming this kolla-toolbox eliminates all of that confusion and its probably a bit more accurate of a name too. Closes-Bug: #1541053 Change-Id: I8fd1f49d5a22b36ede5b10f46b9fe02ddda9007e
2016-01-28Update cleanup-containers to remove manila containersMauricio Lima1-0/+1
Change-Id: Ie7a53396b03ce4e472b5e810a02ccdfc9bd8aacd Partially-Implements: blueprint enable-manila-containers
2016-01-20refactor the cleanup containersAllen Gao1-10/+10
TrivialFix Sort the containers, remove *_data ones, etc. Change-Id: Ic7923828517da954e7c8802d6cf5918e425df255
2015-12-14Remove ironic containers in the cleanup scriptArtur Zarzycki1-1/+2
TrivialFix Change-Id: Ia37369acf8bf7ca7f49fd647f40c6e98f40e93d8
2015-12-09Remove cinder containers in the cleanup scriptSidharth Surana1-1/+2
Change-Id: I29b788a71f30d133e66759a5de2ecd43222313a8 Closes-Bug: #1524557
2015-12-02adds tools/cleanup-containers regex supportSean Mooney1-20/+24
- this change extends the tools/cleanup-containers script to support a grep extended regex as a first paramater. - if tools/cleanup-containers is called with a grep extended regex string as a first paramater, only containers mataching that regex will be cleaned up. - e.g. tools/cleanup-containers "neutron|openvswitch" will cleanup all container whoes name contains either neutron or openvswitch. Change-Id: Iadb68c0a8de40e9ec2c0a27568e3a372ec0e8303 Closes-Bug: #1522168
2015-11-28Remove openvswitch_data container in the cleanup scriptHui Kang1-1/+1
Change-Id: Iec94e254e8df501005fd3660c80e3c2eefbb05bb Closes-bug: #1520833
2015-11-13Add Ansible support for MagnumMichal Rostecki1-0/+1
Change-Id: Idb25ac4d3148c9b9400cf675ac2e47d35cce6224 Implements: blueprint ansible-magnum
2015-10-22Remove memcached container in cleanup-containers toolMichal Rostecki1-1/+2
Change-Id: Ic56b7b2fd6cd7d191cc364a37f3ebbc44950932e Closes-Bug: #1508780
2015-10-06put conatiner name to array in cleanup-containersKuo-tung Kao1-4/+5
The brace in string variable will not be expanded in some case. Put conatiner name into array. Change-Id: I2fb16e7352bd579f207efce0fb9b2565a1e7236d Closes-Bug: #1502467
2015-09-27Improve cleanup scriptSam Yaple1-5/+31
Its still dirty, but at least it won't kill all your containers. Change-Id: Ie468210bd0f273432ca16fc9530bf9acd2a808ed Closes-Bug: #1486620
2015-08-31Improve scripts with some check before kick rm commandKai Qiang Wu(Kennan)1-2/+6
Closes-Bug: #1490387 Change-Id: I4a9476085b9c5b2cae3801e5b1954e85068f4e03
2015-07-23Removes Host Cleanup from Container Cleanup ScriptDaneyon Hansen1-33/+1
Split the content of cleanup-containers into containers cleanup and host cleanup. This allows to run the cleanup-containers from OSX clients, while keeping needed code to delete host artifacts left behind by the neutron agents container. In addition, cleanup-containers may disappear in the future, replaced by a docker-compose wrapper. Co-Authored-By: Martin André <martin.andre@kvhasia.com> Co-Authored-By: Swapnil Kulkarni <me@coolsvap.net> Change-Id: I3aa731e7e0f9eb3dad9c363bb5d4a575d84a2fae Closes-Bug: #1477383
2015-07-14Update scripts to check if docker is usable for $USERSwapnil Kulkarni1-0/+2
Added new script for checking user permissions on docker command execution Change-Id: I3b727590d9a29f416f5b847912b7250c555c2333 Closes-Bug: #1473554
2015-07-10Remove requirement for root user in scriptsSwapnil Kulkarni1-6/+0
The following files had requirement for root user which can be removed as long as as the the user executing script is part of docker group Scripts updated tools/kolla tools/cleanup-containers Closes-Bug: #1473551 Change-Id: Ia4aea205f5da20fb1ded4f7a5d11eeebe5f40aa9
2015-05-28Make clenaup-containers bashate compliantSteven Dake1-10/+10
Change-Id: I5469e6e60b9e20ee98c9149697f663e94e58077d Partially-Implements: blueprint bashate-gate
2015-05-06Updates cleanup-containersDaneyon Hansen1-1/+37
Previously cleanup-containers suffered from the following limitations: 1. The docker rm command would fail if all the containers were not stopped. 2. The script would throw an error if no containers existed. 3. Artifacts such as veths, bridges, etc.. would remain on the host after containers were removed. These artifacts should be removed if the containers are removed. Change-Id: I5eadb23fec9e34125a32f6c3e39c241d97932910
2015-01-15Pass cleanup scripts arguments to dockerMartin André1-1/+1
This allows to maintain the default behavior unchanged while making it possible to force clean. Follow-up to https://review.openstack.org/#/c/145921/ Change-Id: Ie5733b22bda9cdd7d08f5c5ecc5a3d94b984a125
2015-01-08Cleanup of images and containers needs a '-f' flag to force shutdownRyan Hallisey1-1/+1
Change-Id: I0642dcd36fe5af261b8f35744e3e88460a13fc85
2014-10-17Docker image and process cleaup toolRyan Hallisey1-0/+3
When running Docker, you can unknowingly use up a lot of memory. This tool will make it easier to clean up Docker. Change-Id: Icfd780f12b01956093a2933dd484cde1e2d6d5bc
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-05 20:33:24 +0000