Discover Account Resources in DZS Cloud RO

DZS Cloud Orchestration can discover the DZS Cloud RO CNFs or VNFs when they are provided with an ETSI-based data model.

Discover Resources for All Accounts

  1. On the Launchpad menu, click DATACENTERS.

  2. Open an account to display the resources discovered from that account.

  3. When the account is connected successfully, click to start discovering resources.

    A pop-up screen appears.

  4. Click DISCOVER and Discovery is initiated.

  5. Once Discovery is complete, the status appears at the top of the screen. Go to the RESOURCE tab to see all of the discovered resources for the account.

    The RESOURCE tab displays resources available to map to service elements during instantiation. This information allows a user to map resources to service elements when an operator does not have direct access to a VIM. This information includes:

    • VM image name, if available

    • The IP address(es) for the server interfaces.

    • The Management IP of the server.

    • Router details if accessible.

    • Additional details in the container resources and added services details.

The examples below display the main resources used for discovery design (server, volume, network and helm).

Openstack VMs

Openstack Volumes

Openstack Networks

Kubernetes Helm

Kubernetes Pods

Kubernetes Networks

 

 

 

 

 

 

 

 

 

 

 

 

 

DZS Cloud Orchestration allows operators to discover resources after adding existing resources into a running NS during instantiation. See Map Service Elements to Existing Resources for details on this process.

Discover Resources for Kubernetes Accounts

Follow the process in the Discover Resources for All Accounts to discover resources for a Kubernetes account. Some of the resources listed in the discovery section are not applicable for Kubernetes Accounts.

The following resources:

  • are applicable for Kubernetes accounts but they are currently not supported as part of the Kubernetes Account discovery: role, security-group (Kubernetes: network-policy), placement-group-vim-availability

  • are not applicable for Kubernetes Account discovery: flavor, interface, image

Some of the resource names are different for a Kubernetes account. Refer to the list below to identify the meaning in a Kubernetes Account.

  • Server = Pod

    • Id= Pod ui (id and name both show the interface name because there is no uuid for an intf.)

    • Name = Pod name (id and name both show the interface name because there is no uuid for an intf.)

    • Volume = persistent-volume-claim attached to the pod.

    The Network associated with the pod is fetched form metadata: annotations: k8s.v1.cni.cncf.io/networks. It will also show the default-k8s-nw. The interface is fetched from metadata: annotations: k8s.v1.cni.cncf.io/networks-status.

  • Network = net-attach-def (network definitions)

    • List subnet = This is applicable if the configuration carries ipam dict. This shows the default nw ‘default-k8s-network’ and the attached id, subnet, etc.

  • Volume = persistent-volume

  • Public-ip = load-balancer’s ingress ip