What is Life Cycle State?
Life cycle states
A service's Life Cycle State indicates the current status of the service or tunnel as it transitions from the planning phase to the deployment phase and beyond. The following states may be observed:
-
During the service or tunnel creation process, a user can save their initial configurations within service management (an associated intent instance is created). The entity name will be reserved, and the user will be able to resume creation when desired. Entities in a Saved state can be deleted, or modified and saved again. When configuration is complete, Saved entities can transition to either a Planned or Deployed state.
-
Newly-created services or tunnels, or services or tunnels in a Saved state, can transition to a Planned state. In this state, an associated intent instance is created in NSP's Network Intents function, but the entity is not deployed to the network. While in a Planned state, the entity's resources are reserved, and therefore cannot be used by any other entity. Entities in a Planned state can be deleted (in addition to deleting the entity from service management, this also deletes the intent instance and removes the resource reservations), or modified and kept in a Planned state. When configuration is complete, Planned entities can transition to a Deployed state.
-
Services or tunnels in a Planned state can transition to a Deployed State. In this state, the desired configuration is sent down to the network and synchronized. Entities in a Deployed state must transition to a Removed state before being deleted. If a Deployed entity is modified, it will no longer be aligned with the associated intent instance. At this point, the user can either save their changes (which will place the entity in the Deployed-Modified state until network synchronization occurs), or redeploy the entity (which keeps the entity in the Deployed state by triggering network synchronization).
-
Services or tunnels in a Deployed-modified state have been modified by the user, but are not synchronized to the network. Entities in a Deployed-modified state must transition to a Removed state before being deleted. Deployed-modified entities can be further modified and saved again, (which keeps the entity in the Deployed-Modified state until network synchronization occurs), or redeployed (which transitions the entity to the Deployed state by triggering network synchronization).
-
Services or tunnels in a Removed state can be deleted. In this state, the entity is removed from the network, but its resources remain reserved and its associated intent instance continues to exist. Removed entities can be deployed/redeployed (which transitions the entity to the Deployed state) or modified and saved (which keeps the entity in the Removed state).
NOTE: Services in a Removed state will display an Operational State of 'Unknown'.
© 2024 Nokia. Nokia Confidential Information
Use subject to agreed restrictions on disclosure and use.