CNMCyber Usable

From CNM Wiki
Revision as of 23:43, 9 December 2022 by Gary (talk | contribs) (→‎External operations)
Jump to: navigation, search

CNM Cloud Usable (in the Russian-language version, known as Работы над Облаком) is the fourth, current, phase of the CNM Cloud Project. CNM Cloud (hereinafter - the Cloud) is a set of technologies that supports CNM Cyber. This very wikipage presents the primary list of those endeavors that are included in that phase. CNM Cyber Project Coordinators (hereinafter, the Coordinators) are invited to organize work on its endeavors.


Trivia

Projects vs operations

The endeavors include:
  • Projects undertaken to develop new systems to be deployed at the Cloud.
  • Operations undertaken to sustain productive functions of deployed systems of the Cloud.

Cloud layers

  1. CNM Farms. The Cloud infrastructure or, in other words, ecosystem of computing servers and cloud OS to support both Opplet and CNM apps.
  2. Opplet. The enterprise-wide utility software that supports CNM apps regardless of their location of those applications in the Cloud.
  3. CNM apps. End-user applications of the Cloud.

Farms

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 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 the Farms' administration
Progress Integration (work) Configuration (work) Statistics (work) Revisions (farms)
Business requirements Done      
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed Integration (product) (product) (product) (product)
Software under consideration Jenkins, Kafka, OpenVPN Terraform, Ansible ZooKeeper N/A

Farms' monitoring

For the purposes of this wikipage, the Farms' monitoring refers to those systems that monitor one or more Farms.
Authorized endeavors related to the Farms' monitoring
Progress Grafana (work) Zabbix (work) Nagios (work)
Business requirements      
Prototypes      
Stakeholder requirements      
Deliverable specifications      
Work specifications      
Certainty      
Utility      
Applicability      
Controllability      
Products to be developed (product) (product) (product)
Software under consideration Grafana Zabbix Nagios

Database management

For the purposes of this wikipage, database management refers to those endeavors that are related to databases of the Cloud.
Authorized endeavors related to database management
Работы MariaDB (work) PostgreSQL (work) Opplet (DBs) Ceph (work)
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed (product) (product) (product) (product)
Software under consideration MariaDB PostgeSQL Cassandra, MuleESB, Hadoop Ceph

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.
Authorized endeavors related to DNS management
Progress CDN DNSSEC Geocast IPv6 Revisions (DNS)
Business requirements          
Prototypes          
Stakeholder requirements          
Deliverable specifications          
Work specifications          
Certainty          
Utility          
Applicability          
Controllability          
Products to be developed (product) (product) (product) (product) (product)
Software under consideration N/A N/A N/A N/A N/A

Support 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.
Authorized endeavors related to support tools
Progress Panels Workspaces Nextcloud (work)
Business requirements      
Prototypes      
Stakeholder requirements      
Deliverable specifications      
Work specifications      
Certainty      
Utility      
Applicability      
Controllability      
Products to be developed (product) (product) (product)
Software under consideration VestaCP, Cachet Eclipse Nextcloud

Node clusters

For the purposes of this wikipage, node clusters 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 node clusters
Progress Bureau (farm) Campus (farm) Lab (farm) Opplet (farm)
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed (product) (product) (product) (product)
Software under consideration ProxmoxVE HAProxy OpenStack CloudStack

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:

  1. Services for CNM apps. Those federation services that Opplet provides to CNM apps.
  2. 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 Node clusters 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 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
Progress WSO2 IS (work) Enrollment IAM Mail (Cloud) Exams Warehouse
Business requirements            
Prototypes            
Stakeholder requirements            
Deliverable specifications            
Work specifications            
Certainty            
Utility            
Applicability            
Controllability            
Products to be developed (product) (product) (product) (product) (product) (product)
Software under consideration WSO2 IS Yii Yii N/A Yii N/A

User-oriented

For the purposes of this 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
Progress Interface (Opplet) Events (Opplet) Mailboxes (Opplet) Newsletters (Opplet) Calendar (Opplet) Registration
Business requirements            
Prototypes            
Stakeholder requirements            
Deliverable specifications            
Work specifications            
Certainty            
Utility            
Applicability            
Controllability            
Products to be developed (product) (product) (product) (product) (product) (product)
Software under consideration 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:

  1. 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.
  2. 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 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
