Proxmox VE Containers and Cluster Lab - Revision history

BenFranske at 15:36, 24 September 2021

2021-09-24T15:36:03Z

← Older revision		Revision as of 15:36, 24 September 2021
Line 31:		Line 31:
	# 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.		# 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.
	# 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.		# 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.
	# ~~Open~~ a connection directly to the VM with remote access		# Use PC-C to open a connection directly to the VM with remote access (SSH to Linux or Remote Desktop to Windows)
	# 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.		# Try migrating the VM with a remote access connection 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.		#* Note that you will need to remove any CD images from the system before it can be migrated.
	# 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		# 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

BenFranske at 22:27, 15 September 2021

2021-09-15T22:27:07Z

← Older revision		Revision as of 22:27, 15 September 2021
Line 39:		Line 39:
	# Safely shut down all your containers and VMs		# Safely shut down all your containers and VMs
	# Safely shutdown your Proxmox VE servers		# Safely shutdown your Proxmox VE servers
			# End your Netlab Reservation

BenFranske: /* IP Addressing */

2021-09-15T22:19:46Z

IP Addressing

← Older revision		Revision as of 22:19, 15 September 2021
Line 8:		Line 8:
	! System !! IP		! System !! IP
	\|-		\|-
	\| ~~Pod 1~~ HV-A \|\| 192.168.1.10		\| HV-A \|\| 192.168.1.10
	\|-		\|-
	\| ~~Pod 1~~ HV-B \|\| 192.168.1.11		\| HV-B \|\| 192.168.1.11
	\|}		\|}

BenFranske: /* Instructions */

2021-09-15T16:51:18Z

Instructions

← Older revision		Revision as of 16:51, 15 September 2021
Line 15:		Line 15:
	=Instructions=		=Instructions=
	# VMs are located on the https://ihcc-netlab.campus.ihitc.net Netlab system, be sure you are connected to the ITCnet VPN before attempting to access this system		# VMs are located on the https://ihcc-netlab.campus.ihitc.net Netlab system, be sure you are connected to the ITCnet VPN before attempting to access this system
			#* NOTE: You will need to make a reservation for the Proxmox Labs in this class before you are able to access the VMs. Changes will be saved between your reservations so you will be able to make multiple reservations over several days as needed to complete labs.
			#* NOTE: If you need to split your work up across multiple reservations be sure to safely shutdown your Proxmox VMs before ending your Netlab reservation. Otherwise when your reservation ends Netlab will simply power off your VMs (without shutting them down first) which could cause data corruption.
			#* NOTE: If you make a mistake and need to have one or both of your HV VMs erased so you can re-install Proxmox you will need to contact your instructor or the ITC lab assistant to have them reset.
	# Boot both your Proxmox VE Server systems		# Boot both your Proxmox VE Server systems
	# 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.		# 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.
Line 22:		Line 25:
	# Create a Proxmox cluster for your pod named "PodX" where X is replaced with your pod letter. 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.		# Create a Proxmox cluster for your pod named "PodX" where X is replaced with your pod letter. 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.
	# Add your Proxmox server B to your Proxmox cluster.		# Add your Proxmox server B to your Proxmox cluster.
			#* NOTE: If you're having difficulty with this there are two critical requirements that must be met per the documentation and in the instructions from the previous lab: the hostnames of the two Proxmox servers MUST be different AND there can be no VMs on servers being added to a cluster (in this case server B is being added to the cluster). Make sure you have met both requirements.
	# Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working		# Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working
	# Deploy a Wordpress server container to a node in your Proxmox cluster, verify it is working		# Deploy a Wordpress server container to a node in your Proxmox cluster, verify it is working

BenFranske: /* Instructions */

2021-09-15T16:47:10Z

Instructions

← Older revision		Revision as of 16:47, 15 September 2021
Line 14:		Line 14:

	=Instructions=		=Instructions=
	# 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		# VMs are located on the https://ihcc-netlab.campus.ihitc.net Netlab 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~~
	# Boot both your Proxmox VE Server systems		# Boot both your Proxmox VE Server systems
	# 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.		# 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.
Line 21:		Line 20:
	# After you have the containers downloaded go ahead and deploy a container based on the Debian template, use DHCP addressing.		# After you have the containers downloaded go ahead and deploy a container based on the Debian template, use DHCP addressing.
	# Try using the Debian container to see if it feels any different than a regular Debian VM.		# Try using the Debian container to see if it feels any different than a regular Debian VM.
	# 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.		# Create a Proxmox cluster for your pod named "PodX" where X is replaced with your pod letter. 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.
	# Add your Proxmox server B to your Proxmox cluster.		# Add your Proxmox server B to your Proxmox cluster.
	# Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working		# Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working

BenFranske: /* IP Addressing */

2021-09-15T16:45:12Z

IP Addressing

@@ Line 2: / Line 2: @@
 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.51.1
+* Default Gateway: 192.168.1.1
-* DNS Server 172.17.139.11
+* DNS Server 192.168.1.1
 {| class="wikitable" style="display: inline-table;"
 ! System !! IP
 |-
-| Pod 1 hv A || 172.17.51.30
+| Pod 1 HV-A || 192.168.1.10
 |-
-| Pod 1 hv B || 172.17.51.31
+| Pod 1 HV-B || 192.168.1.11
 |}

BenFranske: /* IP Addressing */

2020-09-24T16:42:41Z

IP Addressing

← Older revision		Revision as of 16:42, 24 September 2020
Line 2:		Line 2:
	You will be assigning static IPs to your systems in this lab. Please use these settings:		You will be assigning static IPs to your systems in this lab. Please use these settings:
	* Subnet Mask: 255.255.255.0		* Subnet Mask: 255.255.255.0
	* Default Gateway: 172.17.xx.1		* Default Gateway: 172.17.51.1
	* DNS Server 172.17.139.11		* DNS Server 172.17.139.11

