Difference between revisions of "CNMCyber Usable"

From CNM Wiki
Jump to: navigation, search
(App-oriented)
(App-oriented)
Line 237: Line 237:
  
 
  -- добавление функции автоматического изменения ролей [[Оплёт]]а в зависимости от завершения курсов и определённых элементов курсов на [[Брацка Учебка|Учебке]]. В данный момент, роли в [[Оплёт]]е изменяются только администраторами вручную.
 
  -- добавление функции автоматического изменения ролей [[Оплёт]]а в зависимости от завершения курсов и определённых элементов курсов на [[Брацка Учебка|Учебке]]. В данный момент, роли в [[Оплёт]]е изменяются только администраторами вручную.
 +
 +
:*'''[[Mail Server for CNM]]'''. Further development of [[CNM Mail Server]] to explore in the ''Cloud''.
 +
    Oplet mail aggregator -- federation of separate mail agents of various applications.
 +
-- федерализация отдельных почтовых агентов различных приложений.
 +
 
:*'''[[Storage for Opplet]]'''. New development of [[Opplet Storage]] to explore in the ''Cloud''.
 
:*'''[[Storage for Opplet]]'''. New development of [[Opplet Storage]] to explore in the ''Cloud''.
  

Revision as of 23:08, 13 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.

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:
  • Bureau Farm Works. Further development of 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.
  • Campus Farm Works. Further development of 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.
  • Lab Farm Works. Further development of 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.
  • Opplet Farm Works. 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 Над Деловой Над Кампусной Над Опытной Над Оплётной
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 Opplet Farm Works project (section Node clusters of this very wikipage) and DBs for Opplet project (section Database management).

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:
-- перевод регистрации на курсы участников Bskol из Учебки в Оплёт. Регистрация на курсы в Учебке сегодня осуществляется через инструмент cron, который имеет задержку срабатывания. Однако главная проблема, которую надо решить, -- это регистрация участников в учебных системах, которые отличаются от Учебки.
-- добавление приладам функции регистрации пользователей в Оплёте. В данный момент, пользователь должен предварительно зарегистрироваться в Оплёте для того, чтобы пользоваться продвинутыми услугами прилад.
-- добавление функции автоматического изменения ролей Оплёта в зависимости от завершения курсов и определённых элементов курсов на Учебке. В данный момент, роли в Оплёте изменяются только администраторами вручную.
   Oplet mail aggregator -- federation of separate mail agents of various applications.
-- федерализация отдельных почтовых агентов различных приложений.
-- добавление федеративных баз данных и хранилищ в Оплёт и синхронизация хранения данных по всему the Cloud. Прежде всего, эта федерация касается данных клиентов для Справы и Связки. Ранее, обсуждалась возможность использования MongoDB для хранения данных, MuleESB для их сбора и Apache Hadoop для "причёсывания". В дополнение, шёл разговор об включении будущего вики-склада для хранения картинок используемых в Брацкой Правке в Оплёт. Ещё одной идеей было задействование Брацкой Крынки в хранении файлов.
-- перенос блока банка вопросов из Учебки в Оплёт.
   Registration of Oplet for courses - transfer of registration for courses of Bskol participants from Uchebka to Oplet. Registration for courses in Uchebka today is carried out through the cron tool, which has a response delay. However, the main problem to be solved is the registration of participants in training systems that are different from Training.
   Registration of Oplet in Appliances -- adding the function of registering users in Oplet to attachments. At the moment, the user must first register with Opleta in order to use the advanced add-on services.
   Opleth Roles -- Adding a feature to automatically change Opleth roles based on completion of courses and certain elements of Courses in Training. At the moment, roles in the Opleth are only changed manually by administrators.
   Oplet Warehouses -- Add federated databases and storage to Opleth and sync data storage across the Cloud. First of all, this federation concerns the data of the clients for the Right and the Bundle. Earlier, the possibility of using MongoDB for data storage, MuleESB for data collection and Apache Hadoop for "combing" was discussed. In addition, there was talk of including a future wiki store for storing pictures used in Bratskaya Edit in Oplet. Another idea was to involve Bratska Krynka in file storage.
   Oplet test aggregator -- transfer of the block of the bank of questions from Uchebka to Oplet.
Authorized endeavors related to app-oriented Opplet
Endeavors Идентификация Курсы Почтовый агрегатор Регистрация Роли Склады Тесты
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:
-- обновление интерфейса opplet.net до лучше выглядещего и более удобного для пользователей.
-- добавление функции управления участия в мероприятиях организованных в рамках проекта Bskol.
-- добавление функции подписки на рассылки и отписки от них.

Opplet Interface -- Updated the opplet.net interface to look better and be more user friendly.

    Oplet Events -- adding the function of managing participation in events organized within the framework of the Bskol project.
    Corporate mail -- bringing the services of the Oplet mail from a minimally viable product to a finished product.
    Oplet's Mailing Lists -- adding the function of subscribing to mailing lists and unsubscribing from them.
