CNMCyber Usable

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:

• Integration for CNM Farms. New development of 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.
• Configuration for CNM Farms. New development of CNM Cloud configuration that is based on exploring the possibilities of adding the ability to automatically create virtual machines, possibly using Terraform and Ansible.
• Statistics for CNM Farms. New development of CNM Cloud statistics that is based on exploring the possibilities of using ZooKeeper and log management.
• Revisions for CNM Farms. New development of CNM Cloud revisions that aim to build the system of periodic revisions of the Farms.

Authorized endeavors related to the Farms' administration

Progress	Integration	Configuration	Statistics	Revisions (farms)
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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:

• MariaDB for CNM Farms. Further development of CNM MariaDB to explore using additional tools such as MariaDB MaxScale and MariaDB xPand in the existing MariaDB cluster of the Cloud.
• PostgreSQL for CNM Farms. New development of CNM PostgreSQL to create a cluster of PostgeSQL databases of the Cloud. In general, linking similar databases with each other may make their functioning more stable.
• DBs for Opplet. Further development of Opplet DB to optimize existing databases of Opplet and to add new federated databases that can be shared by CNM apps. New databases, for instance, can manage the data of the customers to be taken from and shared with CNM Venture (built with CNM Odoo) and CNM Linkup (built with CNM SuiteCRM). Earlier, the Cloud developers discussed possibilities of using MongoDB or Apache Cassandra for data storage, MuleESB for data collection and Apache Hadoop for "formating".
• Ceph for CNM Farms. Further development of CNM Ceph to document and optimize it.

Authorized endeavors related to database management

Работы	MariaDB	PostgreSQL	Opplet (DBs)	Ceph
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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:

• CDN for CNM Farms. New development of CNM Farm CDN to explore building one or more content delivery networks (CDNs) at least for some of CNM apps.
• DNSSEC for CNM Farms. New development of CNM Farm DNSSEC to explore utilizing DNSSEC in the Cloud.
• Geocast for CNM Farms. New development of CNM Farm Geocast to explore adding Geocast or similar functionality to some part or parts of the Cloud.
• IPv6 for CNM Farms. Further development of CNM Farm IPv6 to explore migration of the Cloud's DNS, except for public access, to IPv6.
• Revisions for CNM DNS. New development of CNM DNS revisions that aim to build the system of periodic revisions of all the Cloud's DNS records.

Authorized endeavors related to DNS management

Progress	CDN	DNSSEC	Geocast	IPv6	Revisions (DNS)
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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.

• Panels for CNM Farms. New development of Panels in CNM Farms to explore adding control panels such as VestaCP, as well as status systems such as Cachet to the Cloud.
• Workspaces for CNM Cloud. New development of Workspaces in CNM Cloud to explore adding personal tools and development environments such as Eclipse to the Cloud.
• Nextcloud for CNM Cloud. New development of CNM Nextcloud to explore adding Nextcloud as a set of personal management tools to the Cloud.

Authorized endeavors related to support tools

Progress	Panels	Workspaces	Nextcloud
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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) 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.

• 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 CNM 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 CNM 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 CNM Lab Farm or Opplet Farm.

Authorized endeavors related to node clusters

Progress	Bureau (farm)	Campus (farm)	Lab (farm)	Opplet (farm)
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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.
• 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.

Authorized endeavors related to app-oriented Opplet

Progress	WSO2 IS	Enrollment	IAM	Mail (Cloud)	Exams	Warehouse
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
Utility
Applicability
Controllability

User-oriented

For the purposes of this wikipage, user-oriented Opplet refers to those services that Opplet provides to its end-users:

• Interface for Opplet. Further development of Opplet interface to improve its usability and graphic design.
• Events for Opplet. New development of Opplet Events to (a) organize events on the administrative side and (b) manage own participation on the end-user side in the Cloud.
• Mailboxes to Opplet. Further development of Opplet Mailboxes to accommodate its automatic creation, management, and cancelation in order to upgrade this feature from its minimum viable product (MVP) state up to the marketable one.
• Newsletters to Opplet. New development of Opplet Newsletters to add mailing list and subscription functionalities.
• Calendar for Opplet. New development of Opplet Calendar to add a federated calendar to Opplet.
• CNM Registration Project.

Authorized endeavors related to user-oriented Opplet

Progress	Interface (Opplet)	Events (Opplet)	Mailboxes (Opplet)	Newsletters (Opplet)	Calendar (Opplet)
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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 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.

