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 configuration options for a KVM 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 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
Service Group Management in Virtual Business Services
Service group management improves business resiliency by providing a method to bundle hardware, software, applications, databases and networks into a single entity with dependencies. By monitoring the health and performance of these service groups, through proactive notification, pending issues can be quickly addressed. InfoScale Operations Manager reports on the relationship of applications to virtual machines, physical servers and clusters and provides coordinated failover of services that span virtual machines and physical machines for multi-tier applications. In the past, customers who wanted this functionality had to build scripts to automate these procedures but this method was complex to manage and test.
To help customers address these issues, Arctera introduced Virtual Business Services (VBS). Virtual Business Services combines the power of VCS and InfoScale Operations Manager to provide complete multi-tier business service management and High Availability. VBS now enables management of multi-tier business services on top of InfoScale Operations Manager and VCS which allows InfoScale Operations Manager to be used as a single tool for availability management.
Virtual Business Services achieves the following:
Co-ordinates the start and stop across different operating systems and/or platforms
Provides fault management and propagation between tiers
Manages multi-tier Disaster Recovery support
Enables automated Disaster Recovery of a complete Virtual Business Service and Virtual Machine management support (start and stop)
High Availability is primarily managed within each tier. The cluster is responsible to keep services highly available within the cluster. The boundaries for an application are the cluste instance. Logically, a VBS can be seen as a container that allows service groups to be built into a single object. To enable VBS, Red Hat Enterprise Virtualization Environments must have VCS installed on the physical server. For the other operating environments within the VBS, it is required that each tier has VCS, Microsoft Cluster Server installed.
In order to deploy VBS, there must be at least one InfoScale Operations Manager Central Server installed in the data center. The InfoScale Operations Manager Central Server is used for configuration, visualization and management of VBS. However, after the initial configuration of a VBS, it can be managed using a CLI as well. VBS functionality does not depend on InfoScale Operations Manager Central Server. CLI operations work regardless of whether the InfoScale Operations Manager Central Server is available or not, and the member nodes of a VBS will operate autonomously of the InfoScale Operations Manager Central Server once VBS is deployed.
Application DR can be between VMs or from a Virtual to Physical DR and vice versa. During the failover of Virtual Machine there is an automatic update of VM (IP, DNS, netmask) to ensure user access to the new instance.
An example of how DR operates across a multi-tier environment:
InfoScale Operations Manager also includes the ability to associate different Virtual Business Services into a Disaster Recovery Plan. This feature enables another level of automation because it allows the customer to combine service groups, Virtual Business Groups and manual scripts into a single procedure. It provides the sequence of operations that will be performed at the DR site, in the event of a disaster. The GUI allows you to choose items to include into the plan and provides single click failover of an entire data center to a secondary site.