Container management blueprints

Default Blueprint for Container Infrastructure Services

Use this default blueprint to create a technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

• Start node: Namespace of type Kubernetes Namespace
• Traversal path and connected nodes: Associated Clusters, Deployment, Software Pod, Host, Virtual Machine, and Host, as shown in the following image:
  
• Default filter rules: The start node has a set filter criterion, as shown in the image. When creating the service model, the service designer must select the names of Kubernetes(K8S) Namespaces as input.
  

Default Blueprint for Kubernetes Infrastructure

Use this default blueprint to create a business application, business service, or technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

• Start node: Namespace of type Kubernetes Namespace
• Traversal path and connected nodes: Associated Clusters, Load Balancer member nodes, Deployments, Virtual Machine, Administrative Collection, and so on, as shown in the following image:
  
• Default filter rules:
  • The start node has a set filter criteria, as shown in the image. This criteria automatically filters Kubernetes Namespaces. Additionally, when creating the service model, the service designer must select the names of Kubernetes(K8S) Namespaces as input.
    
    
    
  • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
    
    

Earlier version of the blueprint

Default Blueprint for Kubernetes to VM to Switch

Use this default blueprint to create a business application or business service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

• Start node: Namespace of type Kubernetes Namespace
• Traversal path and connected nodes: Associated Clusters, Load Balancer member nodes, Deployments, Virtual Machine, Administrative Collection, and so on, as shown in the following image:
  
  
• Default filter rules:
  • The start node has a set filter criterion, as shown in the image. When creating the service model, the service designer must select the names of Kubernetes(K8S) Namespaces as input.
    
    
    
  • The default Filter by Kind link rule is enabled between the Namespace and Cluster nodes connection, as shown in the following image:
    
    
    

  • The default Filter by Kind link rule is enabled between the Namespace and Deployment and between the Deployment and Software Pod nodes connections, as shown in the following image:

    
    
    

  • The default Filter by Kind link rule is enabled between the Software Pod and Host nodes connection, as shown in the following image:
    
    

Default Blueprint for OpenShift Namespace

Use this default blueprint to create a business application, business service, or technical service.

Before you begin

Discover CIs, CI Kinds, and their relationships through BMC Helix Discovery or any other supported data ingestion mechanism such as API calls.

Nodes, connections, and filters

The blueprint contains information about interconnected nodes, their relationships, and the default filter criteria.

• Start node: Namespace of type OpenShift Namespace Namespace
• Traversal path and connected nodes: Associated Clusters, Load Balancer member nodes, Deployments, Virtual Machine, Administrative Collection, Storage member nodes, Cloud Service member nodes, Management Controllers, Hardware Containers, Hosts, Network Interfaces, Network Devices, and so on, as shown in the following image:
  
  
• Default filter rules:
  • The start node has a set filter criteria, as shown in the image. This criteria automatically filters OpenShift Namespaces. Additionally, when creating the service model, the service designer must select the names of OpenShift Namespaces as input.
    
    
    
  • The default Filter by Kind link rule is enabled between the Virtual Machine and Host node connection, as shown in the following image:
    
    

Earlier version of the blueprint

Where to go from here

Creating-service-models