Networking models
You can find information on the models used for BMC Network Automation cloud implementations in the BMC Network Automation online technical documentation topics listed in the following table:
Model | Description | For more information |
---|---|---|
Pod | A pod is composed of the following types of elements: name, ID, site ID, parameters, resource collections, nodes, pairs, and NIC segments. A pod also maintains a reference to the name of the blueprint which created it. A pod name is unique among all pods. The ID is also unique among all pods, and is a number generated by BMC Network Automation. The site ID must refer to a BMC_PhysicalLocation object in the CMDB (or it can be null if the site is unknown). One is free to modify or delete the blueprint used to create a pod without affecting the pod. | Pod model |
Network container | A container is composed of the following types of elements:
A container also maintains a reference to the name of the blueprint from which it was created. A container name must be unique among all containers. The ID is a number generated by BMC Network Automation that also is unique among all containers. The type is a string value used purely for self documenting purposes. You can modify or delete the blueprint used to create a container without affecting the container that was created earlier. The structure of container blueprints mirrors the structure of containers, but it represents a reusable formulation of the information that is present within a container, which is pod-independent. | Container model |
For descriptions of the use cases for the interactions between BMC Network Automation and BMC Cloud Lifecycle Management, see Use cases in the BMC Network Automation online technical documentation.
Comments
Log in or register to comment.