The multi-stage lifecycle management of Core On-Demand encompasses the entire operational lifespan of Core On-Demand instances, commencing with initial deployment and concluding with eventual deletion.
This lifecycle begins with the allocation of cloud resources when a customer creates a Core On-Demand instance. This foundational step establishes the necessary groundwork for subsequent resource allocation, which is initiated upon customer configuration of VPN connectivity and deployment of customer’s core network.
The Core On-Demand ecosystem will continue its evolution by incorporating new features, enhancing scalability and maintainability, and adopting emerging cloud-native patterns. As a result, throughout its lifecycle, Core On-Demand will be subject to periodic updates and enhancements of both infrastructure and service to introduce new features and apply critical security patches. Ericsson is responsible for releasing new versions of Core On-Demand. Google Cloud services handle the release of infrastructure-related versions, ensuring the underlying cloud environment remains robust and capable of supporting evolving Core On-Demand functionalities.
To maintain stability and continuity, the Core On-Demand version management framework also supports the capability to roll back to previous versions should any issues arise following an upgrade.
Customers initiate the decommissioning of a Core On-Demand instance when it's no longer needed, ensuring systematic removal of all associated cloud resources. This phase includes the deletion or archiving of data in accordance with established retention policies and compliance requirements. Once a Core On-Demand instance is decommissioned, the process cannot be reversed, and a new instance must be created if needed.
Next: Data handling