Difference between revisions of "Talk:Educaship Proxmox"
m (Gary moved page Talk:CNM Proxmox to Talk:Educaship Proxmox without leaving a redirect) |
|||
| Line 1: | Line 1: | ||
[[TSP-1]] | [[TSP-1]] | ||
| + | |||
| + | Proxmox for CNM Farms (hereinafter, [[#The Project]]) is the group of endeavors undertaken to advance key aspects of [[Educaship Proxmox]] (hereinafter, [[#The VE]]) including its functionality, usability, reliability, performance, security, scalability, and user satisfaction. | ||
| + | |||
| + | [[CNMCyber Team]] (hereinafter, [[#We]]) currently administers [[#The VE]]. | ||
| + | |||
| + | |||
| + | ==Current state of the VE== | ||
| + | Currently, [[#The VE]] 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 VE]] 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=== | ||
| + | : The peripheral part of [[#The VE]] is called [[CNM Lab Farm]] and is based on one metal server of [[Lab Infrastructure]]. It utilizes [[...]] storage. | ||
| + | |||
| + | ===Adding More VEs=== | ||
| + | : When [[#We]] need more resources, [[#We]] plan to add more instances similar to [[#Peripheral VE]] to the [[#Federated VE]]. | ||
| + | |||
| + | ==Most Urgent Issues== | ||
| + | The issues to work on may include (a) security outside of [[iptables]], (b) adding NAS, as well as advanced backup and recovery systems, and (c) advanced monitoring systems. | ||
| + | |||
| + | ==Requirements== | ||
| + | ===Business=== | ||
| + | : [[Business requirement]]s | ||
| + | |||
| + | ===Prototypes=== | ||
| + | : [[Prototype]]s | ||
| + | |||
| + | ===Stakeholder's=== | ||
| + | : [[Stakeholder requirement]]s | ||
| + | |||
| + | ===Deliverable=== | ||
| + | :[[Deliverable specification]]s | ||
| + | |||
| + | ===Work=== | ||
| + | : [[Work specification]]s | ||
| + | |||
| + | ==States== | ||
| + | ===Certainty=== | ||
| + | : [[State of certainty]] | ||
| + | |||
| + | ===Utility=== | ||
| + | : [[State of utility]] | ||
| + | |||
| + | ===Applicability=== | ||
| + | : [[State of applicability]] | ||
| + | |||
| + | ===Controllability=== | ||
| + | : [[State of controllability]] | ||
| + | |||
| + | Hello, Michel ! | ||
| + | Here are a few brief answers to your questions. Please let me know what else you'd like to know. | ||
| + | 1\. 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. | ||
| + | 2\. We are experiencing some issues obtaining a certificate for a site running behind Pfsense. Due to the absence of the certificate, the service becomes completely unavailable | ||
| + | 3\. We have several websites whose 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. | ||
| + | 4\. In some cases, we have used Ansible. We are open to any solution | ||
| + | 5\. 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. | ||
| + | |||
| + | ==Key Terms== | ||
| + | ===The VE=== | ||
| + | ===The Project=== | ||
| + | ===We=== | ||
| + | [[Category: CNMCyber endeavors]] | ||
Revision as of 14:01, 16 April 2024
Proxmox for CNM Farms (hereinafter, #The Project) is the group of endeavors undertaken to advance key aspects of Educaship Proxmox (hereinafter, #The VE) including its functionality, usability, reliability, performance, security, scalability, and user satisfaction.
CNMCyber Team (hereinafter, #We) currently administers #The VE.
Current state of the VE
Currently, #The VE 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 VE 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 VE is called CNM Lab Farm and is based on one metal server of Lab Infrastructure. It utilizes ... storage.
Adding More VEs
- When #We need more resources, #We plan to add more instances similar to #Peripheral VE to the #Federated VE.
Most Urgent Issues
The issues to work on may include (a) security outside of iptables, (b) adding NAS, as well as advanced backup and recovery systems, and (c) advanced monitoring systems.
Requirements
Business
Prototypes
Stakeholder's
Deliverable
Work
States
Certainty
Utility
Applicability
Controllability
Hello, Michel ! Here are a few brief answers to your questions. Please let me know what else you'd like to know. 1\. 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. 2\. We are experiencing some issues obtaining a certificate for a site running behind Pfsense. Due to the absence of the certificate, the service becomes completely unavailable 3\. We have several websites whose 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. 4\. In some cases, we have used Ansible. We are open to any solution 5\. 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.
