Cloud Management resource profiles

Resource profiles are cloud-agnostic definitions that contain the attributes a resource can have. Users select values for these attributes when they order a cloud resource.

You can determine the options that are acceptable for each resource profile. These options limit the choices the user sees when ordering cloud resources. By creating resource profiles, you give your users the flexibility to determine the parameters that best suits their needs, without needing a separate blueprint or catalog item for each variation. For example, you can create a profile named Small VM and map it to a group of hardware types, each with their own values for memory and virtual CPUs for a given cloud account.

Resource types

Each resource profile has different attributes associated with it. The attributes are defined by the resource types that are populated after you run discovery on a cloud account.
Resource profile type Attributes Resource types
Compute The size of computing resources, including the virtual CPUs, memory, and local storage. Hardware Type

[cmdb_ci_compute_template]

OS Operating system images, including the OS type and version, the root device type, and the image source. Image

[cmdb_ci_os_template]

VMWare Virtual Machine Template

[cmdb_ci_vmware_template]

Security group Firewall rules, such as enabling HTTP and HTTPS.

Compute Security Group Template

[cmdb_ci_security_grp_template]

Storage Volume Template

[cmdb_ci_volume_template]

Application Application Template

[sn_cmp_application_template]

Resource profile mappings

Resource map the following together:
  • A cloud account.
  • A logical datacenter in the cloud account.
  • A specific resource type in the CMDB. This resource type provides the attributes.
  • An optional pricing value that appears to end users when they order a resource with the profile.

By default, Cloud Management associates templates to profiles for AWS and Azure after Discovery is run. For other clouds, such as Google cloud, etc., you must associate the profile with the correct template and datacenter manually.