Proxmox - Revision history

R232huan at 23:51, 12 August 2026

2026-08-12T23:51:59Z

← Older revision		Revision as of 18:51, 12 August 2026
Line 1:		Line 1:
	The Proxmox Vitural Environment ~~(as of 2025-11-02)~~ is a cluster hosted on ~~citric-acid~~, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. https://citric-acid.csclub.uwaterloo.ca:8006.		The Proxmox Vitural Environment is a cluster hosted on sorbitol, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. [https://citric-acid.csclub.uwaterloo.ca:8006 https://tahini.csclub.uwaterloo.ca:8006].

	== LDAP ==		== LDAP ==

S23adhik at 22:04, 15 July 2026

2026-07-15T22:04:14Z

← Older revision		Revision as of 17:04, 15 July 2026
Line 1:		Line 1:
	The Proxmox Vitural Environment (as of 2025-11-02) is a cluster hosted on citric-acid, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. https://citric-acid.csclub.uwaterloo.ca:8006.		The Proxmox Vitural Environment (as of 2025-11-02) is a cluster hosted on citric-acid, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. https://citric-acid.csclub.uwaterloo.ca:8006.

	== ~~Setting up Proxmox~~ ==		== LDAP ==
	To setup ~~proxmox~~, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`.		To setup LDAP, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`.

			Then go to the LDAP page, add ldap realm, and input ldap1.csclub.uwaterloo.ca, and ldap2.csclub.uwaterloo.ca as the servers. Then make sure to sync both groups, and users.
	Then just make sure pam is setup lol

			Label it `csclub`, and make sure to log in using that realm when logging in from web ui.

	== Joining the Cluster ==		== Joining the Cluster ==
Line 11:		Line 13:
	On the new node, from `Server View`, open the `Datacenter` page. Then go to `Cluster`, then `Join Cluster` and paste the join information. You will need to enter the root password of the host where you copied the join information.		On the new node, from `Server View`, open the `Datacenter` page. Then go to `Cluster`, then `Join Cluster` and paste the join information. You will need to enter the root password of the host where you copied the join information.

	== ~~Ceph~~ ==		== Virtual Machines ==
			When making virtual machines in proxmox please first consider whether a full vm is needed, or an lxc will do.
	We use Ceph to store VM and container disks as well as ISO images to allow easy migration between nodes.

			Then go ahead, choose the node (reccomended to choose teriyaki, or tahini), and set a name.

			When setting the name, if it is for a member please use `[watiam]-whatever-they-want`. If it's for something else, please name it clearly. Then when you get to os [storage is still TBD, check syscom irc, same with ISO image].

			Add Qemu Agent, otherwise rest are fine with defaults.

			Disks [TBD]

			Network TBD

	== Networking ==		== Networking ==

R232huan: /* Setting up Proxmox */

2025-11-02T20:15:00Z

Setting up Proxmox

← Older revision		Revision as of 15:15, 2 November 2025
Line 1:		Line 1:
	The Proxmox Vitural Environment (as of 2025-09-15) ~~lives~~ on ~~the~~ citric-acid ~~machine~~ and can be accessed via https://citric-acid.csclub.uwaterloo.ca:8006.		The Proxmox Vitural Environment (as of 2025-11-02) is a cluster hosted on citric-acid, tahini and teriyaki. The GUI can be accessed via the hostname of any machine on port 8006, e.g. https://citric-acid.csclub.uwaterloo.ca:8006.

	== Setting up Proxmox ==		== Setting up Proxmox ==
Line 5:		Line 5:

	Then just make sure pam is setup lol		Then just make sure pam is setup lol

			== Joining the Cluster ==
			To join the cluster, go to the existing CSC Cluster, from `Server View`, open the `Datacenter` page. Then go to `Cluster` and copy the join information.

			On the new node, from `Server View`, open the `Datacenter` page. Then go to `Cluster`, then `Join Cluster` and paste the join information. You will need to enter the root password of the host where you copied the join information.

			== Ceph ==
			We use Ceph to store VM and container disks as well as ISO images to allow easy migration between nodes.

	== Networking ==		== Networking ==

K95ma: +

2025-09-16T02:22:47Z

← Older revision		Revision as of 21:22, 15 September 2025
Line 1:		Line 1:
			The Proxmox Vitural Environment (as of 2025-09-15) lives on the citric-acid machine and can be accessed via https://citric-acid.csclub.uwaterloo.ca:8006.

	== Setting up Proxmox ==		== Setting up Proxmox ==
	To setup proxmox, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`.		To setup proxmox, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`.
Line 10:		Line 12:

	Currently, <code>vmbr0</code> is used for bridged network and <code>vmbr1</code> is used for NAT (see [https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_masquerading Proxmox's wiki on NAT networking] for setup instruction). <code>vmbr0</code> uses the CSC DHCP server, so you can use DHCP there, but <code>vmbr1</code> requires manual IP assignment.		Currently, <code>vmbr0</code> is used for bridged network and <code>vmbr1</code> is used for NAT (see [https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_masquerading Proxmox's wiki on NAT networking] for setup instruction). <code>vmbr0</code> uses the CSC DHCP server, so you can use DHCP there, but <code>vmbr1</code> requires manual IP assignment.

			Note that only using <code>vmbr1</code> requires you to use SSH ProxyJump via citric-acid to access the inner container, as it wouldn't have a public IP.

Y266shen: networking

2025-09-16T00:26:00Z

networking

← Older revision		Revision as of 19:26, 15 September 2025
Line 3:		Line 3:

	Then just make sure pam is setup lol		Then just make sure pam is setup lol

			== Networking ==
			There are two ways to do networking: network bridge and NAT. Network bridge will put the container/virtual machine on the CSC network (basically side-by-side to proxmox itself), while NAT will encapsulate the container/VM inside a private subnet that is only visible to proxmox host itself.

			For services that only exposes HTTP/HTTPS, NAT is more desirable since multiple services can share a host nginx instance, only requiring the host IP to have 80/443 port opened to the Internet, thus saving some IP address in our pool and save some trips to the IST for firewall exemption. But for services that requires custom ports to be opened (for example, BigBlueButton requires a range of UDP ports to be exposed for relaying video streams), using the network bridge and giving the container/VM its own public IP might be easier.

			Currently, <code>vmbr0</code> is used for bridged network and <code>vmbr1</code> is used for NAT (see [https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_masquerading Proxmox's wiki on NAT networking] for setup instruction). <code>vmbr0</code> uses the CSC DHCP server, so you can use DHCP there, but <code>vmbr1</code> requires manual IP assignment.

S23adhik: Created page with "== Setting up Proxmox == To setup proxmox, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`. Then just make sure pam is setup lol"

2025-07-04T21:40:29Z

Created page with "== Setting up Proxmox == To setup proxmox, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`. Then just make sure pam is setup lol"

New page

== Setting up Proxmox ==
To setup proxmox, from `Server View`, open the `Datacenter` page. Then go to `Permissions -> Realms`.

Then just make sure pam is setup lol