Artifact Library #

Introduction #

To execute a simulation and generate a scenario result, you will need to define a target environment, its current resource state, and your assumptions about what factors influence how pool resources might evolve over time. Zypr refers to a target environment as a pool, which represents a collection of servers that host workloads that require similar features.

Zypr's Pool Resources Model is expressed in JSON and is used to describe your pool in a standardized manner that can be input into Zypr's simulation engine. A model defines the initial resource state of a pool, attributes that may be described using continuous variables (e.g., a service demand growth rate), and events that typically require several variables to describe how the event is triggered, when, and for what effect. Rates of hardware utilization are subject to boundary conditions, and constraints may be defined to restrict permissible resources levels, such as core quantity or power consumption. The output of a simulation is a forecast of hardware, software, power and space consumption, inventory balances and turnover.

Zypr refers to events as "jump events" and forecasting future states of a pool involves identifying relevant jump events - from price changes to hardware configuration changes. Zypr simulates the dynamic flow of these state changes over time that results in a far high degree of precision than spreadsheet-based models. And depending upon your selections, Zypr can also identify the series of state changes that produce the lowest total resource cost for a pool.

The artifact library contains pre-defined pool models to assist you in defining models that best meet your particular forecasting needs. The library catalog below is organized by common use-cases. To avoid repetition, only key objects of the pool resources model are identified. You can retrieve the corresponding complete model using the artifact library.

Pool Models by Use Case #

Increase pool average utilization rate #

Overview

Sustainably increasing hardware utilization can provide significant financial savings when it produces commensurate reductions in software, space and power consumption. The foundational drivers to accomplish this are:

1. Improving workload assignment and scheduling
2. Reducing lead-time

Model Id: 10 #

Title: Inc #

Description: #

Complexity: #

Key Concepts: #

Summary: EvolutionSettings and JumpEvent Type UtilizationBoundaries #

This EvolutionRules object defines the boundary conditions and rules for how pool server inventory is permitted to evolve.

  "EvolutionRules" : {
    {
        "PoolUtilizationPercentCurrent": "55.0",
        "PoolUtilizationBoundaryPercentLower": "50.0",
        "PoolUtilizationBoundaryPercentUpper": "60.0",
        "ServiceDemandGrowthPercent": "20"
        } 
    }
  }
  
  "JumpEvents": {
    {
        "EventType":"UtilizationBoundaries",
        "EventId":"1",
        "TriggerTime":"1.00",
        "PoolUtilizationBoundaryPercentLower": "63.5",
        "PoolUtilizationBoundaryPercentUpper": "65.5",
    }
  }