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
- About InfoScale deployments in OpenShift Virtualization environments
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- InfoScale configuration options for a KVM 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 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
Virtual-to-physical clustering and failover
You can also create a virtual-to-physical cluster by combining VCS within a guest VM together with VCS running on any other physical host. This virtual-to-physical cluster enables VCS to monitor applications running within the guest and to fail them over to another host when necessary. It also enables an application running on a physical host to be failed over a guest.
A VCS cluster is formed among the guests and physical hosts. VCS is installed on the guests and on different physical hosts in the cluster. Guests are connected to physical hosts through the network of their VM hosts. In this case, a VM host is a physical host on which one or more guests that form the cluster are hosted.
This VCS cluster manages and monitors the services and applications running on cluster nodes that can either be guests or physical hosts. Any faulted application on one node fails over to another node, which can either be a VM or a physical host.
See Standard bridge configuration.
For such virtual-to-physical or physical-to-virtual clustering, the following I/O fencing configurations are supported:
SCSI-3 with underlying iSCSI devices
Non-SCSI-3
Coordination point server (CP server)