Chapter 02 / Lifecycle

Six states. One direction of gravity.

Every workload lives in exactly one lifecycle state. The state determines whether you pay on-demand, lock in a 3-year commitment, or get put on the auto-shutdown queue. Transitions are restricted: a workload can never go backwards from decommissioning.

Figure 2.1 - The complete UFMS lifecycle transition graph. Twelve allowed edges across six nodes.

What each state means.

newstate 01 / 06

New

Age0-30 daysPricingOn-demand only

0-30 days since creation. Right-sizing not expected. On-demand pricing.

rampingstate 02 / 06

Ramping

Age30-90 daysPricingNo CUDs yet

30-90 days. Traffic still fluctuating. CUDs not yet justified.

existingstate 03 / 06

Existing

Age90+ days, stablePricingEligible for CUDs

90+ days, stable. Should be on commitment-based pricing if applicable. Right-size monthly.

optimizingstate 04 / 06

Optimizing

AgeActive review windowPricingLook-back snapshots

Active rightsizing or commitment review window. Look-back snapshots required.

migratedstate 05 / 06

Migrated

Age+30d to deletePricingFrozen, parallel-run

Workload moved to a different platform. Source still exists for cutover safety. Decommission target = +30 days.

decommissioningstate 06 / 06

Decommissioning

AgeASAP deletePricingBlock new commits

Marked for shutdown. Block new commitments. Prevent scale-up. ASAP delete window.

Allowed transitions, in detail

From / To matrix.

From / To	new	ramping	existing	optimizing	migrated	decommissioning
new	-	allowed				allowed
ramping		-	allowed	allowed		allowed
existing			-	allowed	allowed	allowed
optimizing			allowed	-	allowed	allowed
migrated					-	allowed
decommissioning						-

IFO4