Merge pull request #267112 from MicrosoftDocs/release-operator-5g-core

Release operator 5g core--scheduled release at 4PM of 2/25

Author: huypub

articles/operator-5g-core/concept-centralized-lifecycle-management.md

@@ -0,0 +1,54 @@
+---
+title: Centralized lifecycle management in Azure Operator 5G Core
+description: Outlines the benefit of Azure Operator 5G Core's centralized lifecycle management feature.
+author: HollyCl
+ms.author: HollyCl
+ms.service: azure-operator-5g-core
+ms.topic: concept-article #required; leave this attribute/value as-is.
+ms.date: 02/21/2024
+
+#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
+---
+
+
+# Centralized Lifecycle Management in Azure Operator 5G Core
+ 
+The Azure Operator 5G Core Resource Provider (RP) is responsible for the lifecycle management (LCM) of the following Azure Operator 5G Core network functions:
+- Access and Mobility Management Function (AMF)
+- Session Management Function (SMF)
+- User Plane Function (UPF)
+- Network Repository Function (NRF)
+- Network Slice Selection Function (NSSF)
+- Mobility Management Entity (MME)
+
+ > [!NOTE]
+>  AMF and MME can be deployed as combined network functions by adjusting the helm manifests. 
+
+Lifecycle Management consists of the following operations:
+- Instantiation
+- Upgrade (out of scope for Public Preview)
+- Termination
+
+The Azure Resource Manager (ARM) model that is used for lifecycle management is shown here: 
+
+> [!NOTE]
+> The CNFs are included for Public Preview while the VNFs (VNFAgent and vMME) are targeted for GA release.
+
+:::image type="content" source="media/concept-centralized-lifecycle-management/lifecycle-management-model.png" alt-text="Diagram showing the containerized network functions and virtualized network functions responsible for lifecycle management in Azure Operator 5G Core.":::
+
+Network function deployments require fully deployed local Platform as a Service (PaaS) components (provided by the ClusterServices resource). Any attempt to deploy a network function resource before the ClusterServices deployment fails. ARM templates are serial in nature and don't proceed until dependent templates are complete. This process prevents network function templates from being deployed before the ClusterServices template is complete. Observability deployments also fail if local PaaS deployment is incomplete.
+
+The deployments for cMME and AnyG are variations on the existing helm charts. Creation of these functions is a matter of specifying different input Helm values. The Azure Operator 5G Core RP uses the Network Function Manager (NFM) Resource Provider to perform this activity. 
+
+Azure Operator 5G Core network function images and Helm charts are Azure-managed and accessed by the Azure Operator 5G Core Resource Provider for lifecycle management operations.  
+
+## Local observability
+
+Local Observability is provided by Azure Operator 5G Core Observability components listed in the diagram. Because the Observability function is local, it also available in break-glass scenarios for Nexus where the interfaces can be accessed locally.
+ 
+:::image type="content" source="media/concept-centralized-lifecycle-management/local-observability.png" alt-text="Diagram showing how Azure Operator 5G Core observability components are used in Azure Operator 5G Core." lightbox="media/concept-centralized-lifecycle-management/local-observability.png":::
+
+
+## Next Step
+
+- [Quickstart: Get Access to Azure Operator 5G Core](quickstart-subscription.md)

articles/operator-5g-core/concept-deployment-order.md

@@ -0,0 +1,40 @@
+---
+title: Azure Operator 5G Core Deployment ordering for clusters, network functions, and observability 
+description: Outlines the deployment order for components on Azure Kubernetes Services or Nexus Azure Kubernetes Services
+author: HollyCl
+ms.author: HollyCl
+ms.service: azure-operator-5g-core
+ms.topic: concept-article #required; leave this attribute/value as-is.
+ms.date: 02/21/2024
+
+#CustomerIntent: As a <type of user>, I want <what?> so that <why?>.
+---
+
+# Deployment order for clusters, network functions, and observability 
+
+Mobile Packet Core resources have minimal ordering constraints. To bring up network functions, the cluster services must be already running successfully. The same set of cluster services can be reused for multiple network functions and the cluster services must be deployed on every cluster that hosts the network functions.
+
+## Azure CLI commands used to deploy resources
+
+Use the following Azure CLI commands to deploy resources.
+  
+```azurecli
+{ 
+   [ 
+    Microsoft.MobilePacketCore/clusterServices 
+   ], 
+   [ 
+    Microsoft.MobilePacketCore/amfDeployments 
+    Microsoft.MobilePacketCore/smfDeployments 
+    Microsoft.MobilePacketCore/nrfDeployments 
+    Microsoft.MobilePacketCore/nssfDeployments 
+    Microsoft.MobilePacketCore/upfDeployments 
+    Microsoft.MobilePacketCore/observabilityServices 
+   ]
+```
+
+## Related content
+
+- [Complete the prerequisites to deploy Azure Operator 5G Core on Azure Kubernetes Service](how-to-complete-prerequisites-deploy-azure-kubernetes-service.md)
+- [Complete the prerequisites to deploy Azure Operator 5G Core on Nexus Azure Kubernetes Service](how-to-complete-prerequisites-deploy-nexus-azure-kubernetes-service.md)
+