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
Creating Docker containers with storage attached automatically
In the following procedure, demovol is the name of the volume being created.
To create docker containers with storage attached automatically
- Create a volume using the docker volume create command.
# docker volume create -d veritas --name demovol
- Alternatively, you can also specify size and or layout options using
-ooption.# docker volume create -d veritas --name demovol -o size=1g -o layout=mirror
Note:
If options are not provided while creating a volume, then it uses default values for size and layout that are stored in the
/etc/vx/docker/vxinfoscale-default.conffile. If layout=auto is mentioned, then InfoScale automatically chooses the best layout for the environment. - You can verify whether the volume is created properly by running the a docker volume ls command.
# docker volume ls
DRIVER VOLUME NAME veritas demovol
- You can verify the detail information of the volume using docker volume inspect command.
# docker volume inspect demovol
[ { "Name": "demovol", "Driver": "veritas", "Mountpoint": "/dockerfs/demovol_dockerdg", "Labels": {}, "Scope": "global" } ] - Launch docker container.
# docker run --name <container_name> -it --volume-driver veritas -v demovol:/vol<docker_image> <command>
Where, VxVM volume 'demovol' gets automatically attached to the docker container.
- You may verify that the container is running and accessible.
# docker ps <container_name>
- You can also remove the volume if it is not needed anymore.
# docker volume rm demovol