13 – Service templates > 13.3 Service template references > Fields: Required resources (storage)

Fields: Required resources (storage)

Path: Catalog > Service Management > New/Edit > Resources

Path: Catalog > New Service Template > Resources

The Resources tab is populated with different fields based on the template type you specify in the Template properties (see Fields: Template properties). When you choose "Storage" as the template type, the Resources tab is populated with the following required resource fields.

You will notice that many of the Field type and ID fields are already filled and cannot be edited. The reason for this is that each of these fields are required and must be included in every storage template. If you want to add additional fields to the template, you can click Add field under the "Catalog options" heading (for more information, see Adding new fields).

Image 12-2: Required resources for storage templates

Click to enlarge

Header

This section will appear in the user form as the text heading.

Header caption

Lets you specify the text that will appear as the form heading.

Mount location

This section will appear in the user form as a text box that lets users specify the mount location.

Label

Lets you specify the descriptive label (or name) of the field. What you specify in this field is what the user will see in the form.

By default, the label is "Mount location."

Default value

Lets you specify a value that will be pre-populated in the field when the user opens the form.

If you have not selected the Editable by user option (meaning the user cannot edit the field), then the default value will be the only option for the user. If you want the user to be able to choose from more than the default value, make sure you select the Editable by user option.

Validation

Lets you specify a regular expression (using JavaScript regex syntax) that will check and validate the user input on this field.

For example, if you want users to stop providing invalid drive letters for mount points, you can enter a regular expression like this:

[a-zA-Z]{1}[\:]{0,1}

This validation causes Viewpoint to notify users when they enter something invalid in the field. (For information about regular expressions, please see http://www.regular-expressions.info/.)

Storage Type

Label

Lets you specify the descriptive label (or name) of the field. What you specify in this field is what the user will see in the form.

By default, the label is "Storage Type."

Default value

Lets you specify which storage type will be pre-populated in the field when the user opens the form. The possible storage types that you can choose from are pulled from Moab Web Services.

If you have not selected the Editable by user option (meaning the user cannot edit the field), then the default value will be the only option for the user. If you want the user to be able to choose from more than the default value, make sure you select the Editable by user option.

Size (GB)

Label

Lets you specify the descriptive label (or name) of the field. What you specify in this field is what the user will see in the form.

By default, the label is "Size (GB)."

Default value

Lets you specify a number value that will be pre-populated in the field when the user opens the form.

You must make sure that the Default value is greater than or equal to the Minimum value and less than or equal to the Maximum value.

If you have not selected the Editable by user option (meaning the user cannot edit the field), then the default value will be the only option for the user. If you want the user to be able to choose from more than the default value, make sure you select the Editable by user option.

Minimum

Lets you specify the minimum value that Viewpoint will accept from the user.

For example, if you specify a minimum value of 100 GB, the user will not be allowed to request less than 100 GB of storage.

Maximum

Lets you specify the maximum value that Viewpoint will accept from the user.

For example, if you specify a maximum value of 400 GB, the user will not be allowed to request more than 400 GB of storage.

Step

Lets you specify a number interval that the number spinner uses to move up or down. For example, if you specify "10," the number spinner will move up or down by ten integers each time the user clicks up or down.

The spinner will not allow the user to go above the Maximum value or below the Minimum value.

Enforce Step

Lets you enforce that the users cannot specify a number value (by typing it in) that does not conform to the Step settings you specify.

Features

Label

Lets you specify the name of the field that the user will see. By default, the label is "Features."

Default feature tags

Lets you type the names of feature tags to be attached to a service when the template is submitted.

Attaching feature tags to services enables Moab to locate instances of the feature when it follows any configured feature-based rules. This is an auto-complete field that will suggest tags as you type. To select the suggested feature, click Enter. To remove a tag, click the X next to it.

Additional options

Some fields have the one or more of the following additional options:

Editable by user

Lets you specify whether or not the user will be allowed to modify the specifications of the resource.

If you select this option, you must be sure you specify a default value. Failing to do this will leave a blank field that the user will not be able to do anything with.

Schedulable resource

Lets you specify whether the field represents a schedulable resource. When a field is marked as a schedulable resource, its value must be an integer. If you do not select this option, Viewpoint assumes the field is a variable, and its value can be non-numeric.

The Schedulable resource option is, in essence, an attribute that allows you to define the type of data being written. For example, if you select Schedulable resource when defining a text field with the ID set to "bob" and the Value set to "5", then the service request would have an "attributes" section like this (with the "bob" key-value pair written to the resources object in the service request):

attributes: {

  moab: {

    job: {

      resources: {

        bob: "5"

      },

      variables: {

      }

    }

  }

}

If you left the Schedulable resource option unchecked, then the same input field would be interpreted as a variable (written in the variable object):

attributes: {

  moab: {

    job: {

      resources: {

      },

      variables: {

        bob: "5"

      }

    }

  }

}

Visible to user

Lets you specify whether or not the field will appear in the user service template form.

When you select this option, the Editable by user option will automatically clear. (If a user cannot see the field, they cannot edit it.)

Related topics