<commit_before>.. raw:: pdf

   PageBreak

.. index:: Stopping Deployment and Resetting Environment

Stopping Deployment and Resetting Environment
=============================================

.. contents :local:

.. _Stop_Deployment:

Stopping Deployment from Web UI
-------------------------------

After clicking "Deploy changes" and deployment itself starts, a small red
button to the right of the progress bar will appear:

.. image:: /_images/stop_deployment_button.png
  :align: center

By clicking this button, you may interrupt deployment process (in case of any
errors, for example). This may lead to two possible results:

1. If no nodes have finished deployment (reached "ready" status), all nodes
   will be rebooted back to bootstrap. The environment will be reset to its
   state right before "Deploy Changes" was pressed. The environment may be
   redeployed from scratch. Two things will happen in UI:

    * First, all nodes will become offline and will eventually return back
      online after reboot. As you can't deploy an environment which includes
      offline nodes, the next deployment should be started after all nodes
      have been successfully discovered and report as online in UI.
    * Second, all settings will be unlocked on all tabs and for all nodes, so
      that the user may change any setting before starting a new deployment.

This is quite similar to resetting the environment (:ref:`Reset_Environment`).

2. Some nodes are already deployed (usually controllers) and have reached
   "ready" status in the UI. In this case, the behavior will be different:

    * Only nodes which did not reach "ready" status will be rebooted back to
      bootstrap and deployed ones will remain intact.
    * Settings will remain locked because they have been already applied to
      some nodes. You may reset the environment (:ref:`Reset_Environment`) to
      reboot all nodes, unlock all parameters and redeploy an environmtent
      from scratch to apply them again.


.. index:: Resetting an environment after deployment

.. contents :local:

.. _Reset_Environment:

Resetting environment after deployment
--------------------------------------

Right now the deployment process may be completed in one of three ways
(not including deleting the environment itself):

1) Environment is deployed successfully<commit_msg>Important note on provisioning interruption<commit_after>.. raw:: pdf

   PageBreak

.. index:: Stopping Deployment and Resetting Environment

Stopping Deployment and Resetting Environment
=============================================

.. contents :local:

.. _Stop_Deployment:

Stopping Deployment from Web UI
-------------------------------

After clicking "Deploy changes" and deployment itself starts, a small red
button to the right of the progress bar will appear:

.. image:: /_images/stop_deployment_button.png
  :align: center

By clicking this button, you may interrupt deployment process (in case of any
errors, for example). This may lead to two possible results:

1. If no nodes have finished deployment (reached "ready" status), all nodes
   will be rebooted back to bootstrap. The environment will be reset to its
   state right before "Deploy Changes" was pressed. The environment may be
   redeployed from scratch. Two things will happen in UI:

    * First, all nodes will become offline and will eventually return back
      online after reboot. As you can't deploy an environment which includes
      offline nodes, the next deployment should be started after all nodes
      have been successfully discovered and report as online in UI.
    * Second, all settings will be unlocked on all tabs and for all nodes, so
      that the user may change any setting before starting a new deployment.

This is quite similar to resetting the environment (:ref:`Reset_Environment`).

2. Some nodes are already deployed (usually controllers) and have reached
   "ready" status in the UI. In this case, the behavior will be different:

    * Only nodes which did not reach "ready" status will be rebooted back to
      bootstrap and deployed ones will remain intact.
    * Settings will remain locked because they have been already applied to
      some nodes. You may reset the environment (:ref:`Reset_Environment`) to
      reboot all nodes, unlock all parameters and redeploy an environment
      from scratch to apply them again.

.. note::

    In Release 4.1, deployment cannot be interrupted during the
    provisioning stage. This means that a user can click on "Stop
    deployment" while nodes are provisioning, but they will be rebooted
    back to bootstrap only when OS installation is complete.


.. index:: Resetting an environment after deployment

.. contents :local:

.. _Reset_Environment:

Resetting environment after deployment
--------------------------------------

Right now the deployment process may be completed in one of three ways
(not including deleting the environment itself):

1) Environment is deployed successfully
{'fraction_non_alphanumeric': 0.08878691141260973, 'fraction_numerical': 0.0015961691939345571, 'mean_word_length': 3.456, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4493373', 'n_tokens_mistral': 1155, 'n_tokens_neox': 1114, 'n_words': 666}