InfoScale™ 9.0 Virtualization Guide - Linux
- Section I. Overview of InfoScale solutions used in Linux virtualization
- Overview of supported products and technologies
- Overview of the InfoScale Virtualization Guide
- About InfoScale support for Linux virtualization environments
- About KVM technology
- About InfoScale deployments in OpenShift Virtualization environments
- About InfoScale deployments in OpenStack environments
- Virtualization use cases addressed by InfoScale
- About virtual-to-virtual (in-guest) clustering and failover
- Overview of supported products and technologies
- Section II. Implementing a basic KVM environment
- Getting started with basic KVM
- Creating and launching a kernel-based virtual machine (KVM) host
- RHEL-based KVM installation and usage
- Setting up a kernel-based virtual machine (KVM) guest
- About setting up KVM with InfoScale solutions
- InfoScale solutions configuration options for the kernel-based virtual machines environment
- Dynamic Multi-Pathing in the KVM guest virtualized machine
- DMP in the KVM host
- SF in the virtualized guest machine
- Enabling I/O fencing in KVM guests
- SFCFSHA in the KVM host
- DMP in the KVM host and guest virtual machine
- DMP in the KVM host and SFHA in the KVM guest virtual machine
- VCS in the KVM host
- VCS in the guest
- VCS in a cluster across virtual machine guests and physical machines
- Installing InfoScale in 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
- About application availability options
- Cluster Server in a KVM environment architecture summary
- Virtual to Virtual clustering and failover
- I/O fencing support for virtual-to-virtual clustering
- Virtual to Physical clustering and failover
- Recommendations for improved resiliency of InfoScale clusters in virtualized environments
- 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 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
- Limitations while managing Docker containers
- Section V. Reference
- Appendix A. Troubleshooting
- InfoScale logs for CFS configurations in OpenStack environments
- Troubleshooting virtual machine live migration
- The KVMGuest resource may remain in the online state even if storage connectivity to the host is lost
- VCS initiates a virtual machine failover if a host on which a virtual machine is running loses network connectivity
- Appendix B. Sample configurations
- Appendix C. Where to find more information
- Appendix A. Troubleshooting
Installing and configuring Cluster Server with Microsoft Hyper-V virtual-to-virtual clustering
The Microsoft Hyper-V role is a hypervisor-based server virtualization technology for the x86_64 architecture. It provides you with the software infrastructure and management tools that you can use to create and manage a virtualized server computing environment.
To enable VCS support for in-guest clustering, before you install VCS on the guest virtual machines, you must set up a private network between them, which involves the following steps:
Add two NICs to the virtual machine for private communication.
Note:
Arctera recommends that you add one more interface/NIC to the virtual machine for public communication. Also, if the virtual machines for which you are configuring the network run on separate physical hosts, ensure that you set up an LLT communication channel between the physical hosts.
Attach a switch to each of the two additional NICs.
To create a virtual network on the physical host
- From the Hyper-V manager, create two virtual networks for private LLT heartbeat communication.
- Assign appropriate physical interfaces to the newly-created virtual networks.
To configure the network for the virtual machines
- Create two network interfaces of 'Legacy Network Adaptor' type, and associate them with the newly-created virtual networks.
- Repeat step 1 for each virtual machine where you want to monitor application availability with VCS.
To set up a cluster of virtual (guest) machines with Cluster Server (VCS), perform the following procedures:
Consult the requirements listed in the InfoScale Release Notes.
Install VCS on the guest virtual machine as described in the InfoScale Installation Guide.
Configure VCS in the guest virtual machine as described in the Cluster Server Configuration and Upgrade Guide.
Note:
You can install and configure VCS on a virtual machine the same way that you do on a physical system. No additional steps are required to make it work on a virtual machine.
For details, refer to the Cluster Server Administrator's Guide.
VCS supports non-SCSI3, CP server-based fencing in virtual machines to prevent corruption of data disks. SCSI3 fencing is not supported.
For information on configuring fencing, refer to the InfoScale Installation Guide.
VCS in-guest clustering continues to provide high availability of applications on virtual machines, in live migration scenarios initiated by the virtualization technology.
Arctera performs tests for live migration support in the Hyper-V environment under the following conditions:
Microsoft Failover Clustering is enabled
Virtual machine image resides on Microsoft Clustered Shared Volumes