Instance Limits

Setting an Instance Limit on an asset will limit how many concurrent instances of an Asset that can be provisioned. This can be used to:

  • Manage usage of an Asset that is constrained due to licensing considerations
  • Manage usage of an Asset that is constrained due to physical resources

Once a instance limit is reached, the deployment runs will remain in the scheduled state until the resource becomes available (i.e another deployment run that uses the resource is released or cancelled). Instance limits are defined for software assets, physical machines (containers), and devices. Instances limits can also be set to unlimited.

How to Set an Instance Limit

To Set an Instance Limit on an Asset via the UI:

  1. Select the Asset you want to modify from the Library in the main navigation menu to the left
  2. Once on the Asset's main page click the edit icon corresponding with the Instance Limits toggle on the right side of the page

To Set an Instance Limit on an Asset via the Properties file:

The instance limit can also be set in the asset.properties file of a software asset before uploading into CONS3RT. Below is an example showing the correct syntax for an instance limit of 5 in an asset.properties file.

# Instance limit expressed as a number (e.g. licensing limitations)
# Comment out for unlimited instances (default: unlimited)
instanceLimit=5

If the instanceLimit is commented out the system will interpret this as unlimited instances, which is the default configuration.

For more information on creating or modifying an asset.properties file see Creating Component Assets, or for a complete example of an asset.properties file, see the Cons3rt GitHub.