Problem Description

All blueprints which are deployed must be assigned a Lease End Date so that their quoted consumption costs can be reserved out of a budget for the specified period that they run. Pre-reserving costs out of budgets ensures that budget overspending cannot occur.

The Lease End Date is displayed at the time of deployment and is a mandatory field. Users will observe that they must specify a Lease End Date value, which cannot be indefinite/forever.

Cause

This is by design.

Buttonwood's governance framework doesn't allow for leases to run forever. This ensures that workloads are not left forgotten, and hence consuming costs.

Buttonwood also pre-reserves consumption costs out of budgets to ensure that budget overspending cannot occur.

Resolution

Users will need to discuss with Broker administrators and configure an appropriate Cost Centre and Budget model to support the tracking of costs for workloads which need to run for extended periods of time.