• AVideo for CNM Cloud. Further development of CNM AVideo to upgrade this app from its minimum viable product (MVP) state up to the marketable one. Previously, several test videos were recorded and posted there, but their fate is currently unknown. At this moment, it is unclear where and how this app will be finally installed since its HA and storage solutions haven't been designed yet.
• WordPress for CNM Cloud. Further development of CNM WordPress to upgrade this app from its minimum viable product (MVP) state up to the marketable one. WordPress and MariaDB as its database management system are used under the hood of this app. Previously, the Cloud developers struggled with the viruses, so an effective anti-virus strategy must be found.
• MediaWiki for CNM Cloud. Further development of CNM MediaWiki to upgrade this app from its minimum viable product (MVP) state up to the marketable one. MediaWiki and MariaDB as its database management system are used under the hood of this app. For a few years, the stable version of MediaWiki has not been updated due to new versions' conflict with our LDAP plugin. However, a decision has been made to migrate the integration to WSO2 IS and it is not clear whether LDAP will remain necessary. Also periodically there are problems with pictures, which the Warehouse for CNM Cloud project shall address.
• HumHub for CNM Cloud. Further development of CNM HumHub to upgrade this app from its minimum viable product (MVP) state up to the marketable one. HumHub and MariaDB as its database management system are used under the hood of this app.
• Moodle for CNM Cloud. Further development of CNM Moodle to upgrade this app from its minimum viable product (MVP) state up to the marketable one. Moodle and MariaDB as its database management system are used under the hood of this app.

Authorized endeavors related to utilizing MariaDB apps

Progress	AVideo	WordPress	MediaWiki	HumHub	Moodle
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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:

• GitLab for CNM Cloud. Further development of CNM GitLab to upgrade this app from its minimum viable product (MVP) state up to the marketable one. GitLab and PostgreSQL as its database management system are used under the hood of this app. Initially, the Cloud developers utilized Redmine instead of GitLab; some projects haven't been moved yet. The Redmine instance shall be moved to CNM Lab Farm.
• SuiteCRM for CNM Cloud. Further development of CNM SuiteCRM to upgrade this app from its minimum viable product (MVP) state up to the marketable one. SuiteCRM and PostgreSQL as its database management system are used under the hood of this app.
• Odoo for CNM Cloud. Further development of CNM Odoo to upgrade this app from its minimum viable product (MVP) state up to the marketable one. Odoo and PostgreSQL as its database management system are used under the hood of this app. Its HR and recruiting modules are planned to be used as soon as possible.
• Jitsi for CNM Cloud. Further development of CNM Jitsi to upgrade this app from its minimum viable product (MVP) state up to the marketable one. Jitsi is used under the hood of this app. Its database management system is unknown. At this moment, it is unclear where and how this app will be finally installed since its HA and storage solutions haven't been designed yet.

Authorized endeavors related to utilizing non-MariaDB apps

Progress	GitLab	SuiteCRM	Odoo	Jitsi
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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.

• OpenEdX for CNM Cloud. New development of CNM OpenEdX to explore OpenEdX and evaluate it in comparison with Moodle. CNM Cert hosts only first three levels of WorldOpp program; other courses, including language courses, are planned to be done on the OpenEdX platform.
• ProjecQtOr for CNM Cloud. New development of CNM ProjecQtOr to explore ProjecQtOr and evaluate it in comparison with other project management software that is deployed in the Cloud.
• Redmine for CNM Cloud. Further development of CNM Redmine to keep Redmine in the Cloud as a legacy app.
• Taiga for CNM Cloud. New development of CNM Taiga to explore Taiga software and evaluate it in comparison with other project management software that is deployed in the Cloud.

Authorized endeavors related to experimental apps

Progress	OpenEdX	ProjecQtOr	Redmine	Taiga
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
Utility
Applicability
Controllability

Enterprise

Venture administration

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

• Personnel for CNM Cloud. Further development of CNM Cyber personnel to advance human resource management for those human resources that work on the Cloud.
• Agency for CNM Cloud. New development of CNM Cyber agency to build an organizational structure behind the Cloud.
• Finance for CNM Cloud. New development of CNM Cyber finance to build financial accounting, reporting, and management behind the Cloud.
• Legal for CNM Cloud. New development of CNM Cyber legal to build legal activities behind the Cloud.

Authorized endeavors related to enterprise administration

Progress	Personnel	Agency	Finance	Legal
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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 outside of the enterprise behind the Cloud.

• Industry for CNM Cloud. New development of CNM industry monitoring to build 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.
• Developers for CNM Cloud. New development of CNM developer relationships to administer relationships with the Cloud developers.
• Technologies for CNM Cloud. New development of CNM technology monitoring to build 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.
• Help Desk for CNM Cloud. New development of CNM Cloud help desk to build a help desk at the Cloud.
• Operators for CNM Cloud. New development of CNM operator relationships to administer relationships with the Cloud operators.

Authorized endeavors related to enterprise external operations

Progress	Industry	Developers	Technologies	Help Desk	Operators
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
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:

• Industry Councils for CNM Cloud. New development of CNM industry councils to build groups of professionals who work in the industries related to the Cloud.
• Professional Committees for CNM Cloud. New development of CNM professional committees to build groups of professionals who work in the positions related to the Cloud.
• Users for CNM Cloud. New development of CNM User Group to build groups of end-users of the Cloud to discuss its challenges and possible solutions.
• Sysadmins for CNM Cloud. New development of Society of Sysadmins to build a group of system administrators.

Authorized endeavors related to stakeholder groups

Progress	Councils	Committees	Users	Sysadmins
Business requirements
Prototypes
Stakeholder requirements
Deliverable specifications
Project specifications
Certainty
Utility
Applicability
Controllability