Authorized endeavors related to user-oriented Opplet
Endeavors Интерфейс Мероприятия Оплёта Почта корпоративная Рассылки
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        

Apps

Усилия по построению пользовательских приложений, которые включены в существующую и могут потенциально быть включены в технологию перспективную. Для всех, надо:

  1. Обновлять все приложения до последних стабильных версий и устанавливать свежие патчи, если и когда они появляются в наличии. Основное требование для любого приложения -- привязка к нашему WSO2 Identity Server (WSO2 IS). Дополнительное требование для любого приложения -- привязка к нашему OpenLDAP.
  2. Документировать то, что у нас есть, и выявлять проблемы.

Efforts to build custom applications that are included in existing and could potentially be included in future technology. For everyone, you need:

    Update all applications to the latest stable versions and install the latest patches if and when they become available. The basic requirement for any application is to be connected to our WSO2 Identity Server (WSO2 IS). An additional requirement for any application is to bind to our OpenLDAP.
    Document what we have and identify problems.

Utilizing MariaDB

For the purposes of this wikipage, utilizing MariaDB apps refer to those endeavors that are utilized or can be used on several rather than one individual Farm:
Пять полных прилад the Cloud используют MariaDB в качестве своих баз данных:
для разработок Брацкой Бачки, её курсовой и будущей версии, а также ПО. В настоящее время, основная прилада установлена, но не используется. Ранее, туда были записаны несколько пробных видео, их судьба в данный момент не известна. Основная прилада, скорее всего, не будет установлена на главном кластере Кампусной Фермы из-за особенностей добавки функционала высокой доступности. Нет решения где и как она будет окончательно установлена.
для разработок Брацкой Вебки, её курсовой и будущей версии, а также ПО. В настоящее время, установленных прилад нет. Предпринималось несколько попыток установки, однако эффективной стратегии борьбы с вирусами найдено не было.
для разработок Брацкой Правки, её курсовой и будущей версии, а также ПО. В настоящее время, основная прилада установлена и активно используется. Из-за проблем интеграции с LDAP, версии уже несколько лет не обновляются. Также периодически появляются проблемы с картинками. Почтовый агент либо не подключен, либо не работает.
для разработок Брацкой Сетки, её курсовой и будущей версии, а также ПО. В настоящее время, основная прилада установлена, но используется несистематически. Почтовый агент либо не подключен, либо не работает.
для разработок Брацкой Учебки, её курсовой и будущей версии, а также ПО. В настоящее время, основная прилада установлена и активно используется. Несколько проблем задокументировано на странице Работа над Учебками. Почтовый агент либо не подключен, либо не работает.

Working on Tanks for the development of Bratskaya Tank, its course and future version, as well as software. Currently, the main attachment is installed but not in use. Previously, several test videos were recorded there, their fate is currently unknown. The main attachment will most likely not be installed on the Campus Farm's main cluster due to the nature of adding high availability functionality. There is no decision where and how it will be finally installed.

   Working on Webcams for the development of the Bratsk Webcam, its course and future version, as well as software. There are currently no attachments installed. Several installation attempts have been made, but no effective anti-virus strategy has been found.
   Work on Edits for the development of Bratskaya Edit, its course and future version, as well as software. Currently, the main attachment is installed and actively used. Due to integration issues with LDAP, the versions have not been updated for several years. Also periodically there are problems with pictures. The mail agent is either not connected or not working.
   Work on Grids for the development of the Bratskaya Grid, its course and future version, as well as software. Currently, the main attachment is installed, but is not used systematically. The mail agent is either not connected or not working.
   Work on training manuals for the development of the Bratskaya training manual, its course and future versions, as well as software. Currently, the main attachment is installed and actively used. Several issues are documented on the Working on Tutorials page. The mail agent is either not connected or not working.
Authorized endeavors related to utilizing MariaDB apps
Endeavors Бачки Вебки Правки Сетки Учебки
Business requirements        
Product prototypes        
User requirements        
Work requirements        
Technical requirements        
Endeavor consent        
Utility        
Applicability        
Controllability        
Так как приложения существуют не в вакууме, часть усилий по развитию приложений относится к другим группам. Например, к:

Because apps don't exist in a vacuum, part of the app development effort goes to other groups. For example, to:

    Domain projects include CDN in the Cloud.
    Pilot projects include LDAP for Editing.

Utilizing non-MariaDB

