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
Installing and configuring Cluster Server for Oracle Virtual Machine (OVM) virtual-to-virtual clustering
Oracle VM is an enterprise-grade server virtualization solution that supports guest (virtual machines) that supports various operating systems, including Linux. Based on the Xen hypervisor technology, OVM also provides you with an integrated, Web-based management console.
Before you install VCS on the guest virtual machines, you must set up a private network between them. This involves the following steps:
To enable VCS support of virtual-to-virtual clustering
- Set up a private network between the guest virtual machines.
Apart from the public NIC on each physical host, create two additional NICs.
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.
If the virtual machines for which you configure the network run on separate physical hosts, ensure that you create a LLT communication channel between the physical hosts.
Attach a switch to each of the two additional NICs
To create a private network on the physical host
- From the Oracle VM 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 virtual machines
- Create two interfaces (in a network that is created with the option Create a hybrid network with bonds/ports and VLANS) and associate the interfaces with the newly-created virtual networks.
- Repeat step 1 for each virtual machine where you want to monitor 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 InfoScale Availability on the guest virtual machine as described in the InfoScale Installation Guide.
Configure VCS on 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.
Fordetails, refer to the Cluster Server Administrator's Guide.
Arctera supports live migration in the OVM environment only when the virtual machine image resides in NFS data domains.
VCS supports non-SCSI3, CP server-based fencing in virtual machines to prevent corruption of data disks.
For information on configuring fencing, refer to the Cluster Server Configuration and Upgrade Guide.