openstack/deb-sahara
Code Issues Proposed changes

[DOC] Cleanup time for incomplete clusters

Browse Source 
Cleanup time for incomplete clusters feature documented.
closes-bug: 1185909

Change-Id: I785b25b30e88cf0604236d34aaf3170b990b21d3
This commit is contained in:
Michael Ionkin
2016-07-11 18:00:16 +03:00
parent 0f86ad2339
commit c90a1da596
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/userdoc/advanced.configuration.guide.rst
View File

@@ -585,3 +585,21 @@ CORS specification`_.
.. _Administrator Guide: http://docs.openstack.org/admin-guide/cross_project_cors.html
.. _W3C CORS specification: www.w3.org/TR/cors/
Cleanup time for incomplete clusters
------------------------------------
Sahara provides maximal time (in hours) for clusters allowed to be in states
other than "Active", "Deleting" or "Error". If a cluster is not in "Active",
"Deleting" or "Error" state and last update of it was longer than
"cleanup_time_for_incomplete_clusters" hours ago then it will be deleted
automatically. You can enable this feature by adding appropriate config
property in the ``default`` section (by default it set up to ``0`` value which
means that automatic clean up is disabled). For example, if you want cluster to
be deleted after 3 hours if it didn't leave "Starting" state then you should
specify:
.. sourcecode:: cfg
[DEFAULT]
cleanup_time_for_incomplete_clusters = 3