Versions Compared

Old Version 4

changes.mady.by.user Aravindhan Ayyanathan

Saved on

compared with

New Version 5

changes.mady.by.user Aravindhan Ayyanathan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...



  1. COMMISSIONED
    rApp will be in this state right after creation. and 
    once the DEPRIMING is completed
  2. PRIMING
    This is a transition state. rApp will be in this 
    state once the PRIMING requested for rApp
  3. PRIMED
    rApp will be in this state once afterthe PRIMING is 
    completed. 
    In this state rApp instances can be 
    created
  4. DEPRIMING
    This is a transition state. rApp will be 
    in this state once the DEPRIMING requested for rApp

...

The rApp Instance lifecycle contains 4 states. The state and transitions are as follows,



  1. UNDEPLOYED
    rApp instance gets created in this state and 
    once the rApp Instance undeploy is completed
  2. DEPLOYING
    This is the transition state. rApp instance will
    be in this state once DEPLOY is requested
  3. DEPLOYED
    rApp instance will be in this state once the 
    rapp instance deployment is completed.
  4. UNDEPLOYING
    This is a transition state. rApp instance will
    be in this state once UNDEPLOY requested for 
    rApp instance


Flows

rApp flow

Create rApp

:

  1. API user creates rApp by sending rApp package
  2. rApp Manager validates the rApp
  3. rApp Manager stores the rApp in the file system if the rApp is valid
  4. API user provided with the status of rApp creation.
  5. API user request to Prime the rApp
  6. rApp Manager fetches the ACM composition from rApp package and 
    creates the ACM composition in ACM-R
  7. rApp Manager gets the ACM composition creation status from ACM-R
  8. rApp Manager request ACM-R to prime the ACM composition 
  9. rApp Manager gets the ACM composition priming status from ACM-R
  10. rApp Manager checks with DME for the unknown information type from rApp package
  11. rApp Manager get the information type availability from DME
  12. API user provided with the status of rApp priming

Delete rApp

:

  1. API user request to Deprime rApp
  2. rApp Manager request ACM-R to deprime the ACM composition 
  3. rApp Manager get the status of ACM composition depriming.
  4. rApp Manager requests ACM-R to delete the ACM composition 
  5. rApp Manager gets the status of ACM composition deletion
  6. API user provided with the deprime rApp status.
  7. API user request to delete the rApp
  8. rApp Manager validates that the rApp is in COMMISSIONED state and 
    there is no rApp Instances are available.
  9. API User provided with delete rApp status

...