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
About installing and configuring the OpenStack environment
Use RHOSP director to install and create your OpenStack environment. Then, use the undercloud to install and configure the overcloud.
When you configure the undercloud node, make sure to use at least of three 1 Gbps NICs, one for each of the following:
External network
Provisioning or control plane network
Data plane network
The overcloud consists of multiple controller and compute nodes.
Make sure to use at least two NICs, one for each of the following:
Control plane network
Data plane network
After the OpenStack deployment is successful, create the following resources:
Basic overcloud flavors
Private network for guest VMs
External network for floating IPs for guest VMs
Security key pairs for accessing guest VMs
Security group
VM instances
Cinder volumes
When attaching block storage to VMs, OpenStack uses the virtio-blk
driver by default. The storage appears as a virtio-blk
device on a controller node and as a virtio
disk (/dev/vda
, /dev/vdb
) on a compute node.
See UDID mismatch in a CFS cluster in an OpenStack environment.