Resource blocks

Resource blocks are the building blocks of cloud catalog items. Each resource block is based on a CI type from the CMDB. In a blueprint, each resource block acts as the template for a CI that the user requests as part of a catalog item.

Using resource blocks

You can use the resource blocks that are included with the base system, modify them, or create custom resource block based on CI types. In almost every case, you can use a base-system resource block directly or modify it slightly to meet your needs.

You use resource blocks to:

Resource block operations

Each resource block specifies allowed operations. For example, the Load Balancer resource block provides the following operations: provision, deprovision, register or de-register instances from load balancer, enable SSL, and upload SSL certificate.

Resource blocks in the base system

  • AWS Datacenter
  • Azure Datacenter
  • Chef Server
  • Cloud Resource
  • Compute Security Group
  • Internet Gateway
  • Load Balancer
  • Network
  • Network Interface Card
  • OpenStack Datacenter
  • Route Table
  • Router
  • Storage Volume
  • Subnet
  • Virtual Server
  • vSphere Datacenter

Resource Blocks page

The Resource Blocks page (Cloud Management > Cloud Service Design > Resource Blocks) displays basic information for each resource block. Click a resource block to view or modify its configuration.

Resource Blocks in the blueprint

In a blueprint, each resource block acts as the template for a CI that the user requests as part of a catalog item. In the example, a resource block that represents a virtual server from any provider in the blueprint becomes, in the stack, an actual virtual server from the provider that the requester specified.

In the example blueprint design, the blueprint includes a Virtual Server resource block and a Datacenter resource block. Each resource block carries with it operation configurations, interface configurations, and binding configurations. When you publish the blueprint as a cloud catalog item, a user can request the item. During the process of configuring the item, the user specifies that (for example) the Virtual Server should be an AWS VM and that the Datacenter should be an AWS datacenter in a particular location. When the user clicks the Launch button, the system applies the configuration settings to provision the stack.