Difference between revisions of "Educaship Proxmox"
(→Instances) |
|||
| Line 1: | Line 1: | ||
| − | [[Educaship Proxmox]] (hereinafter, [[#The | + | [[Educaship Proxmox]] (hereinafter, [[#The VEs]]) is the [[ProxmoxVE]] instances and supporting software packages that are used at [[CNM Farms]]. |
| Line 6: | Line 6: | ||
===Learning Resource=== | ===Learning Resource=== | ||
==Instances== | ==Instances== | ||
| − | Currently, [[#The | + | Currently, [[#The VEs]] consists of two instances, [[#Federated VE]] and [[#Peripheral VE]]. [[#We]] will consider [[#Adding More VEs]] when such a need emerges. |
===Federated VE=== | ===Federated VE=== | ||
| − | : The federated part of [[#The | + | : The federated part of [[#The VEs]] is called [[CNM Bureau Farm]] and is based on three metal servers of [[Bureau Infrastructure]]. It utilizes <code>ha-manager</code> and [[Ceph]] storage. |
===Peripheral VE=== | ===Peripheral VE=== | ||
| − | : The peripheral part of [[#The | + | : The peripheral part of [[#The VEs]] is called [[CNM Lab Farm]] and is based on one metal server of [[Lab Infrastructure]]. |
===Adding More VEs=== | ===Adding More VEs=== | ||
| Line 20: | Line 20: | ||
===Jitsi functionality=== | ===Jitsi functionality=== | ||
| − | : Jitsi software is selected to be used for webconferencing. Currently, we use some instance outside of [[#The | + | : Jitsi software is selected to be used for webconferencing. Currently, we use some instance outside of [[#The VEs]] because of challenges as follows. We have multiple Jitsi installations, one of which is in Docker. In this installation, there is no sound at all. Also, when updating Docker, a conference is not created. |
===Openness to the world=== | ===Openness to the world=== | ||
| Line 31: | Line 31: | ||
===VM automation=== | ===VM automation=== | ||
| − | : We would like [[# | + | : We would like [[#Peripheral VE]] and [[#Peripheral VE]] only to create a VM for each VM customer automatically. In some cases, we have used Ansible. We are open to any solution. |
===Monitoring=== | ===Monitoring=== | ||
Revision as of 15:53, 16 April 2024
Educaship Proxmox (hereinafter, #The VEs) is the ProxmoxVE instances and supporting software packages that are used at CNM Farms.
Contents
Double Objective
Functional Platform
Learning Resource
Instances
Currently, #The VEs consists of two instances, #Federated VE and #Peripheral VE. #We will consider #Adding More VEs when such a need emerges.
Federated VE
- The federated part of #The VEs is called CNM Bureau Farm and is based on three metal servers of Bureau Infrastructure. It utilizes
ha-managerand Ceph storage.
Peripheral VE
- The peripheral part of #The VEs is called CNM Lab Farm and is based on one metal server of Lab Infrastructure.
Adding More VEs
- When #We need more resources, #We plan to add more instances similar to #Peripheral VE to the #Federated VE.
Projects
Jitsi functionality
- Jitsi software is selected to be used for webconferencing. Currently, we use some instance outside of #The VEs because of challenges as follows. We have multiple Jitsi installations, one of which is in Docker. In this installation, there is no sound at all. Also, when updating Docker, a conference is not created.
Openness to the world
- To utilize pfSense better, we consider clustering VMs at #Peripheral VE and placing HAProxy and similar proxies behind pfSense on the #Federated VE.
- We are experiencing some issues obtaining SSL certificates for our sites running behind Pfsense. Due to the absence of the certificate, the service becomes completely unavailable.
Storage for VMs
- We are looking for solutions for distributed storage available to several VMs. We have several websites that use MariaDB; their databases are combined in a Galera Cluster. We need a solution for these websites' files to have a shared storage. We tried GlusterFS, but it seemed too slow to us. We copied the files to this storage for almost a week, and as a result, the website did not work.
VM automation
- We would like #Peripheral VE and #Peripheral VE only to create a VM for each VM customer automatically. In some cases, we have used Ansible. We are open to any solution.
Monitoring
- Our current monitoring doesn't satisfy us. We use Grafana for Proxmox. We would like to add several servers that do not use Proxmox, configure communication channels, and expand monitoring according to our tasks.
Security
- Our security outline shall be reviewed and improved.
Backup and recovery
- We use Proxmox Backup Server on the #Federated VE. We consider adding NAS, as well as advancing backup and recovery systems.
