SCNET · Enterprise IT · Ankara, Türkiye

Sanal Çekirdek

Consolidation without knowing capacity is guesswork.

The virtualization layer changes most often and costs most in licensing. Sanal Çekirdek designs it with capacity data, licensing model and refresh schedule considered together.

Consolidation done without measurement produces bottlenecks rather than savings. Measurement comes before the decision.

Capacity measurement and consolidation

A consolidation ratio is the result of measurement, not a target. CPU, memory, disk latency and network use are collected as time series; the gap between peak and average sets the overcommit limit.

  • Measurement covers at least one full business cycle
  • Peaks are reported separately from averages
  • Memory runs out before CPU in most estates
  • Disk latency sets the practical consolidation ceiling

How licensing shapes architecture

Virtualization decisions change licensing cost directly. For software licensed per core, cluster design, placement rules and node size determine the bill. Design the architecture first and the licensing second, and the invoice becomes a surprise.

  • Placement rules keep licensing boundaries intact
  • Node size is chosen together with core counting
  • Audit readiness is maintained continuously
  • Refresh is aligned with the contract term

High availability and maintenance

A cluster must absorb the loss of a node without business impact. Redundancy headroom, maintenance windows and live migration capability are planned together, and the patch calendar is built against that headroom.

  • Headroom is calculated against the busiest hour
  • The patch calendar is tied to cluster capacity
  • Live migration separates maintenance from downtime
  • The storage path carries no single point of failure

Refresh and exit planning

Hardware and platform versions do not age on the same calendar. The refresh plan considers end-of-support dates alongside budget periods, and the cost of exit is known up front in case the platform changes.

  • End-of-support dates tracked on one calendar
  • Refresh waves aligned to budget periods
  • Exit cost measured alongside the cost of staying
  • Data portability treated as a design criterion

How we work

  1. Collect capacity and utilization data
  2. Set the consolidation limit by measurement
  3. Reconcile cluster and placement rules with licensing
  4. Tie maintenance and patching to capacity
  5. Align the refresh plan with budget periods

How success is measured

  • The consolidation ratio rests on measurement
  • Losing one node produces no business impact
  • Licensing coverage matches the actual estate
  • No out-of-support platform version remains

Frequently asked questions

Should we use containers instead of virtualization?

They are different layers, not competitors. Containers may suit newly built services; most existing enterprise applications stay on virtual machines. The call is made per application.

Is overcommit safe?

Within a measured limit, yes. What is dangerous is committing against averages without knowing peaks; on the memory side that limit arrives far earlier than on CPU.

How hard is changing platform?

The difficulty is usually dependency, not technology: if backup, monitoring and automation tooling is tied to the platform, that is where migration cost grows. This is why we measure exit cost early.

Send us your capacity data and we will establish the consolidation limit together, measured rather than assumed.

Request a capacity analysis