Difference between revisions of "CNMCyber Usable"
(→iDosvid) |
|||
(12 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | [[CNM Cloud Usable]] | + | [[CNMCyber Usable]] (formerly known as [[CNM Cloud Usable]]; in the Russian-language version, known as [https://pravka.bskol.com/ru/%D0%A0%D0%B0%D0%B1%D0%BE%D1%82%D1%8B_%D0%BD%D0%B0%D0%B4_%D0%9E%D0%B1%D0%BB%D0%B0%D0%BA%D0%BE%D0%BC Работы над Облаком]) is the fourth, current, phase of the [[CNM Cloud Project]]. [[Opplet]] (hereinafter, the ''Cloud'') is a set of technologies that supports [[CNMCyber]] (hereinafter, the ''Cyber''). This very wikipage presents the primary list of those endeavors that are included in that phase. [[CNMCyber Coordinator]]s (hereinafter, the ''Coordinators'') are invited to coordinate those endeavors. |
Line 9: | Line 9: | ||
===This page navigation=== | ===This page navigation=== | ||
− | : This very wikipage is designed to publish progress reports on the endeavors that are listed in the [[:Category: | + | : This very wikipage is designed to publish progress reports on the endeavors that are listed in the [[:Category: CNMCyber endeavors|"CNMCyber endeavors" category]]. The endeavor tags are included in the head row of the tables; the term, ''work'', refers to the endeavors'' on this very page. |
: Those tables also contain reports, links to the products that the endeavors are designed to benefit, as well as links to applicable wikipages of [[commercial off-the-shelf]] ([[commercial off-the-shelf|COTS]]) products that power the ''Cyber'' products. | : Those tables also contain reports, links to the products that the endeavors are designed to benefit, as well as links to applicable wikipages of [[commercial off-the-shelf]] ([[commercial off-the-shelf|COTS]]) products that power the ''Cyber'' products. | ||
==Admin tools== | ==Admin tools== | ||
− | : For the purposes of this wikipage, ''support tools'' refer to those software development and sysadmin administrative tools that are (a) listed at https://github.com/kahun/awesome-sysadmin and (b) not mentioned in other sections of the endeavors. | + | : For the purposes of this very wikipage, ''support tools'' refer to those software development and sysadmin administrative tools that are (a) listed at https://github.com/kahun/awesome-sysadmin and (b) not mentioned in other sections of the endeavors. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to support tools | |+Authorized endeavors related to support tools | ||
Line 45: | Line 45: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[Panels in CNM Farms|Panels (product)]]!![[ | + | ![[Panels in CNM Farms|Panels (product)]]!![[Educaship Eclipse]]!![[Educaship Nextcloud]]!![[Educaship LDAP]] |
|- | |- | ||
!COTS | !COTS | ||
Line 55: | Line 55: | ||
===Farms' administration=== | ===Farms' administration=== | ||
− | : For the purposes of this wikipage, the ''Farms<nowiki>'</nowiki> administration'' refers to those endeavors that are utilized or can be used on several rather than one individual ''Farm''. | + | : For the purposes of this very wikipage, the ''Farms<nowiki>'</nowiki> administration'' refers to those endeavors that are utilized or can be used on several rather than one individual ''Farm''. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to administration of the Farms | |+Authorized endeavors related to administration of the Farms | ||
Line 95: | Line 95: | ||
===Farms' monitoring=== | ===Farms' monitoring=== | ||
− | : For the purposes of this wikipage, the ''Farms<nowiki>'</nowiki> monitoring'' refers to those systems that monitor one or more ''Farms''. | + | : For the purposes of this very wikipage, the ''Farms<nowiki>'</nowiki> monitoring'' refers to those systems that monitor one or more ''Farms''. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to monitoring of the Farms | |+Authorized endeavors related to monitoring of the Farms | ||
Line 126: | Line 126: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship Grafana]]!![[Educaship Zabbix]]!![[Educaship Nagios]] |
|- | |- | ||
!COTS | !COTS | ||
Line 135: | Line 135: | ||
===Farms' security=== | ===Farms' security=== | ||
− | : For the purposes of this wikipage, ''farms' security'' refers to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. | + | : For the purposes of this very wikipage, ''farms' security'' refers to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to security of the Farms | |+Authorized endeavors related to security of the Farms | ||
Line 166: | Line 166: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship iptables]]!![[Educaship Fail2ban]]!![[PfSense for Farms|Educaship pfSense]]!![[Educaship SpamAssassin]] |
|- | |- | ||
!COTS | !COTS | ||
Line 173: | Line 173: | ||
===DNS management=== | ===DNS management=== | ||
− | : For the purposes of this wikipage, ''DNS management'' refers to those endeavors that are utilized or can be used to manage [[DNS]] of the ''Cloud''. | + | : For the purposes of this very wikipage, ''DNS management'' refers to those endeavors that are utilized or can be used to manage [[DNS]] of the ''Cloud''. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to DNS management | |+Authorized endeavors related to DNS management | ||
Line 211: | Line 211: | ||
===Farm platforms=== | ===Farm platforms=== | ||
− | : For the purposes of this wikipage, ''farm platforms'' refer to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. | + | : For the purposes of this very wikipage, ''farm platforms'' refer to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to farm platforms | |+Authorized endeavors related to farm platforms | ||
|Endeavors | |Endeavors | ||
− | ![[ | + | ![[Talk:Educaship Proxmox|Proxmox (work)]]!![[HAProxy for CNM Farms|HAProxy (work)]]!![[Farm for Lab|Lab (farmwork)]]!![[Farm for Opplet|Opplet (farmwork)]] |
|- | |- | ||
![[Business requirement]]s | ![[Business requirement]]s | ||
Line 242: | Line 242: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship Proxmox]]!![[Educaship HAProxy]]!![[Farm for Lab|Lab (farm)]]!![[Farm for Opplet|Opplet (farm)]] |
|- | |- | ||
!COTS | !COTS | ||
− | |[[ProxmoxVE]]||[[HAProxy]]||[[OpenStack]]||[[Apache CloudStack|CloudStack]] | + | |[[ProxmoxVE]], [[Proxmox Backup Server]]||[[HAProxy]]||[[OpenStack]]||[[Apache CloudStack|CloudStack]] |
|} | |} | ||
Line 251: | Line 251: | ||
===DBMS=== | ===DBMS=== | ||
− | : For the purposes of this wikipage, ''DBMS'' refer to those endeavors that are related to [[database management system]]s ([[database management system|DBMS]]) of the ''Cloud''. | + | : For the purposes of this very wikipage, ''DBMS'' refer to those endeavors that are related to [[database management system]]s ([[database management system|DBMS]]) of the ''Cloud''. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to database management | |+Authorized endeavors related to database management | ||
Line 282: | Line 282: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship MariaDB]]!![[Educaship PostgreSQL]]!![[OppletDB]]!![[Educaship Ceph]] |
|- | |- | ||
!COTS | !COTS | ||
Line 289: | Line 289: | ||
===Farms' recovery=== | ===Farms' recovery=== | ||
− | : For the purposes of this wikipage, ''farms' security'' refers to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. | + | : For the purposes of this very wikipage, ''farms' security'' refers to clusters of nodes that are utilized or can be used to build the ''Farms''. The four ''Farms'' are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available ''Farms'' includes a [[load balancer]] on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to recovery of the Farms | |+Authorized endeavors related to recovery of the Farms | ||
Line 320: | Line 320: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship mysqldump]]!![[Educaship Mariabackup]]!![[Bureau Backup Server]]!![[for Opplet|Opplet (farm)]] |
|- | |- | ||
!COTS | !COTS | ||
Line 334: | Line 334: | ||
===App-oriented=== | ===App-oriented=== | ||
− | : For the purposes of this wikipage, ''app-oriented Opplet'' refers to those endeavors to build [[Opplet]] that support [[CNM app]]s rather than its [[end-user]]s. | + | : For the purposes of this very wikipage, ''app-oriented Opplet'' refers to those endeavors to build [[Opplet]] that support [[CNM app]]s rather than its [[end-user]]s. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to app-oriented Opplet | |+Authorized endeavors related to app-oriented Opplet | ||
Line 372: | Line 372: | ||
===User-oriented=== | ===User-oriented=== | ||
− | : For the purposes of this wikipage, ''user-oriented Opplet'' refers to those endeavors to build [[Opplet]] that support its [[end-user]]s rather than [[CNM app]]s. | + | : For the purposes of this very wikipage, ''user-oriented Opplet'' refers to those endeavors to build [[Opplet]] that support its [[end-user]]s rather than [[CNM app]]s. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to user-oriented Opplet | |+Authorized endeavors related to user-oriented Opplet | ||
Line 417: | Line 417: | ||
===Utilizing MariaDB=== | ===Utilizing MariaDB=== | ||
− | : For the purposes of this wikipage, ''utilizing MariaDB apps'' refer to those [[CNM stable app]]s that utilize [[MariaDB]] as its database management system. The ''Cloud'' incorporates at least five of them. | + | : For the purposes of this very wikipage, ''utilizing MariaDB apps'' refer to those [[CNM stable app]]s that utilize [[MariaDB]] as its database management system. The ''Cloud'' incorporates at least five of them. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to utilizing MariaDB apps | |+Authorized endeavors related to utilizing MariaDB apps | ||
Line 448: | Line 448: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship AVideo]]!![[Educaship WordPress]]!![[Educaship MediaWiki]]!![[Educaship HumHub]]!![[Educaship Moodle]] |
|- | |- | ||
!COTS | !COTS | ||
Line 455: | Line 455: | ||
===Utilizing non-MariaDB=== | ===Utilizing non-MariaDB=== | ||
− | : For the purposes of this wikipage, ''utilizing non-MariaDB apps'' refer to those [[CNM stable app]]s that don't utilize [[MariaDB]] as its database management system. The ''Cloud'' incorporates at least four of those ''Apps'': | + | : For the purposes of this very wikipage, ''utilizing non-MariaDB apps'' refer to those [[CNM stable app]]s that don't utilize [[MariaDB]] as its database management system. The ''Cloud'' incorporates at least four of those ''Apps'': |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to utilizing non-MariaDB apps | |+Authorized endeavors related to utilizing non-MariaDB apps | ||
Line 462: | Line 462: | ||
|- | |- | ||
![[Business requirement]]s | ![[Business requirement]]s | ||
− | | || || || | + | | || || ||[[Jitsi for CNM Cloud#Business|Done]] |
|- | |- | ||
![[Prototype]]s | ![[Prototype]]s | ||
− | | || || || | + | | || || ||[[Jitsi for CNM Cloud#Prototypes|Done]] |
|- | |- | ||
![[Stakeholder requirement]]s | ![[Stakeholder requirement]]s | ||
− | | || || || | + | | || || ||[[Jitsi for CNM Cloud#Stakeholder's|Done]] |
|- | |- | ||
![[Product specification]]s | ![[Product specification]]s | ||
− | | || || || | + | | || || ||[[Educaship Jitsi#Product specification|Done]] |
|- | |- | ||
![[State of certainty|Certainty]] | ![[State of certainty|Certainty]] | ||
− | | || || || | + | | || || ||[[Jitsi for CNM Cloud#Certainty|Done]] |
|- | |- | ||
![[State of utility|Utility]] | ![[State of utility|Utility]] | ||
− | | || || || | + | | || || ||[[Jitsi for CNM Cloud#Utility|In progress]] |
|- | |- | ||
![[State of applicability|Applicability]] | ![[State of applicability|Applicability]] | ||
Line 486: | Line 486: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship GitLab]]!![[Educaship SuiteCRM]]!![[Educaship Odoo]]!![[Educaship Jitsi]] |
|- | |- | ||
!COTS | !COTS | ||
Line 493: | Line 493: | ||
===Experimental=== | ===Experimental=== | ||
− | : For the purposes of this wikipage, ''experimental apps'' refer to (a) [[CNM future app]]s, (b) some applications that have been installed to be analyzed and evaluated, (c) those applications that are to be utilized during short hands-on training sessions, and (d) legacy applications that are retired from [[CNM stable app]], but are still kept as "museum" exhibits. | + | : For the purposes of this very wikipage, ''experimental apps'' refer to (a) [[CNM future app]]s, (b) some applications that have been installed to be analyzed and evaluated, (c) those applications that are to be utilized during short hands-on training sessions, and (d) legacy applications that are retired from [[CNM stable app]], but are still kept as "museum" exhibits. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to experimental apps | |+Authorized endeavors related to experimental apps | ||
Line 524: | Line 524: | ||
|- | |- | ||
|Products | |Products | ||
− | ![[ | + | ![[Educaship OpenEdX]]!![[Educaship ProjecQtOr]]!![[Educaship Redmine]]!![[Educaship Taiga]] |
|- | |- | ||
!COTS | !COTS | ||
Line 532: | Line 532: | ||
==Enterprise== | ==Enterprise== | ||
===Venture administration=== | ===Venture administration=== | ||
− | : For the purposes of this wikipage, ''venture administration'' refers to human administration of the ''Cloud'' enterprise. | + | : For the purposes of this very wikipage, ''venture administration'' refers to human administration of the ''Cloud'' enterprise. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to enterprise administration | |+Authorized endeavors related to enterprise administration | ||
Line 567: | Line 567: | ||
===External operations=== | ===External operations=== | ||
− | : For the purposes of this wikipage, ''enterprise external operations'' refer to those endeavors that are utilized or can be used outside of the enterprise behind the ''Cloud''. | + | : For the purposes of this very wikipage, ''enterprise external operations'' refer to those endeavors that are utilized or can be used outside of the enterprise behind the ''Cloud''. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to enterprise external operations | |+Authorized endeavors related to enterprise external operations | ||
Line 602: | Line 602: | ||
===Stakeholder groups=== | ===Stakeholder groups=== | ||
− | : For the purposes of this wikipage, ''stakeholder groups'' refer to those endeavors that are utilized or can be used to manage groups of the ''Cloud'' stakeholders. | + | : For the purposes of this very wikipage, ''stakeholder groups'' refer to those endeavors that are utilized or can be used to manage groups of the ''Cloud'' stakeholders. |
:{|class="wikitable" width=100% style="text-align:center;" | :{|class="wikitable" width=100% style="text-align:center;" | ||
|+Authorized endeavors related to stakeholder groups | |+Authorized endeavors related to stakeholder groups |
Latest revision as of 14:02, 16 April 2024
CNMCyber Usable (formerly known as CNM Cloud Usable; in the Russian-language version, known as Работы над Облаком) is the fourth, current, phase of the CNM Cloud Project. Opplet (hereinafter, the Cloud) is a set of technologies that supports CNMCyber (hereinafter, the Cyber). This very wikipage presents the primary list of those endeavors that are included in that phase. CNMCyber Coordinators (hereinafter, the Coordinators) are invited to coordinate those endeavors.
Contents
Trivia
Cloud layers
- CNM Farms. The Cloud infrastructure or, in other words, ecosystem of computing servers and cloud OS to support both Opplet and CNM apps. On this very wikipage, the Farms endeavors are divided in Farms (in general) and Database management.
- Opplet. The enterprise-wide utility software that supports CNM apps regardless of their location of those applications in the Cloud. On this very wikipage, the Opplet endeavors are divided in App-oriented and User-oriented.
- CNM apps. End-user applications of the Cloud. On this very wikipage, the apps endeavors are divided in Utilizing MariaDB, Utilizing non-MariaDB, and Experimental.
- This very wikipage is designed to publish progress reports on the endeavors that are listed in the "CNMCyber endeavors" category. The endeavor tags are included in the head row of the tables; the term, work, refers to the endeavors on this very page.
- Those tables also contain reports, links to the products that the endeavors are designed to benefit, as well as links to applicable wikipages of commercial off-the-shelf (COTS) products that power the Cyber products.
Admin tools
- For the purposes of this very wikipage, support tools refer to those software development and sysadmin administrative tools that are (a) listed at https://github.com/kahun/awesome-sysadmin and (b) not mentioned in other sections of the endeavors.
Authorized endeavors related to support tools Endeavors Panels (work) Eclipse (work) Nextcloud (work) LDAP (work) Business requirements Submitted Submitted Prototypes Stakeholder requirements Submitted Submitted Product specifications Certainty Utility Applicability Controllability Products Panels (product) Educaship Eclipse Educaship Nextcloud Educaship LDAP COTS VestaCP, Cachet Eclipse software Nextcloud OpenLDAP
Farms (in general)
CNM Farms (hereinafter, the Farms) present the infrastructure for the functioning of both the CNM apps and Opplet that serves those apps. The Farms are assembled using commercial off-the-shelf (COTS) software only.
Farms' administration
- For the purposes of this very wikipage, the Farms' administration refers to those endeavors that are utilized or can be used on several rather than one individual Farm.
Authorized endeavors related to administration of the Farms Endeavors Integration (work) Configuration (work) Statistics (work) Farmwork (overall) Business requirements Done Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Integration (product) Configuration (product) Statistics (product) CNM Farms* COTS Jenkins, Kafka, OpenVPN Terraform, Ansible ZooKeeper N/A *CNM Farms include CNM Bureau Farm, CNM Campus Farm, Opplet Farm, as well as CNM Lab Farm and its sub-farms Campus Farm Lab, Bureau Farm Lab, Opplet Farm Lab.
Farms' monitoring
- For the purposes of this very wikipage, the Farms' monitoring refers to those systems that monitor one or more Farms.
Authorized endeavors related to monitoring of the Farms Endeavors Grafana (work) Zabbix (work) Nagios (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship Grafana Educaship Zabbix Educaship Nagios COTS Grafana Zabbix Nagios
InfluxDB
Farms' security
- For the purposes of this very wikipage, farms' security refers to clusters of nodes that are utilized or can be used to build the Farms. The four Farms are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available Farms includes a load balancer on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems.
Authorized endeavors related to security of the Farms Endeavors Iptables (work) Fail2ban (work) PfSense (work) SpamAssassin (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship iptables Educaship Fail2ban Educaship pfSense Educaship SpamAssassin COTS Iptables Fail2ban PfSense Apache SpamAssassin
DNS management
- For the purposes of this very wikipage, DNS management refers to those endeavors that are utilized or can be used to manage DNS of the Cloud.
Authorized endeavors related to DNS management Endeavors CDN (work) DNSSEC (work) Geocast (work) IPv6 (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products CDN (product) DNSSEC (product) Geocast (product) IPv6 (product) COTS N/A N/A N/A N/A
Farm platforms
- For the purposes of this very wikipage, farm platforms refer to clusters of nodes that are utilized or can be used to build the Farms. The four Farms are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available Farms includes a load balancer on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems.
Authorized endeavors related to farm platforms Endeavors Proxmox (work) HAProxy (work) Lab (farmwork) Opplet (farmwork) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship Proxmox Educaship HAProxy Lab (farm) Opplet (farm) COTS ProxmoxVE, Proxmox Backup Server HAProxy OpenStack CloudStack
Database management
DBMS
- For the purposes of this very wikipage, DBMS refer to those endeavors that are related to database management systems (DBMS) of the Cloud.
Authorized endeavors related to database management Работы MariaDB (work) PostgreSQL (work) OppletDB (work) Ceph (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship MariaDB Educaship PostgreSQL OppletDB Educaship Ceph COTS MariaDB PostgeSQL Cassandra, MuleESB, Hadoop Ceph
Farms' recovery
- For the purposes of this very wikipage, farms' security refers to clusters of nodes that are utilized or can be used to build the Farms. The four Farms are made up of clustered nodes. Each cluster must have at least one (a) DNS entry point, which for highly available Farms includes a load balancer on a public web address, (b) synchronization of resources of common individual nodes, at least databases, (c) monitoring, ( d) security, including firewalls; and (e) backup and recovery systems.
Authorized endeavors related to recovery of the Farms Endeavors (work) (work) (work) Opplet (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship mysqldump Educaship Mariabackup Bureau Backup Server Opplet (farm) COTS [[]] [[]] [[]] [[]]
Opplet
Opplet represents (a) enterprise-wide middleware that serves the Cloud and (b) a group of end-user applications that allows end-users to utilize it. Therefore, the Opplet's functionalities can be divided into two groups:
- Services for CNM apps. Those federation services that Opplet provides to CNM apps.
- Services for end-users. Those services that Opplet provides to its end-users.
Some endeavors that are related to Opplet are included in the Farm for Opplet project (section Farm platforms of this very wikipage) and DBs for Opplet project (section Database management). The core of Opplet is written specifically for the Cloud using Yii framework. Its periphery devices are assembled using commercial off-the-shelf (COTS) software.
App-oriented
- For the purposes of this very wikipage, app-oriented Opplet refers to those endeavors to build Opplet that support CNM apps rather than its end-users.
Authorized endeavors related to app-oriented Opplet Endeavors WSO2 IS (work) Enrollment (work) IAM (work) Mail (work) Exams (work) Warehouse (work) Business requirements Submitted Prototypes Stakeholder requirements Submitted Product specifications Submitted Certainty Utility Applicability Controllability Products WSO2 IS Enrollments IAM Mail (server) Exams Warehouse COTS WSO2 IS Yii Yii N/A Yii N/A
User-oriented
- For the purposes of this very wikipage, user-oriented Opplet refers to those endeavors to build Opplet that support its end-users rather than CNM apps.
Authorized endeavors related to user-oriented Opplet Endeavors Interface (work) Events (work) Mailboxes (work) Newsletters (work) Calendar (work) Profile (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Interface Events Mailboxes Newsletters Calendar Profiles COTS Yii Yii N/A N/A N/A Yii
CNM apps
CNM apps (hereinafter, the Apps) present end-user applications that are available to users of the Cloud. The Apps include:
- CNM stable apps that have at least 2 installations -- one is used for its target purposes and another is available for hands-on training. Any stable App needs to be able to work with our future Opplet WSO2 IS and, possibly, existing OpenLDAP. The Apps are assembled using commercial off-the-shelf (COTS) software only. Those endeavors that need to be undertaken for every stable App, must encompass (a) updating the Apps to the latest stable versions and install the latest patches if and when they become available and (b) documenting what we have and identify problems.
- CNM future apps that are installed on the CNM Lab Farm only. These apps represent either popular COTS packages or end-user application that can be deployed in the Cloud as CNM stable apps in the future.
This section lists both (a) those Apps that are incorporated, both CNM stable and future apps, as well as (b) some applications that may be potentially incorporated in the Cloud. Some endeavors that are related to the Apps are included in projects listed in DNS management and App-oriented sections of this very wikipage.
Utilizing MariaDB
- For the purposes of this very wikipage, utilizing MariaDB apps refer to those CNM stable apps that utilize MariaDB as its database management system. The Cloud incorporates at least five of them.
Authorized endeavors related to utilizing MariaDB apps Endeavors AVideo (work) WordPress (work) MediaWiki (work) HumHub (work) Moodle (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship AVideo Educaship WordPress Educaship MediaWiki Educaship HumHub Educaship Moodle COTS AVideo WordPress MediaWiki HumHub Moodle
Utilizing non-MariaDB
- For the purposes of this very wikipage, utilizing non-MariaDB apps refer to those CNM stable apps that don't utilize MariaDB as its database management system. The Cloud incorporates at least four of those Apps:
Authorized endeavors related to utilizing non-MariaDB apps Endeavors GitLab (work) SuiteCRM (work) Odoo (work) Jitsi (work) Business requirements Done Prototypes Done Stakeholder requirements Done Product specifications Done Certainty Done Utility In progress Applicability Controllability Products Educaship GitLab Educaship SuiteCRM Educaship Odoo Educaship Jitsi COTS GitLab SuiteCRM Odoo Jitsi
Experimental
- For the purposes of this very wikipage, experimental apps refer to (a) CNM future apps, (b) some applications that have been installed to be analyzed and evaluated, (c) those applications that are to be utilized during short hands-on training sessions, and (d) legacy applications that are retired from CNM stable app, but are still kept as "museum" exhibits.
Authorized endeavors related to experimental apps Endeavors OpenEdX (work) ProjecQtOr (work) Redmine (work) Taiga (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Educaship OpenEdX Educaship ProjecQtOr Educaship Redmine Educaship Taiga COTS OpenEdX ProjecQtOr Redmine Taiga
Enterprise
Venture administration
- For the purposes of this very wikipage, venture administration refers to human administration of the Cloud enterprise.
Authorized endeavors related to enterprise administration Endeavors Personnel (work) Agency (work) Finance (work) Legal (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Personnel (product) Agency (product) Finance (product) Legal (product)
External operations
- For the purposes of this very wikipage, enterprise external operations refer to those endeavors that are utilized or can be used outside of the enterprise behind the Cloud.
Authorized endeavors related to enterprise external operations Endeavors Industry (work) Developers (work) Technologies (work) Help Desk (work) Operators (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Industry (product) Developers (product) Technologies (product) Help Desk (product) Operators (product)
Stakeholder groups
- For the purposes of this very wikipage, stakeholder groups refer to those endeavors that are utilized or can be used to manage groups of the Cloud stakeholders.
Authorized endeavors related to stakeholder groups Endeavors Councils (work) Committees (work) Users (work) Sysadmins (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products Councils (product) Committees (product) Users (product) Sysadmins (product)
iDosvid
iDosvid is a project that provides training, career guidance, and practical activities using the resources of the Braska School for students of Ukrainian schools. Page of developments and work on the project.
Endeavors related to promote the project Endeavors iDosvid.com (work) IDosvid.com design (work) Apps on iDosvid (work) Partner schools (work) Donors for iDosvid (work) Business requirements Done In progress Prototypes In progress Done Stakeholder requirements Done Submitted Product specifications In progress In progress Certainty Submitted Not started Utility Not started Not started Applicability Not started Not started Controllability Not started Not started Products iDosvid.com IDosvid.com design
Events
Endeavors related to promote the project Endeavors CNMCyber This Week (work) CNMCyber Guided Tours (work) Business requirements Prototypes Stakeholder requirements Product specifications Certainty Utility Applicability Controllability Products CNMCyber This Week (product) CNMCyber Guided Tours (product)