I am working on a project where we are currently attempting to use proxmox to host lab environments.
Users can log into a webpage where they can start lab. The system calls proxmox to clone a vm template and create the lab. Users can tinker around with real servers to get a grasp on server admin concepts. This is also implemented and we have been successfully able to proxy the noVNC server from proxmox using NGINX. We used the proxy server to handle authentication.
We are now trying to support multi-vm labs where a set of vms get added to a network in which: they can access the internet, they cannot access another user's lab or our internal infrastructure. We would also like to give users the ability to customize their own switches.
My questions are:
Do we handle the networking of this with Open vSwitch and if we do, how do we gracefully adjust the configuration without rebooting the entire host? Is there a graceful way of handling this?
How to we allow users to tinker with switches while also preventing them from accessing another user's lab.
Thanks!
Users can log into a webpage where they can start lab. The system calls proxmox to clone a vm template and create the lab. Users can tinker around with real servers to get a grasp on server admin concepts. This is also implemented and we have been successfully able to proxy the noVNC server from proxmox using NGINX. We used the proxy server to handle authentication.
We are now trying to support multi-vm labs where a set of vms get added to a network in which: they can access the internet, they cannot access another user's lab or our internal infrastructure. We would also like to give users the ability to customize their own switches.
My questions are:
Do we handle the networking of this with Open vSwitch and if we do, how do we gracefully adjust the configuration without rebooting the entire host? Is there a graceful way of handling this?
How to we allow users to tinker with switches while also preventing them from accessing another user's lab.
Thanks!
Last edited: