Package types (0.2.2)

Request object for ApplyDeployment. The resources in given deployment gets applied to Orchestration Cluster. A new revision is created when a deployment is applied.

Request for applying a hydrated deployment.

Request object for ApproveBlueprint.

A Blueprint contains a collection of kubernetes resources in the form of YAML files. The file contents of a blueprint are collectively known as package. A blueprint can be a) imported from TNA's public catalog b) modified as per a user's need c) proposed and approved. On approval, a revision of blueprint is created which can be used to create a deployment on Orchestration or Workload Cluster.

BlueprintView defines the type of view of the blueprint.

Values: BLUEPRINT_VIEW_UNSPECIFIED (0): Unspecified enum value. BLUEPRINT_VIEW_BASIC (1): View which only contains metadata. BLUEPRINT_VIEW_FULL (2): View which contains metadata and files it encapsulates.

Request object for ComputeDeploymentStatus.

Response object for ComputeDeploymentStatus.

Request object for CreateBlueprint.

Request object for CreateDeployment.

Message for creating a EdgeSlm.

Message for creating a OrchestrationCluster.

Request object for DeleteBlueprint.

Message for deleting a EdgeSlm.

Message for deleting a OrchestrationCluster.

Deployment contains a collection of YAML files (This collection is also known as package) that can to applied on an orchestration cluster (GKE cluster with TNA addons) or a workload cluster.

DeploymentLevel of a blueprint signifies where the blueprint will be applied.

Values: DEPLOYMENT_LEVEL_UNSPECIFIED (0): Default unspecified deployment level. HYDRATION (1): Blueprints at HYDRATION level cannot be used to create a Deployment (A user cannot manually initate deployment of these blueprints on orchestration or workload cluster). These blueprints stay in a user's private catalog and are configured and deployed by TNA automation. SINGLE_DEPLOYMENT (2): Blueprints at SINGLE_DEPLOYMENT level can be a) Modified in private catalog. b) Used to create a deployment on orchestration cluster by the user, once approved. MULTI_DEPLOYMENT (3): Blueprints at MULTI_DEPLOYMENT level can be a) Modified in private catalog. b) Used to create a deployment on orchestration cluster which will create further hydrated deployments. WORKLOAD_CLUSTER_DEPLOYMENT (4): Blueprints at WORKLOAD_CLUSTER_DEPLOYMENT level can be a) Modified in private catalog. b) Used to create a deployment on workload cluster by the user, once approved.

DeploymentView defines the type of view of the deployment.

Values: DEPLOYMENT_VIEW_UNSPECIFIED (0): Unspecified enum value. DEPLOYMENT_VIEW_BASIC (1): View which only contains metadata. DEPLOYMENT_VIEW_FULL (2): View which contains metadata and files it encapsulates.

Request object for DiscardBlueprintChanges.

Response object for DiscardBlueprintChanges.

Request object for DiscardDeploymentChanges.

Response object for DiscardDeploymentChanges.

EdgeSlm represents an SLM instance which manages the lifecycle of edge components installed on Workload clusters managed by an Orchestration Cluster.

File represents a yaml file present in a blueprint's package.

Configuration of the full (Autopilot) cluster management

Request object for GetBlueprint.

Request object for GetDeployment.

Message for getting a EdgeSlm.

Request object for GetHydratedDeployment.

Message for getting a OrchestrationCluster.

Request object for GetPublicBlueprint.

A collection of kubernetes yaml files which are deployed on a Workload Cluster. Hydrated Deployments are created by TNA intent based automation.

Hydration status.

Request object for ListBlueprintRevisions.

Response object for ListBlueprintRevisions.

Request object for ListBlueprints.

Response object for ListBlueprints.

Request for listing all revisions of a deployment.

List of deployment revisions for a given deployment.

Request object for ListDeployments.

Response object for ListDeployments.

Message for requesting list of EdgeSlms

Message for response to listing EdgeSlms.

Request object for ListHydratedDeployments.

Response object for ListHydratedDeployments.

Message for requesting list of OrchestrationClusters.

Message for response to listing OrchestrationClusters.

Request object for ListPublicBlueprints.

Response object for ListPublicBlueprints.

Configuration of the cluster management

This message has oneof_ fields (mutually exclusive fields). For each oneof, at most one member field can be set at the same time. Setting any member of the oneof automatically clears all other members.

.. _oneof: https://proto-plus-python.readthedocs.io/en/stable/fields.html#oneofs-mutually-exclusive-fields

Configuration of the Master Authorized Network that support multiple CIDRs

Per-Site Status.

Deployment status of NFDeploy.

Represents the metadata of the long-running operation.

Orchestration cluster represents a GKE cluster with config controller and TNA specific components installed on it.

Request object for ProposeBlueprint.

A Blueprint contains a collection of kubernetes resources in the form of YAML files. The file contents of a blueprint are collectively known as package. Public blueprint is a TNA provided blueprint that in present in TNA's public catalog. A user can copy the public blueprint to their private catalog for further modifications.

Request object for RejectBlueprint.

Request object for RemoveDeployment.

Status of a deployment resource.

Represent type of CR.

Values: RESOURCE_TYPE_UNSPECIFIED (0): Unspecified resource type. NF_DEPLOY_RESOURCE (1): User specified NF Deploy CR. DEPLOYMENT_RESOURCE (2): CRs that are part of a blueprint.

Request object for RollbackDeployment.

Request object for SearchBlueprintRevisions.

Response object for SearchBlueprintRevisions.

Request object for SearchDeploymentRevisions.

Response object for SearchDeploymentRevisions.

SiteVersion Hydration is targeting.

Configuration of the standard (GKE) cluster management.

Status of an entity (resource, deployment).

Values: STATUS_UNSPECIFIED (0): Unknown state. STATUS_IN_PROGRESS (1): Under progress. STATUS_ACTIVE (2): Running and ready to serve traffic. STATUS_FAILED (3): Failed or stalled. STATUS_DELETING (4): Delete in progress. STATUS_DELETED (5): Deleted deployment. STATUS_PEERING (10): NFDeploy specific status. Peering in progress. STATUS_NOT_APPLICABLE (11): K8s objects such as NetworkAttachmentDefinition don't have a defined status.

Request object for UpdateBlueprint.

Request object for UpdateDeployment.

Request object for UpdateHydratedDeployment.

Workload status.