Use case · Multi-site enterprise
Changing hypervisor without knowing what runs on it
Five sites, several thousand virtual machines on VMware, a ServiceNow CMDB fed by discovery and by forms, siloed network, infrastructure and security teams. The VMware contract expires in eighteen months; Hyper-V and Nutanix are under review.
- VMware
- HHyper-V (via export)
- Nutanix
- ServiceNow
Figures measured in a demonstration
-
Flows checked against the rules
Under 1 second
to check 602 flows against the firewall rules, on a fictional estate of about 200 virtual machines.
For you: you know which rules the new hypervisor must carry over before a single machine moves.
-
Impact of one application stopping
5 business capabilities
affected when one application stops, each with the path of the dependency.
For you: each migration wave is planned knowing what it puts at stake for the business.
The situation before the VMware migration
The head of infrastructure must choose the hypervisor that will replace VMware and plan the move. Every option is priced on an inventory: number of machines, dependencies, flows, versions. But the CMDB and VMware do not give the same answer, and no flow can be followed end to end from one site to another. The committee expects a deliverable, not raw data. And the deployment has to stay within the group's perimeter.
What gets in the way
- A CMDB that is out of date, and therefore unreliable
- Five sites organised by several teams, each in its own way
- Outage impact discovered on the day of the outage
- An inventory for the move to produce without spending a quarter on it
What one hour of Uncia brings
A read-only account on each site's vCenter, the ServiceNow CMDB and the core firewalls; flow matrices to complete them.
- All five sites organised the same way, on the same map
- The gaps between ServiceNow and VMware, machine by machine, both values kept
- Outage impact: which applications and flows go down for each candidate machine
- End-of-support per machine and per site, to decide what to move and what to replace
- Flows between sites judged against the rules, point by point
- If this application stops 5 business capabilities affected, each with its path
- The path of every dependency from application to business capability, link by link
- 3 business flows affected collect, inform the policyholder, issue a contract
What changes
Hyper-V and Nutanix are compared on an inventory where every machine carries its source, its dependencies and its end-of-support date, instead of a CMDB that would first need cleaning. The order of the move is decided on the real impact of an outage. Network, security and infrastructure teams read the same map. And the CMDB stays in place: its gaps are shown, and it is up to the CMDB owners to fix them.
-
For the head of infrastructure
A target hypervisor priced on facts, and an order of the move built on solid ground.
-
For the CISO
An inventory of unjustified flows and out-of-support machines, before anything is moved.
-
For leadership
A multi-million-euro decision, taken with all the information it needs.
See your estate in Uncia in 30 minutes
Come with one site's vCenter export and the CMDB extract that describes it: we show you their gaps during the demo.
The features involved
- Feature
Run: impact, questions, reports
See the feature - Feature
Connectors and sources
See the feature - Feature
IT mapping, across every layer
See the feature