InfoScale™ 9.0 Virtualization Guide - Linux
- Section I. Overview of InfoScale solutions used in Linux virtualization
- Overview of supported products and technologies
- About InfoScale support for Linux virtualization environments
- About KVM technology
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- InfoScale solutions configuration options for the kernel-based virtual machines environment
- Installing and configuring VCS in a kernel-based virtual machine (KVM) environment
- Configuring KVM resources
- Getting started with basic KVM
- Section III. Implementing InfoScale an OpenStack environment
- Section IV. Implementing Linux virtualization use cases
- Application visibility and device discovery
- Server consolidation
- Physical to virtual migration
- Simplified management
- Application availability using Cluster Server
- Virtual machine availability
- Virtual machine availability for live migration
- Virtual to virtual clustering in a Hyper-V environment
- Virtual to virtual clustering in an OVM environment
- Multi-tier business service support
- Managing Docker containers with InfoScale Enterprise
- About the Cluster Server agents for Docker, Docker Daemon, and Docker Container
- Managing storage capacity for Docker containers
- Offline migration of Docker containers
- Disaster recovery of volumes and file systems in Docker environments
- Section V. Reference
- Appendix A. Troubleshooting
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
About virtual-to-virtual (in-guest) clustering and failover
When you run Cluster Server (VCS) in multiple guest virtual machines, you can create guest-to-guest (also called virtual-to-virtual) clusters. You can use VCS to monitor individual applications running inside each guest. In case of application failure, VCS can fail over the application to another guest virtual machine in the virtual-to-virtual cluster.
The following figure illustrates a sample in-guest VCS deployment in one virtual machine each across two physical hosts.
The virtual machines in the cluster can either be on the same physical host or on different physical hosts. VCS is installed in the virtual machines and creates a cluster. This is just like the cluster that VCS creates among physical systems. The cluster monitors the applications and services that run inside the virtual machines. Any faulted application or service is failed over to another virtual machine in the cluster.
To ensure application failover, application data must reside on storage shared by member virtual machines within the cluster.
Note:
In this configuration, since VCS runs inside a virtual machine, VCS cannot fail over the virtual machine itself.
VCS can be deployed inside guest virtual machines (in-guest support) in the following virtualization environments:
Microsoft Hyper-V
Red Hat OpenShift Virtualization (OpenShift)
Red Hat OpenStack Platform (RHOSP)
Oracle Virtual Machine (Oracle VM)
Kernel-based Virtual Machine (KVM) technology for Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES)
Linux guests in VMware ESXi environments