Line 8:		Line 8:
	! System !! IP		! System !! IP
	\|-		\|-
	\| Pod 1 VM A \|\| 172.17.xx.xx		\| Pod 1 hv A \|\| 172.17.51.30
	\|-		\|-
	\| Pod 1 VM B \|\| 172.17.xx.xx		\| Pod 1 hv B \|\| 172.17.51.31
	\|-		\|-
	\| Pod ~~2 VM~~ A \|\| 172.17.xx.xx		\| Pod 1 PC A \|\| 172.17.51.32
	\|-		\|-
	\| Pod 2 ~~VM B~~ \|\| 172.17.xx.xx		\| Pod 2 hv C \|\| 172.17.51.35
	\|-		\|-
	\| Pod ~~3 VM A~~ \|\| 172.17.xx.xx		\| Pod 2 hv D \|\| 172.17.51.36
	\|-		\|-
	\| Pod 3 ~~VM B~~ \|\| 172.17.xx.xx		\| Pod 2 PC B \|\| 172.17.51.37
			\|-
			\| Pod 3 hv E \|\| 172.17.51.40
			\|-
			\| Pod 3 hv F \|\| 172.17.51.41
			\|-
			\| Pod 3 PC C \|\| 172.17.51.42
	\|}		\|}
	{\| class="wikitable" style="display: inline-table;"		{\| class="wikitable" style="display: inline-table;"
	! System !! IP		! System !! IP
	\|-		\|-
	\| Pod 4 ~~VM A~~ \|\| 172.17.xx.xx		\| Pod 4 hv G \|\| 172.17.51.45
	\|-		\|-
	\| Pod 4 ~~VM B~~ \|\| 172.17.xx.xx		\| Pod 4 hv H \|\| 172.17.51.46
	\|-		\|-
	\| Pod ~~5 VM A~~ \|\| 172.17.xx.xx		\| Pod 4 PC D \|\| 172.17.51.47
	\|-		\|-
	\| Pod 5 ~~VM B~~ \|\| 172.17.xx.xx		\| Pod 5 hv I \|\| 172.17.51.50
	\|-		\|-
	\| Pod ~~6 VM A~~ \|\| 172.17.xx.xx		\| Pod 5 hv J \|\| 172.17.51.51
	\|-		\|-
	\| Pod 6 ~~VM B~~ \|\| 172.17.xx.xx		\| Pod 5 PC E \|\| 172.17.51.52
			\|-
			\| Pod 6 hv K \|\| 172.17.51.55
			\|-
			\| Pod 6 hv L \|\| 172.17.51.56
			\|-
			\| Pod 6 PC F \|\| 172.17.51.57
	\|}		\|}
	{\| class="wikitable" style="display: inline-table;"		{\| class="wikitable" style="display: inline-table;"
	! System !! IP		! System !! IP
	\|-		\|-
	\| Pod 7 ~~VM A~~ \|\| 172.17.xx.xx		\| Pod 7 hv M \|\| 172.17.51.60
	\|-
	~~\| 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 7 hv N \|\| 172.17.51.61
	\|-		\|-
	\| Pod ~~9 VM B~~ \|\| 172.17.xx.xx		\| Pod 7 PC G \|\| 172.17.51.62
	\|}		\|}

BenFranske: /* IP Addressing */

2020-09-17T16:54:42Z

IP Addressing

← Older revision		Revision as of 16:54, 17 September 2020
Line 1:		Line 1:
	=IP Addressing=		=IP Addressing=
	You will be assigning static IPs to your systems in this lab. Please use these settings:		You will be assigning static IPs to your systems in this lab. Please use these settings:
	~~All VMs:~~
	* Subnet Mask: 255.255.255.0		* Subnet Mask: 255.255.255.0
	* Default Gateway: 172.17.xx.1		* Default Gateway: 172.17.xx.1

BenFranske: Created page with "=IP Addressing= You will be assigning static IPs to your systems in this lab. Please use these settings: All VMs: * Subnet Mask: 255.255.255.0 * Default Gateway: 172.17.xx.1 *..."

2020-09-17T16:54:28Z

Created page with "=IP Addressing= You will be assigning static IPs to your systems in this lab. Please use these settings: All VMs: * Subnet Mask: 255.255.255.0 * Default Gateway: 172.17.xx.1 *..."

New page

=IP Addressing=
You will be assigning static IPs to your systems in this lab. Please use these settings:
All VMs:
* Subnet Mask: 255.255.255.0
* Default Gateway: 172.17.xx.1
* DNS Server 172.17.139.11

{| class="wikitable" style="display: inline-table;"
! 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
|}
{| class="wikitable" style="display: inline-table;"
! 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
|}
{| class="wikitable" style="display: inline-table;"
! 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=
# 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
# Boot both your Proxmox VE Server systems
# 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 [https://pve.proxmox.com/wiki/Linux_Container#pct_container_images ProxMox Linux Containers] page.
# After you have the containers downloaded go ahead and deploy a container based on the Debian template, use DHCP addressing.
# Try using the Debian container to see if it feels any different than a regular Debian VM.
# 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.
# Add your Proxmox server B to your Proxmox cluster.
# Deploy a Ubuntu container to a node in your Proxmox cluster, verify it is working
# Deploy a Wordpress server container to a node in your Proxmox cluster, verify it is working
# 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
# 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.
# 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.
# Open a connection directly to the VM with remote access
# 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.
# 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
# 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
# Try cloning one of your VMs
# Safely shut down all your containers and VMs
# Safely shutdown your Proxmox VE servers