Deploying captured or imported images
You can deploy images that are created when you capture a virtual machine or import a volume-backed image. The deploy target can be a specific host or a host group.
- Select the image in the graphical user interface and select Deploy.
- Specify the properties of the new virtual
machine as needed. You can use PowerVC resources, such as a storage template, compute template, and storage connectivity group to specify custom settings.
- Add existing volumes or new (blank) volumes in any order,
or remove the volumes as needed. Notes:
- The IP address information for imported networks is unknown and therefore they are created as DHCP networks. You can edit the network in the Network Panel to provide the static details to match the real configuration of your network.
- If you are using a static network to deploy, you can either deploy with an IP address from the IP address pool or manually assign an IP address to the virtual machine. When you use the IP address pool, only the addresses that are available and are not locked can be assigned to the virtual machine. Ensure that you review and lock the IP address that you do not want assigned before you deploy a virtual machine.
- PowerVC supports up to 32 network interfaces on the virtual machines. However, when paired with NovaLink, one of those is reserved for the RMC NIC. There must be one network added to PowerVC for each network interface that you specify.
- The volumes that are part of the image cannot be removed from the list.
- If you want to deploy multiple instances of an image then any new and existing volumes that you add during the deploy must be multi-attach enabled by selecting Enable sharing.
- For NovaLink, you can deploy an image that has at most 25 volumes. Additionally, you can capture at most 25 volumes when you capture a virtual machine.
- Click Deploy.
If you want to remove a network interface on the virtual machine that you deployed, you must enable the persistence rules on the virtual machine. To enable the persistence rules, restore 75-persistent-net-generator.rules then restart the virtual machine to get the 70-persistent-net.rules regenerated.
- Restart the virtual machine to detect attached volumes.
- Follow the instructions in the Scanning Storage Interconnects topic to configure the Red Hat Enterprise Linux 7 operating system to detect the attached storage volumes automatically on the deployed virtual machine.