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
Migrating Docker Daemons and Docker Containers
InfoScale Enterprise also addresses the use case related to migrating both the infrastructure and container data. In this scenario, you need to bring down the Docker Daemon and Docker Container on the primary node and bring them up on the secondary node.
While migrating containers, ensure that you stop the Docker Daemon and Docker Container on the primary node before you migrate them to the secondary node.
To configure the Docker Daemon and containers using SFCFS
- Create a shared disk group and volume and do mkfs.
# vxdg -s init dockdg disk1 disk2 disk3
# vxassist -g dockdg make vol7 10G
# mkfs -t vxfs /dev/vx/dsk/dockdg/vol7
- Mount the volume on each cluster node.
# mount -t vxfs -o cluster /dev/vx/dsk/dockdg/vol7 /docvol
Where docvol is the directory used by the Docker Daemon for Docker infrastructure.
- Configure Docker to start the Docker Daemon on newly created CFS mount point,
/docvol.Note:
Docker stores all its data, metadata, containers on alloted CFS shares. Though this CFS share is visible on all cluster nodes, Docker Daemon should be started from only one node a time.
- To initialize the migration make sure Docker Daemon is stopped from the source node and CFS share is not being consumed by Docker Daemon.
# systemctl stop docker
- Start the Docker Daemon on target node by appending -g /docvol in the
OPTIONSfield in the/etc/sysconfig/dockerconfiguration file..# systemctl start docker
The Docker Daemon is initialized on the target node. After migration is complete, Docker containers will be in exited state. User may need to manually start the containers.
Note:
To configure Docker Containers with VCS, refer to the Cluster Server Agent for Docker Installation and Configuration Guide guide.