Difference between revisions of "CNMCyber Usable"

From CNM Wiki
Jump to: navigation, search
(Venture administration)
(Venture administration)
Line 439: Line 439:
 
==Enterprise==
 
==Enterprise==
 
===Venture administration===
 
===Venture administration===
: For the purposes of this wikipage, ''venture administration'' refers to administration of the ''Cloud'' enterprise.
+
: For the purposes of this wikipage, ''venture administration'' refers to human administration of the ''Cloud'' enterprise.
 
:*'''[[Personnel for CNM Cloud]]'''. Further development of [[CNM Cloud Personnel]] to explore in the ''Cloud''.
 
:*'''[[Personnel for CNM Cloud]]'''. Further development of [[CNM Cloud Personnel]] to explore in the ''Cloud''.
  

Revision as of 15:40, 15 November 2022

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
Endeavors Integration Configuration Statistics Revisions
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

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 PostgreSQL Opplet (DBs) Ceph
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

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
Endeavors CDN DNSSEC Geocast IPv6 Ревизия DNS
Business requirements          
Product prototypes          
User requirements          
Work requirements          
Technical requirements          
Endeavor consent          
Utility          
Applicability          
Controllability          

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
Endeavors Panels Workspaces Nextcloud
Business requirements      
Product prototypes      
User requirements      
Work requirements      
Technical requirements      
Endeavor consent      
Utility      
Applicability      
Controllability      

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) 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.
  • Farm for Bureau. Further development of CNM Bureau Farm to advance its features. Currently, this Farm is based on two bare-metal servers. This Farm also utilizes a portion of one bare-metal server that belongs to the Lab Farm. 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.
  • Farm for Campus. Further development of CNM Campus Farm to advance its features. Currently, this Farm is based on three virtual private servers (VPSes), which databases are synchronized via MariaDB Galera, and high availability functionality is based on HAProxy and includes (a) entry point, (b) monitoring, (c) security, and (d) backup and recovery system. One of the servers is also connected to additional storage, which is supposed to be converted to NAS.
  • Farm for Lab. Further development of CNM Lab Farm to advance its features. Currently, this Farm is based on one bare-metal server. This Farm requires no high availability functionality due to the experimental nature of the applications installed on it. Due to the lack of high availability requirement, this farm will require an advanced backup and recovery system.
  • Farm for Opplet. Further development of Opplet Farm to advance its features. Currently, this Farm is based on two virtual private servers (VPSes); however, they haven't been included in one network. It is expected that a few developments of Campus Farm will be used here.
Previously, a private cloud built on OpenStack was used. It was closed due to high cost and low workload at the time. The development of the project may require the transfer of some of the Farms resources to the cloud solution again. Recently, Apache CloudStack has also become popular. If such a decision is made, it will be necessary to decide which support package to use and whether it will be the development of Lab Farm or Opplet Farm.
Authorized endeavors related to node clusters
Endeavors Bureau (farm) Campus (farm) Lab (farm) Opplet (farm)
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

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 that are utilized or can be used on several rather than one individual Farm:
  • 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.
  • Roles to Opplet. Further development of Opplet roles to (a) automatically add new federated roles of an Opplet user 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.
Authorized endeavors related to app-oriented Opplet
Endeavors WSO2 IS Enrollment Roles Mail (Cloud) Exams Warehouse
Business requirements            
Product prototypes            
User requirements            
Work requirements            
Technical requirements            
Endeavor consent            
Utility            
Applicability            
Controllability            

User-oriented

For the purposes of this wikipage, user-oriented Opplet refers to those endeavors that are utilized or can be used on several rather than one individual Farm:
Authorized endeavors related to user-oriented Opplet
Endeavors Interface (Opplet) Events (Opplet) Mailboxes (Opplet) Newsletters (Opplet) Calendar (Opplet)
Business requirements          
Product prototypes          
User requirements          
Work requirements          
Technical requirements          
Endeavor consent          
Utility          
Applicability          
Controllability          

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 CNM 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
Endeavors AVideo WordPress MediaWiki HumHub Moodle
Business requirements          
Product prototypes          
User requirements          
Work requirements          
Technical requirements          
Endeavor consent          
Utility          
Applicability          
Controllability          

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
Endeavors GitLab SuiteCRM Odoo Jitsi
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

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
Endeavors OpenEdX ProjecQtOr Redmine Taiga
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

Enterprise

Venture administration

For the purposes of this wikipage, venture administration refers to human administration of the Cloud enterprise.


Cloud Human Resources -- building Cloud Human Resources, Human Resources, and practices to serve existing staff.

-- построение Кадров Облака, отдела кадров и практик по обслуживанию существующего персонала.
    Organization for the Cloud -- building the Cloud Organization, the structure of the organization behind the Cloud.
-- построение Организации Облака, структуры организации стоящей за the Cloud.
     -- building Bskol Finance, financial accounting and reporting, and financial management.
-- построение Финансов Bskol, финансового учёта и отчётности, а также управления финансами.
     -- building the Legal aspects of the Cloud, legalizing the activities of the Cloud.
-- построение Юридических аспектов Облака, юридического оформления деятельности Облака.
Authorized endeavors related to enterprise administration
Endeavors Кадровое Организационное Финансовое Юридическое
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

External operations

For the purposes of this wikipage, enterprise external operations refer to those endeavors that are utilized or can be used on several rather than one individual Farm:


Industry for the Cloud -- building the Cloud Industry Tracker, a system to collect data on the Cloud's industries, their news and trends, examine that data, compare the Cloud's organization to general trends, and propose changes to the Cloud.

-- построение Слежения за индустрией Облака, системы по сбору данных об индустриях the Cloud, их новостях и тенденциях, изучению этих данных, сравнение организации работы с the Cloud с общими тенденциями и выработки предложений по измемениям в работе с the Cloud.
   Developers for the Cloud -- building Work with Cloud developers.
-- построение Работы с разработчиками Облака.
   Technologies for the Cloud -- building the Cloud Technology Tracker, a system to collect data on technologies in the Cloud markets, their news and trends, study this data, compare the Cloud's offerings with those of competitors, and generate proposals for changes to the Cloud.
-- построение Слежения за технологиями Облака, системы по сбору данных о технологиях на рынках the Cloud, их новостях и тенденциях, изучению этих данных, сравнение предложений the Cloud с предложениями конкурентов и выработки предложений по измемениям в the Cloud.
   Help Desk for the Cloud -- Building a Cloud Help Desk
-- построение Службы техподдержки Облака
   Cloud Operators -- Building Work with Cloud Operators.
-- построение Работы с эксплуатационщиками Облака.
Authorized endeavors related to enterprise external operations
Endeavors Индустрия Разработчики Технологии Техподдержка Эксплуатационщики
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

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:

Committees for the Cloud -- Building Cloud-Valued Committees

-- построение Ценных Облаку комитетов
    Tips for the Cloud -- Building Cloud-Value Tips
-- построение Ценных Облаку советов
    Cloud Users - Building Cloud User Groups
-- построение Групп пользователей Облака
    SysAdmins for the Cloud -- Building a Community of Sysadmins‎.
-- построение Сообщества Сисадминов‎.
Authorized endeavors related to stakeholder groups
Endeavors Комитеты Советы Пользователи Сисадмины
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

Name yours