Publisher Resource Preview Management feature

This article introduces the publisher resource preview management feature in Azure Operator Service Manager. The publisher API offers partners a seamless experience for onboarding network functions (NFs) and network service designs (NSDs). The publisher API preview feature enables publishers to manage NF artifacts across various lifecycle states. With the ability to control deployments, access privileges, and version management, partners can provide a smooth experience for their customers while maintaining the quality and stability of their offerings.

Considerations for tenants, subscriptions, and regions

• Publisher NSDV and NFDV resources must be in the same Azure tenant as site network service (SNS) resources.

• NSDV and NFDV states are key for cross-subscription:

  • Preview: The SNS is deployable in the same subscription as the NSDV or NFDV.
  • Active: The SNS is deployable in any subscription.

• Publisher resources can be in different Azure Core or Azure Operator Nexus regions from SNS resources.

• Publisher names must be unique within a region.

• SNS resources can reference configuration group values (CGVs) from any region, but they can reference site resources only from the same region.

• CGVs can reference a configuration group schema (CGS) in any region.

• Network functions:

  • Can reference an NFDV from any region.
  • Must reference Azure Stack Edge from the same region, if they're hosted on Azure Stack Edge.

• The Azure Resource Manager template within a virtualized network function (VNF) must deploy resources to the same region as the network function.

• Containerized network functions (CNFs) can reference a custom location from any region.

NFDV and NSDV states

Artifact manifest states

• Uploading means the state is mutable and the artifacts within the manifest can be altered.
• Uploaded means the state is immutable and the artifacts within the manifest can't be altered.

Immutable artifacts are tested artifacts that can't be modified or overwritten. Use of immutable artifacts with Azure Operator Service Manager helps ensure the consistency, reliability, and security of its artifacts across environments and platforms. NFDVs and NSDVs that have a version state of Active are enforced to deploy immutable artifacts.

Update the artifact manifest state

To change the state of an artifact manifest resource, use the following Azure CLI command:

  az aosm publisher artifact-manifest update-state \
    --resource-group <myResourceGroupName> \
    --publisher-name <myPublisherName> \
    --artifact-store-name <myArtifactStoreName> \
    --name <myArtifactManifestName> \
    --state Uploaded

NFDV and NSDV state machine

• Preview is the default state.
• Deprecated is a terminal state but can be reversed.

Update the NFDV state

To change the state of an NFDV resource, use the following Azure CLI command:

  az aosm publisher network-function-definition version update-state \
    --resource-group <myResourceGroup> \
    --publisher-name <myPublisherName> \
    --group-name <myNetworkFunctionDefinitionGroupName> \
    --version-name <myNetworkFunctionDefinitionVersionName> \
    --version-state Active | Deprecated

Update the NSDV state

To change the state of an NSDV resource, use the following Azure CLI command:

  az aosm publisher network-service-design version update-state \
    --resource-group <myResourceGroup> \
    --publisher-name <myPublisherName> \
    --group-name <myNetworkServiceDesignGroupName> \
    --version-name <myNetworkServiceDesignVersionName> \
    --version-state Active | Deprecated