Progress AVideo (work) WordPress (work) MediaWiki (work) HumHub (work) Moodle (work)
Business requirements          
Prototypes          
Stakeholder requirements          
Deliverable specifications          
Work specifications          
Certainty          
Utility          
Applicability          
Controllability          
Products to be developed (product) (product) (product) (product) (product)
Software under consideration AVideo WordPress MediaWiki HumHub Moodle

Utilizing non-MariaDB

For the purposes of this 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
Progress GitLab (work) SuiteCRM (work) Odoo (work) Jitsi (work)
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed (product) (product) (product) (product)
Software under consideration GitLab SuiteCRM Odoo Jitsi

Experimental

For the purposes of this 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
Progress OpenEdX (work) ProjecQtOr (work) Redmine (work) Taiga (work)
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed (product) (product) (product) (product)
Software under consideration OpenEdX ProjecQtOr Redmine Taiga

Enterprise

Venture administration

For the purposes of this wikipage, venture administration refers to human administration of the Cloud enterprise.
Authorized endeavors related to enterprise administration
Progress Personnel Agency Finance Legal
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed (product) (product) (product) (product)

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.
Authorized endeavors related to enterprise external operations
Progress Industry Developers Technologies (work) Help Desk (work) Operators (work)
Business requirements          
Prototypes          
Stakeholder requirements          
Deliverable specifications          
Work specifications          
Certainty          
Utility          
Applicability          
Controllability          
Products to be developed Industry (product) Developers (product) Technologies (product) Help Desk (product) Operators (product)

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.
Authorized endeavors related to stakeholder groups
Progress Councils (work) Committees (work) Users (work) Sysadmins (work)
Business requirements        
Prototypes        
Stakeholder requirements        
Deliverable specifications        
Work specifications        
Certainty        
Utility        
Applicability        
Controllability        
Products to be developed Councils (product) Committees (product) Users (product) Sysadmins (product)

Name yours

CNM Cloud integration that is based on exploring the possibilities of integrating the Cloud, such as using Jenkins and Kafka, and adding VPNs, such as integrating email services across the Farms.


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:
  • WSO2 IS for Opplet. New development of Opplet WSO2 IS to add WSO2 Identity Server (WSO2 IS) services to Opplet. Currently, Opplet utilizes OpenLDAP as its authorization and identity connector. However, OpenLDAP does not allow single sign-on (SSO) services. In addition, the Opplet developers faced troubles in changing roles and in connecting some end-user applications such as MediaWiki with OpenLDAP. Adding WSO2 IS also aims to introduce user registration in Opplet within CNM apps. Currently, the users must first register with Opplet in order to use those CNM app's services that are available for the registered users only. It is unclear at the moment whether OpenLDAP shall be kept in Opplet after WSO2 IS addition and, if so, how.
  • Enrollment to Opplet. New development of Opplet Enrollment to transfer the course registration (which Moodle in Australian way calls "enrolment") from CNM Cert to Opplet. Beyond visibility of user enrollment status on Opplet dashboard, this transfer shall resolve several problems: (a) speed. The current enrollment is carried out through the cron tool, which has a response delay, (b) enrollment in LMSes other than CNM Cert. The Cert accommodates only first 3 levels of the educational programs, (c) automatic unenrollment from those courses that have successfully been completed.
  • IAM to Opplet. Further development of Opplet IAM to (a) automatically add new federated Opplet roles based on the course progress and (b) communicate those roles to CNM apps. Currently, Opplet user roles can only be changed manually by Opplet administrators.
  • Mail for CNM Cloud. Further development of CNM Mail Server to make sure that all CNM apps can send and, when applicable, receive emails through it.
  • Exams to Opplet. New development of Opplet Exams to move test banks from CNM Moodle to Opplet.
  • Warehouse for CNM Cloud. New development of Opplet Warehouse to create a federated object storage in order to make illustrations and other files available for various CNM apps. The Cloud developers earlier also discussed an idea was to utilize CNM GitLab as a file storage.





Retrieved from "https://pravka.bskol.com/w/index.php?title=CNMCyber_Usable&oldid=77306"