vOPS Server Standard 6 extends control into cloud deployments
VKernel announced vOPS Server Standard 6.0. This release extends control into cloud environments and virtual machine (VM) performance with unified multi-data source VM issue diagnosis, change impact modeling and VMware vCloud Director integration.
Unlike physical servers, where applications are mapped to unique hardware such as physical network connections, virtual infrastructures can’t be seen or touched by an administrator. This lack of physical attachment provides tremendous benefit but also adds dramatic complexity from:
- Resource contention issues
- Extreme mobility of virtual machines and connected storage
- Cloud deployment models that increase change volume with additional automation.
The end result is a highly complex and dynamic system of interlocking parts, many of which cannot be assessed without processing data through advanced analytics.
Because change is constantly occurring within virtualized infrastructures, issues often develop unexpectedly. Worse, a problem in one object can affect many others as resources are shared. System administrators must typically engage in “fire-fighting” multiple issues before determining the root cause of a problem.
The only way to ensure performance and fiscally sound business operations, and ultimately provide sanity to the system administrator, is to deliver a solution that can control the virtual environment.
vOPS provides control for cloud deployments and VM performance through analytics, advice and automation. The 6.0 release of vOPS Server Standard enhances these capabilities with:
- Unified multi-data source VM issue diagnosis
- Change impact modeling
- vCloud Director integration.
Because VMs share IT resources, any change can adversely impact performance issues in other areas of the virtual environment. Assessing changes manually is difficult due to the sheer volume of data that must be processed. Yet, environment changes are a leading cause of unexpected VM performance issues that cause system administrators to go into “fire-fighting” mode.
To remove this source of “fire-fighting,” vOPS Server Standard 6.0 introduces change impact modeling. Changes can be modeled in a “dress rehearsal” before executing them. vOPS’ analytics determine if issues will occur as a result of a change, and changes can then be automatically implemented.