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

Compare with Current View Page History

« Previous Version 7 Next »

This page contains details of planning and implementation of the migration 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. 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 migrate an instance.

  • Source Composition Definition Id - The Id of the composition that the instance is currently based on.
  • Target Composition Definition Id - The Id of 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 is primed
  • the target composition is primed and contains the same element definitions present in the source composition
  • the instance is deployed and based on the the source composition

Migration Sequence Diagram

Note: The functionality for the upload of a new composition definition already exists


Migration Sequence UserRest UserRest ACM ACM DB DB Participants Participants Create New Composition type for Migration Composition Definitions Saved Definition Prime Definition Prime Definition Migration per Instance Migrate Instance (InstanceId, sourceCompId, targetCompId) Instance migration from source to targetcomposition type. alt["instance Id and Composition Ids exist"] 202 Async Operation Definition Validation (v1 no new elements/structure) instance and AC Element will be set in a transitional state (UPGRADING) Move from source to target compostion Move completed instance and AC Element will be set in a final state (DEPLOYED)and Comp Def IDs change for instance and AC Element 400 Bad Reqest

  • No labels