Whenever your organization is going through a business initiative, planned or unplanned, IT is required to deliver the necessary resources to guarantee both performance and success.
The goal is keeping up with the pace of business needs, while providing the agility to position technology as the competitive advantage it was promised to be. The harsh reality is, it’s getting harder to do as our environments explode in both size, and complexity. The short of it is, it’s not going to get any easier.
Overcoming the challenges associated with planned and unplanned work, and executing on both, in a performant and efficient manner is the secret sauce to being a first class IT organization. For this reason, Turbonomic provides the Reserve/Deploy workflow, that ties in seamlessly with your business’s current change management, and transforms the way your business delivers digital advancements.
Traditional Methods to Reserve and Deploy Workflows
Before we talk about Turbonomic, let’s remind ourselves how workloads are being reserved and deployed today. Traditional means of planning for future capacity needs, immediate or not, look and feel much different: Data is collected by batch processes, is then exported or downloaded, simulations/analytics are run, Change Management is completed, submitted, approved (and) finally, workloads are deployed.
Challenges with Traditional Methods
The problem with how we manage for planned and unplanned work today is that we deploy based on last week’s (or last month’s) environment state. We fail to account for how growth and fluctuations in workload demand impact changes (planned or unplanned).
Looking at this problem from a broader context, our CTO has listed the main problems with how planning is traditionally performed:
- Using algorithms that have no understanding of real-time application performance.
- Using only historical data with no regards to environment changes.
- Executing analytics in batch, which prevents them from taking into consideration changes in workload demand.
- Recommendations are bad because the data they used to bake the plan is usually stale.
This makes it very difficult, if not impossible to scale in a performant fashion; certainly not and efficient one.
What Turbonomic Does?
Reserve Capacity for all deployments; now, or at a future date.
- Reserve Capacity (Planned/Unplanned):
- Turbonomic’s real-time engine will account for capacity (planned or unplanned) and place or size workloads based on real-time application demand.
- Turbonomic’s real-time engine will not account for the capacity until the specified date.
- A reservation remains active until its deployed, cancelled, or deployment date has passed.
- If capacity is not available, end-user will be notified to increase capacity to maintain QoS (capacity constraint accounts for SLA’s such as: HA and FT).
How we do it?
Turbonomic solves this problem by not looking at capacity planning as a snapshot in time - a one-time static occurrence - but a practice of continuous capacity management.
The challenge is not collecting data; the challenge is doing something meaningful with it! What reservation/deployment does, is understand how real-time changes in application demand (spinning/scaling up down or out workloads) impact the other entities within the virtual/cloud environment; autonomically aligning real-time application demand, infrastructure supply and future resource requirements, planned or unplanned.