Proxmox VE Containers and Cluster Lab

IP Addressing

You will be assigning static IPs to your systems in this lab. Please use these settings:

• Subnet Mask: 255.255.255.0
• Default Gateway: 172.17.xx.1
• DNS Server 172.17.139.11

System	IP
Pod 1 VM A	172.17.xx.xx
Pod 1 VM B	172.17.xx.xx
Pod 2 VM A	172.17.xx.xx
Pod 2 VM B	172.17.xx.xx
Pod 3 VM A	172.17.xx.xx
Pod 3 VM B	172.17.xx.xx

System	IP
Pod 4 VM A	172.17.xx.xx
Pod 4 VM B	172.17.xx.xx
Pod 5 VM A	172.17.xx.xx
Pod 5 VM B	172.17.xx.xx
Pod 6 VM A	172.17.xx.xx
Pod 6 VM B	172.17.xx.xx

System	IP
Pod 7 VM A	172.17.xx.xx
Pod 7 VM B	172.17.xx.xx
Pod 8 VM A	172.17.xx.xx
Pod 8 VM B	172.17.xx.xx
Pod 9 VM A	172.17.xx.xx
Pod 9 VM B	172.17.xx.xx

Instructions

1. VMs are located on the https://netlab-ihcc.campus.ihitc.net server system, be sure you are connected to the ITCnet VPN before attempting to access this system
   • NOTE: Make sure you are working on the VMs in the ITC-2300 resource group and not in the Remote Network Pods resource group
2. Boot both your Proxmox VE Server systems
3. Check the available container templates on your PVE server and make sure you have downloaded the latest Debian system templates. Also download at least one of the Turnkey Linux appliance templates such as the Wordpress template.
   • NOTE: If you have an incomplete list of container templates it's likely the case that your system was powered off when the auto-run script went to check the list of available templates. You can refresh this list manually from the PVE command line using information from the ProxMox Linux Containers page.
4. After you have the containers downloaded go ahead and deploy a container based on the Debian template, use DHCP addressing.
5. Try using the Debian container to see if it feels any different than a regular Debian VM.
6. Create a Proxmox cluster for your pod named "PodX" where X is replaced with your pod number. Do this on the Proxmox node containing your VMs, nodes to be added will not be able to have VMs until after they are added.
7. Add your Proxmox server B to your Proxmox cluster.
8. Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working
9. Deploy a Wordpress server container to a node in your Proxmox cluster, verify it is working
10. Try migrating one of your VMs from the last lab which is NOT powered on from one node to another node in the cluster and then powering up and verifying the VM still works
11. Try migrating one of your Linux containers from one node to another node in the cluster. Note that containers will be powered off while being moved and will then be restarted once the move is complete.
12. Setup some kind of remote access to one of your VMs. That could be Remote Desktop to a Windows VM or SSH to a Linux VM.
13. Open a connection directly to the VM with remote access
14. Try migrating another the VM with remote access open (while it is powered on) from one node to another node in the cluster. Make sure you can maintain connectivity and work on the VM the entire time the VM is being migrated.
    • Note that you will need to remove any CD images from the system before it can be migrated.
15. Try modifying an existing VM by adding extra storage, in the form of an additional virtual disk and ensure you can see and use the space inside your VM
16. Try modifying an existing container by adding extra storage, in the form of an additional mount point and ensure you can see and use the space inside your container
17. Try cloning one of your VMs
18. Safely shut down all your containers and VMs
19. Safely shutdown your Proxmox VE servers