For the purposes of this wikipage, utilizing non-MariaDB apps refer to those endeavors that are utilized or can be used on several rather than one individual Farm:
для разработок Брацкой Крынки, её курсовой и будущей версии, а также ПО. Окончательный перевод Крынки с Redmine на GitLab. В настоящее время, GitLab стоит и несистематически используется, хотя и не на верном веб-адресе. База данных -- PostgreSQL. Тот Redmine, который использовался для Крынки, надо перевести на Опытно Облако.
для разработок Брацкой Связки, её курсовой и будущей версии, а также ПО. В настоящее время, не используется вообще. База данных -- PostgreSQL.
для разработок Брацкой Справы, её курсовой и будущей версии, а также ПО. В настоящее время, не используется, но есть планы переводить туда отдел кадров и рекрутирование. База данных -- PostgreSQL.
для разработок Брацких Жиц, её курсовой и будущей версии, а также ПО. Построение кластера для высокой доступности Брацких Жиц. Основная прилада стоит и, в настоящее время, предпринимаются попытки её использования. База данных неизвестна.

Translation of Krynka to GitLab for the development of Bratska Krynka, its course and future version, as well as software. Final transfer of Krynka from Redmine to GitLab. Currently, GitLab stands and is inconsistently used, although not at the correct web address. The database is PostgreSQL. The Redmine that was used for Krynka should be transferred to Experimental Cloud.

   Work on Bundles for the development of Bratskaya Bundle, its course and future version, as well as software. Currently not used at all. The database is PostgreSQL.
   Work on the Rights for the development of Bratskoy Prava, its course and future versions, as well as software. Currently not in use, but there are plans to move the HR and recruiting department there. The database is PostgreSQL.
   Sustainability for Zhytsi for the development of Bratsky Zhytsi, its course and future version, as well as software. Building a cluster for high availability Bratsky Zhytsy. The main attachment is standing and, at present, attempts are being made to use it. The database is unknown.
Authorized endeavors related to utilizing non-MariaDB apps
Endeavors Крынки Связки Справы Жици
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 those endeavors that are utilized or can be used on several rather than one individual Farm:
Усилия по построению перспективных и популярных ресурсов the Cloud:
-- уже много лет, стабильная версия MediaWiki не обновляется из-за конфликта новых версий с нашим плагином LDAP. Однако принято решение о переводе интеграции на WSO2 IS и не ясно, будет ли оставлен LDAP в качестве обязательного.
  • OpenEdX. Further development of v to explore in the Cloud.
-- Moodle решено оставить исключительно под три начальных курса Лестницы к Профессии. Другие курсы, включая языковые, планируется делать на платформе OpenEdX.
  • ProjecQtOr. Further development of v to explore in the Cloud.
-- некогда был установлен для коротких тренингов по ПО для управления проектами.
  • Redmine. Further development of v to explore in the Cloud.
-- некогда использовался для Крынки, сейчас рассматривается возможность оставить для тренинга или в качестве "музейного" экспоната.
  • Taiga. Further development of v to explore in the Cloud.
-- некогда был установлен для коротких тренингов по ПО для управления проектами.

MediaWiki LDAP -- For many years now, the stable version of MediaWiki has not been updated due to a new version conflict with our LDAP plugin. However, a decision has been made to migrate the integration to WSO2 IS and it is not clear if LDAP will remain mandatory.

   OpenEdX -- Moodle decided to leave exclusively under the three initial courses of the Ladder to the Profession. Other courses, including language courses, are planned to be done on the OpenEdX platform.
   ProjecQtOr -- was once installed for short training sessions on project management software.
   Redmine - once used for Krynka, now considering the possibility of leaving it for training or as a "museum" exhibit.
   Taiga -- was once installed for short training sessions on project management software.
Authorized endeavors related to experimental apps
Endeavors MediaWiki LDAP 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 those endeavors that are utilized or can be used on several rather than one individual Farm:
-- построение Кадров Облака, отдела кадров и практик по обслуживанию существующего персонала.
-- построение Организации Облака, структуры организации стоящей за the Cloud.
-- построение Финансов Bskol, финансового учёта и отчётности, а также управления финансами.
-- построение Юридических аспектов Облака, юридического оформления деятельности Облака.

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.
    Finance for the Cloud -- building Bskol Finance, financial accounting and reporting, and financial management.
    Legal for the Cloud -- 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:
-- построение Слежения за индустрией Облака, системы по сбору данных об индустриях the Cloud, их новостях и тенденциях, изучению этих данных, сравнение организации работы с the Cloud с общими тенденциями и выработки предложений по измемениям в работе с the Cloud.
-- построение Работы с разработчиками Облака.
-- построение Слежения за технологиями Облака, системы по сбору данных о технологиях на рынках the Cloud, их новостях и тенденциях, изучению этих данных, сравнение предложений the Cloud с предложениями конкурентов и выработки предложений по измемениям в the Cloud.
-- построение Службы техподдержки Облака
-- построение Работы с эксплуатационщиками Облака.

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.

   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.
   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