Parameters

Provide layered customization using parameters

A parameter passes additional data along with an order, such as text, numbers, and dates. In Cloud Management Platform, the same parameter can behave differently depending on the group ordering it, the environment building it, and the blueprint it belongs to. A parameter may be:

  • Limited to a set of options.
  • Constrained by a minimum, a maximum, or a regular expression, depending on its type.
  • Unconstrained, letting requestors enter any value.
  • Given a value under Global Defaults.
  • Required or optional.
  • Set to Show on Objects, so it appears on the servers and resources where it has been made available, or Available to all servers.
  • Set to Show as Attribute, so it appears on the overview or details tab of the server or resource it is associated with.
  • Set to Allow Multiple Values, so more than one option can be selected at once.

Parameters are added to specific groups and environments and blueprints, where their options and constraints are configured.

Adding and managing parameters

  1. Go to Admin > Parameters.
  2. Select Add.
  3. Fill in the required and optional information.
  4. Select Create to add the new parameter.

Screenshot of the Create New Parameter dialog. (opens full-size image in a new tab)

Parameter display sequence

Customize the sequence in which parameters appear on forms when managing and ordering blueprints.

  1. Go to Admin > Parameter Display Sequence.
  2. Drag the handle at the left of a row to reorder it, or use the move to top and move to bottom arrows.
  3. Select Add to add another parameter to this list.

Parameters that are not on this list appear in alphabetical order below those that are.

Subgroup inheritance of parameters

Groups are hierarchical, and a subgroup inherits its parent group’s parameters and preconfigurations, including any options and constraints set on the parent. This makes it easier to manage orders across many groups. Inheritance is enabled by default. To disable it, go to Admin > Miscellaneous Settings, select the Ordering tab, and clear Inherit Group Parameters.

For example, given the following group structure:

A group hierarchy with group A as the parent of groups B, C, and D (opens full-size image in a new tab)

Groups inherit parameters from parent groups

If you set the CPUs parameter on group A, then groups B, C, and D inherit it. The CPUs parameter, with any options and constraints set on A, appears on orders for group A and all of its subgroups.

Subgroups may add and override their parent’s parameters

If you also set the CPUs parameter on group B with its own options, orders for group B use those options instead, even though the parameter already exists on its parent.

Parameters are always inherited from the nearest ancestor

Once CPUs is overridden on group B, orders from groups C and D show the options and constraints from group B. You can view inherited parameters from a subgroup’s Parameters tab.


Parameter options

How Cloud Management Platform (CMP) decides which values a parameter offers, and the defaults, constraints, and dependencies that shape them

Static options

Define a fixed list of values for a parameter on a group, an environment, or a blueprint

Generated parameter options

Build a parameter’s option list at runtime from a plugin

Parameter templates

Some parameters accept a template instead of a fixed value