You are here: Supporting Documents > Reference Topics > Setting Up the Infrastructure to Meet Your Service Level Agreements > Special Considerations for Service Level Agreements

Special Considerations for Service Level Agreements

One of the most powerful features of Stratus Cloud Workload Services is the ability to customize the Orchestration engine to ensure that your applications are in compliance with special business and infrastructure requirements that are unique to your business. These may include the need for:

Use Appendix C: Mapping Business Requirements into Tag Categories and Tags to list out special considerations. You can group them into custom categories. Create tags under the custom categories, and these are respected by the Orchestration engine for application deployment and management.

Once you have your tree, use it as a guide for adding new categories and tags in the Stratus Management Console. You can change or edit the tree; for more information, refer to "To change the tree" in An Overview of Service Level Availability Requirements.

Additionally, each category can display as a question in the Service Catalog, and your users can narrow down their selection using this custom criteria.

To ensure that a category or tag does not display in the Service Catalog:

  1. In the main menu, click Service Level Definitions to display service levels by category.
  2. Locate the service level definition by typing its name into the search field at the top of the page, or scroll through the listings. Click to select.
  3. Click the > at the left of the service level definition list entry to display the categories associated with the service level definition.
  4. For the move the slider left until it turns gray. This hides the designated category or tag while still enabling the tag to be used on the deployment packages or hypervisors.
  5. Click Confirm.

Custom categories can have binary values, meaning you can only assign one of the tags within a category, or you can multi-assign the tags. The application or hypervisor can have none, some, or all of those values associated with them.

of