How to uninstall OSM: Difference between revisions
From OSM Public Wiki
Fernandezca (talk | contribs) (Created page with "__TOC__ This page intends to provide means to leave the environment clean and ready, assuming OSM release FOUR was installed previously. This should allow successful OSM rede...") |
Fernandezca (talk | contribs) mNo edit summary |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
This page intends to provide means to leave the environment clean and ready, assuming OSM release FOUR was installed previously. This should | This page intends to provide means to leave the environment clean and ready, assuming OSM release FOUR was installed previously. This should enable successful OSM redeployments in the future. | ||
== Removing the OSM stack == | == Removing the OSM stack == | ||
Line 15: | Line 15: | ||
=== Manual procedure === | === Manual procedure === | ||
Stop the | Stop the osm docker stack and remove all unused containers, images and volumes: | ||
docker stack rm osm | docker stack rm osm | ||
# Warning: the instruction below will clean all volumes and images, not only the ones used by OSM | |||
docker system prune --all --volumes | docker system prune --all --volumes | ||
Line 24: | Line 25: | ||
After removing the OSM stack (either automatically or manually), remove any packages that were left: | After removing the OSM stack (either automatically or manually), remove any packages that were left: | ||
# Warning: the instruction below will remove Docker, which may be used by others | |||
sudo apt remove --purge docker-ce | sudo apt remove --purge docker-ce | ||
# Warning: tthe instruction below will remove Juju, which may be used by others | |||
sudo snap remove juju | sudo snap remove juju | ||
sudo apt remove --purge osm-devops python-osmclient | sudo apt remove --purge osm-devops python-osmclient |
Latest revision as of 12:25, 27 September 2018
This page intends to provide means to leave the environment clean and ready, assuming OSM release FOUR was installed previously. This should enable successful OSM redeployments in the future.
Removing the OSM stack
Any of the two following procedures should work.
Automatic procedure
It is possible to clean the environment by providing a flag to the OSM installer script:
sudo ./install_osm.sh --uninstall
Manual procedure
Stop the osm docker stack and remove all unused containers, images and volumes:
docker stack rm osm # Warning: the instruction below will clean all volumes and images, not only the ones used by OSM docker system prune --all --volumes
Removing packages in the system
After removing the OSM stack (either automatically or manually), remove any packages that were left:
# Warning: the instruction below will remove Docker, which may be used by others sudo apt remove --purge docker-ce # Warning: tthe instruction below will remove Juju, which may be used by others sudo snap remove juju sudo apt remove --purge osm-devops python-osmclient