Using your IaaS architect privileges, you give users minimum and maximum parameters for memory and the number of allowed CPU's. This conserves resources, but also accommodates your user's needs.

Software architects and application architects are not allowed to configure machine components, but they can reuse blueprints that contain machines components. When you finish editing your machine component, you publish your blueprint so other architects can reuse your machine blueprint to design their own catalog items. Your published blueprint is also available to catalog administrators and tenant administrators to include in the service catalog.


  1. Click the Machine Resources tab.
  2. Specify CPU settings for provisioned machines.
    1. Enter 1 in the Minimum text box.
    2. Enter 4 in the Maximum text box.
  3. Specify memory settings for provisioned machines.
    1. Enter 1024 in the Minimum text box.

      This field is automatically populated based on the memory of your template.

    2. Enter 4096 in the Maximum text box.
  4. Specify storage settings for provisioned machines.

    Some storage information is populated based on the configuration of your template, but you can add additional storage.

    1. Click the New icon (Add).
    2. Enter 10 in the Capacity (GB) text box.
    3. Click OK.
  5. Click Finish.
  6. Select the row containing CentOS on vSphere and click Publish.


You created a catalog-ready blueprint to deliver cloned vSphere CentOS machines to your users and to reuse in other blueprints as the standard for CentOS machines.

What to do next

Using your tenant administrator privileges, create a catalog service for architects to validate their blueprints. Publish your CentOS on vSphere machine blueprint as a catalog item and request it to verify your work. See Scenario: Configure the Catalog for Rainpole Architects to Test Blueprints.