You are here: Supporting Documents > Reference Topics > Tags Overview > Tags Categorization

Tags Categorization

This page contains the default tag categories having rules associated with them. Tag categories comprise the service catalog by adding categories, or by editing an existing category and its tags. Default tag categories include:

Availability level (strategy to implement)
Types of hypervisors to consume
Recovery mode (desired behavior for failure recovery)

Availability: This represents the service level agreement, and is used for grouping applications throughout the user interface.
Hypervisor group: An internal method of organizing hypervisors
Application category: An internal method of organizing the Service Catalog Applications, displayed in the Application Owner Service Catalog

Fault-Tolerant/Availability Tags

The following table lists availability tags and the rules associated with them.

Tag Category	Tags	Deployment Entity	Infrastructure Entity	Functional Description
Availability	Mission Critical, Business Critical, Commodity	Deployment Package / Application Volume	Hypervisor VolumeType (storage device)	The Availability tag may have an imperfect match: Commodity can go on Business Critical or Mission Critical Business Critical can go on Mission Critical If there is no availability tag requested on the instance, the system looks for the availability tag of the application.

Tag
Category

Monitoring and Recovery Tags

The following table lists monitoring and recovery tags and the rules associated with them.

Tag Category	Tags	Deployment Entity	Infrastructure Entity	Functional Description
Recovery Mode	Auto-restart instance Do not restart/recover instance	Deployment Package Image Instance	n/a	Describes the recovery mode implemented when an instance is evacuated to another compute node. The Orchestrator can restart the instance on another node if your configuration supports it. RECOVERY_MODE_RESTART requires a perfect match where the hypervisor has shared storage (LOCAL_STORAGE_GROUP). RECOVERY_MODE_NONE may have a perfect match where the hypervisor has shared storage (LOCAL_STORAGE_GROUP) or no shared storage (HYPERVISOR_LOCAL_STORAGE_GROUP_NONE). The recovery mode does not apply to KVM-FT instances, because KVM-FT itself manages recovery.

Tag
Category

Tags

Deployment
Entity

Infrastructure
Entity

Functional
Description

Recovery Mode

Auto-restart instance

Do not restart/recover instance

Deployment Package Image

Instance

n/a

Describes the recovery mode implemented when an instance is evacuated to another compute node. The Orchestrator can restart the instance on another node if your configuration supports it.

RECOVERY_MODE_RESTART requires a perfect match where the hypervisor has shared storage (LOCAL_STORAGE_GROUP).

RECOVERY_MODE_NONE may have a perfect match where the hypervisor has shared storage (LOCAL_STORAGE_GROUP) or no shared storage (HYPERVISOR_LOCAL_STORAGE_GROUP_NONE).

The recovery mode does not apply to KVM-FT instances, because KVM-FT itself manages recovery.

Product Support and Downloads Web: http://www.stratus.com/services-support/downloads Phone: (US Toll-Free) 866-763-1813 Phone: (International) 602-852-3094	About Stratus U.S. Operations 111 Powdermill Road Maynard, MA 01754-3409 978-461-7000 Worldwide Office Locations
Product Documentation (PDF Format) Stratus Cloud Solution Administrator's Guide Stratus Cloud Solution Installation Guide	About Help Help created at 12:06 PM on 5/8/2015.