ManageIQ announced EVM Version 5 (V5), providing unified cloud management that enables IT services to be easily provisioned and managed across physical, virtual, private and public cloud infrastructures, including Amazon and Rackspace.
This new release builds on ManageIQ’s deep technical expertise and success helping enterprise IT organizations, including a growing number of Fortune 1000 customers, adopt and manage virtualized private clouds.
By extending EVM management capabilities, including provisioning, resource management, monitoring, governance and compliance to public cloud platforms, ManageIQ provides an enterprise-grade, single platform to manage the migration and successful adoption of hybrid cloud computing.
“ManageIQ has been helping enterprise IT organizations successfully adopt cloud computing through a transformational approach that typically starts with moving from virtualization to private clouds,” said Joseph Fitzgerald, ManageIQ Chief Product Officer. “We see our customers evolving their cloud strategies to include public clouds, so we have extended EVM to manage both private and public clouds in an integrated, hybrid fashion – addressing the needs of cloud management in the enterprise.”
Effective delivery and management of IT services across hybrid clouds requires real-time management and automation capabilities that are “unified by design” – not loosely coupled, point-tool integrations that leave visibility, governance and automation gaps. ManageIQ addresses these requirements architecturally, through an Adaptive Management Platform that enables continuous closed-loop management, tightly coupling provisioning together with configuration, resource and workload automation.
Its industry-leading EVM Suite now supports hybrid cloud infrastructures with unified monitoring, management and automation, giving IT organizations operational visibility and control through a single pane of glass. EVM delivers user self-service provisioning and management uniformly and transparently across hypervisors and cloud providers, enabling optimal service delivery based on business policies, service levels and cost.
EVM V5’s unified self-service provisioning, monitoring, metering/chargeback, adaptive automation and policy-based orchestration with role-based executive, operational and user dashboards has been extended beyond physical and virtual infrastructures to public and hybrid clouds, including:
- Public cloud support for Amazon (AWS and CloudWatch).
- OpenStack support for both public cloud providers such as Rackspace, and for private clouds, as well as VMware vCloud support delivered in 4Q2012.
- Support for a broad range of IT services from simple, single systems to complex n-tier systems delivered from a self-service portal as well as through other enterprise service catalogs and portals.
- Powerful service orchestration capabilities for requesting, configuring and managing services, as well as holistic visibility and policy-based control over services including power operations, flexing and monitoring.
EVM V5’s out-of-the-box integration with other enterprise management systems maximizes operational efficiencies and leverages existing IT investments across hybrid clouds, including:
- Service automation for provisioning, flexing and decommissioning, driven via change management systems and enterprise service catalogs, as well as IT Process and orchestration tools.
- Service monitoring with policy-based incident and alert creation, containing comprehensive contextual information to reduce mean-time-to-repair.
- Real time discovery and monitoring capabilities that ensure CMDBs are kept accurate and up-to-date.
- Usage and metering information can be federated into financial management systems for billing and chargeback.
- Supported integrations include ServiceNow, CA, Microsoft Systems Center, BMC, HP, F5 and NetApp, as well as RESTful and SOAP-based management web-services.
EVM V5 will be generally available September 30, 2012.
The Latest
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.
The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...