Using Commit and Regress

Overview

SARK UCS/MVP 2.1.13 provides a commit button on every panel in the server manager, and a regress button in the globals panel. The purpose of the commit is to speed up the deployment of your system. In previous releases Asterisk was updated every time a change was made to the server manager, and this could be fairly slow, particularly with smaller CPU's. In this release Asterisk is only updated when a commit is performed.

<img src="http://81.149.154.14/docs/images/V2.0/commit_regress.jpg"

Commit

The save buttons and the delete buttons update your changes in the panels, but do not update Asterisk. It is the commit button that updates Asterisk with your changes. The save and delete buttons are very quick to update changes, whereas, the commit may take some time. It is recommended that you make all your updates to the system using the save and delete buttons. When you are ready to go live with these updates then perform a commit. The commit button will turn red when there are changes that require a commit.

Regress

The globals panel has a regress button. This allows the user to regress to the previous committed setup. A maximum of five regressions can be performed. The regress button will turn red when a regression can be performed.