You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This page contains details of planning and implementation of the upgrade/rollback functionality for instances in ACM-R. Rest interface users will be able to call a new endpoint in order to trigger the moving/migration of an instance from a source composition definition to a target composition definition. In this way, the migration of the instance will support both an upgrade and rollback of the instance in question. Calls to migrate the instance will take place on an instance-by-instance basis. The caller will have to supply the following parameters when making the call to upgrade an instance.

  • Source Composition Definition Id - The composition that the instance is currently based on.
  • Target Composition Definition Id - The composition that the instance is to be migrated to.
  • Instance Id - The Id of the instance that the caller wishes to migrate.

This operation will only be possible if the source composition id, target composition id and the instance id exist in ACM.

Upgrade/Rollback Sequence Diagram

Create New Composition type for Upgrade UserRest UserRest ACM ACM Participants Participants DB DB Existing Composition Upload Functionality Composition Definitions Saved Definition Prime Definition Prime Definition Upgrade or Rollback per Instance Migrate Instance (InstanceId, sourceCompId, targetCompId) Instance migration from source to targetcomposition type. Could also be rollback alt["instance Id and Composition Ids exist"] 202 Async Operation Definition Validation (v1 no new elements/structure) Comp Def IDs change for instance and AC Element Move from source to target compostion Move completed 400 Bad Reqest

  • No labels