Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Create a custom resource block

Create a custom resource block

The base system provides several resource blocks that you can use directly or modify to meet your needs. You typically do not create a new, custom resource block.

Before you begin

Role required: sn_cmp.cloud_service_designer

About this task

Use the steps in this procedure that apply in your case and skip steps that you do not need.


  1. Navigate to Cloud Management > Cloud Service Design > Resource Blocks and click New.
  2. On the General Information tab, enter a unique and meaningful Name and Description for the resource block, and then enter the following settings:
    Layer Tag that represents the type of resource block:
    • Application: Layer that represents resources that are applications. For example, the 'PetStore' application might exist on a Tomcat or WebLogic platforms.
    • Platform: Layer that represents resources that are typically hosted on a virtual server like MySQL, Tomcat, or Apache.
    • Logical DataCenter: Layer that represents resources that are datacenters like AWS, Openstack, Azure, or vSphere.
      Note: The term "Logical" is used to indicate that, when the resulting catalog is eventually instantiated, the resource block can implement a datacenter from any supported provider that the requester specifies. That is, the resource block that represents the datacenter is "cloud-agnostic."
    • Virtual Infrastructure: Layer that represents resources that are virtual and still provide infrastructure for the virtual world like NetApp SVM, NetApp CDOT, CISCO ICF Cloud, or VMware NSX.
    • Virtual Workload: Layer that represents resources that are hosted on a datacenter. For example, Virtual Server, Storage Volume, Network, or Gateway.
    • Applications are deployed on Platforms.
    • Platforms are deployed on Logical Datacenters or Virtual Infrastructures.
    CI type Optional: CI type that the resource block represents. When the requester launches a stack, the specified CI type is implemented.
    Interface Default Guest interface (Cloud API interface) to use when you add the resource block to a blueprint.

    Any resource that supports a Host interface that matches the specified Guest interface is a potential host for the resource block.

    Note: If the interface does not appear in the list, you can Create a custom guest interface.
    Create interface Select the check box to create a custom guest interface. See Create a custom guest interface for details.
    Host interface Interface that a host must present to be able to host the resource block.
  3. Right-click the header and select Save.
  4. In the related lists on the Resource Block form, update the settings that apply in your case and skip the lists that are correctly configured for your needs.
    Table 1. Related lists on the Resource Block form
    Related list Description
    Resource Guest Interface Specify the interfaces (endpoints) that the resource block can offer to other resource blocks to consume. For example, a datacenter resource block might offer a compute interface, a network Service Container interface, and a firewall interface.
    Note: In the unlikely case that the interface that you need does not appear in the list, you can Create a custom guest interface.
    Host Resource Host resource types that are potential hosts for the resource block. (For example, a virtual server can be hosted on three different types of datacenter that you specify here).

    Only hosts that support the Host interface that you specified appear in the list.

    For instructions, see Specify a host resource for a resource block.
    Supported Capacity Types This setting applies only to datacenters. Specify the capacity types that the datacenter can support. The choices are:
    • Compute
    • Load Balancer
    • Network
    • Storage
    Resource Bindings Specify the resources that the resource block should be allowed to connect to. Only resources that support the Guest interface that you specified appear in the list. For instructions, see Specify bindings for a resource blocks.
    Resource Endpoint Mappings A resource block can implement multiple endpoints. For example, a VM could implement a ISCSI endpoint, Block endpoint, and NFS endpoint. For instructions, see Configure endpoint operation mapping.
  5. On the Operations tab, specify the operations that the resource block supports. An operation signature consists of input parameters, steps, and output attributes for a particular interface.
  6. On the Resource Script tab, specify the scripts that perform actions on the resource block. See Add a resource script to a resource block.
  7. When all settings are correct, select Published () to make the resource block available to blueprint designers. The fields become read-only.

What to do next

Add operations that are available for the resource block and run an optional script that performs actions on the resource block.

Updates to site content will be made starting around 4am on January 17th (Pacific Time) and lasting approximately 6 hours.  This site may be intermittently unavailable.