The manage editions page shows details of each edition of an application. Edition management supports two interruption-free rollout options and a feature to validate an application before putting it into production. With this page you can move an edition through a lifecycle, for example, activation, validation, rollout, and deactivation. To view this page, click Applications > Edition control center > application.
This page displays the following information:
Edition | Name of the edition. For example, 1.0. |
Description | User-provided description of edition. |
Target | Deployment targets to which edition's modules are mapped. That is, servers or cluster on which this edition is installed. |
State | Current state of edition: Active, validation, inactive |
Status | Current status of edition: Unavailable, stopped, running |
Changes an edition state from inactive to active. Only active editions can be started.
Changes an edition state from inactive to validation. Entering validation mode creates a clone of the edition's current deployment targets and prepares the edition to be started on the cloned deployment targets for validation. When an edition that is in validation mode is rolled out, the rollout acts on the original deployment targets and the cloned deployment targets are deleted.
Changes an edition state from inactive to active. You can use either atomic or group rollout. Group rollout results in servers being upgraded to the new edition at the same time. Each server in the group is quiesced, drained, stopped, and reset. Atomic rollout replaces half the servers in the deployment target at a time. The edition that is replaced is put into the inactive state. The replacement is done cooperatively with the on demand router to ensure that no application requests are lost during the edition transition. This rollout strategy ensures no loss of service for single server deployment targets.
Changes an edition state from active to inactive. Inactive editions cannot be started.