Date: Fri, 9 Apr 1999 11:06:37 +0400 (MSD) From: pavel@ikar.elect.ru To: www@freebsd.org Subject: Created distributed fault-tolerance managment system (ROSKU) Message-ID: <199904090706.LAA00519@ikar.elect.ru>
next in thread | raw e-mail | index | archive | help
Hi, You'll see below some information about our product: ******************** *SIMPLE INFORMATION* ******************** Program environment: -------------------- FreeBSD 2.2.5 jdk-1.1.5 for FreeBSD Minimal hardware requirements: ------------------------------ i486 or higher 16 MB RAM 300 MB HDD (with FreeBSD 2.2.5) any SVGA adapter NE2000 NIC ****************** *MORE INFORMATION* ****************** Moskovskay st. 81 350072 Krasnodar RUSSIA ph: (8612) 579-207, 579-172 fax: (8612) 579-172 www: http://ikar.elect.ru e-mail: rosku@ikar.elect.ru Special Design Bureau "Ikar" ROSKU (Distributed, Fault-tolerance System of Control and Management) System Preview CONTENTS This is a translation of original version of documentation. 1. TERMS AND CONDITIONS 2. ROSKU CONCEPTION 3. SYSTEM PRIMARY PROPERTIES 3.1. FUNCTIONING ENVIRONMENT 3.1.1. System presentation levels 3.1.2. Functional properties 4. OM LANGUAGE 5. DEVELOPMENT ENVIRONMENT 6. CMS CREATION 7. USAGE AREA 8. CERTIFICATION FOR USAGE IN SYSTEMS OF SPECIAL ASSIGNMENT 9. SYSTEM REQUIREMENTS 1. Terms and conditions ROSKU - universal software, which provides to developer possibility to create scaleable, fault-tolerance, real time, control and management systems (CMS) based on standard PC. Control and Management Systems - software, intends for salvation problems of control and management; this package allows to project properly and to describe management system's input and output alphabets, contain data streams management mechanism, data saving mechanism, allows to define input signals and data conversion to output signals rules, to create CMS operator interfaces. Distributed CMS - non symmetrical function on several, united to unified computing complex, PCs CMS. In this case any tow of them don't repeat same calculations and at the same time solve different management subfunctions. For PCs unite to unified computing complex, using standard TCP/IP family network protocols and specialized packet network interface. For complex creation can be used different instrumental configurations - both network and other communication technologies, for example parallel and consistent ports, modems and telephone lines. Distributed, Fault-tolerance CMS - distributed CMS, which able to continue function in case of any complex included PCs has failure. System is continuing to work on remain PCs without brake and data lost. Automated, Distributed, Fault-tolerance CMS - management system, allow, in contrast to automatic (fully autonomous), including in MS an operator (one or any). (Package allow to create an automatic CMS - without operator's interface.) Adaptable, Distribution, Fault-tolerance CMS - system tuning mechanism included CMS both on development phase and on functioning phase. Tuning mechanisms allow to take into account a peculiarity of subject area, CMS gear configuration, solved by system of problems. 2. ROSKU conception ROSKU - universal technology, realized in software package, which provides to developer possibility to create scaleable, fault-tolerance, real time, control and management systems based on standard PC. ROSKU consist development and functioning environment. ROSKU Integrated development environment provides full cycle of CMS developing and debugging, functioning environment - effective and stable work of the distributed CMS. The package has been realized by using two program language - C++ and Java, but it is unified software. Some elements of it is a stand-alone applications, some can be used with each other only. All elements written on C++ are working under the OS FreeBSD UNIX 2.2.6, but can be carry over to the any other POSIXI, POSIX1.b and POSIXI.c supported OS. All systems, written on inter-platform language Java, can functionate under any Java (1.1.5 or higher) supported OS without any changes. The package contains *: * Special library of non visual modules on C++ (system, in fact) * Special library of visual modules on C++ (allow to create operator's interface) * OM Language Implementor (Units Description macro language) (Java) * Development Environment contains: multi-window editor, project inspector, OM language debugger, system emulator (for develop without system loading), device emulator (for develop without managing devices attaching). (Java) * Some useful tools * The program specialized network interface (C++ for FreeBSD) * - items in list can be changed (the package is under the development) 3. System primary properties 3.1. Functioning environment 3.1.1. System presentation levels The physical levels are presented: 1. By the functioning environment (by communication area) 2. By the procedure nods 3. By the connection points to the managing object The communication area - physical environment, data is transferring through in the system plus low-level transfer protocol. The example of communication area is Ethernet network with TCP/IP family protocols. The procedure nodes - the elements of the computing complex, which placed in one communication area, and united in to the unified system by a special package's network protocol (interface). The procedures nodes is a PCs in our case. The connection point to the managing object - it is a physical device, which managing device directly connected to. The connection point can be a port, controller or connection block. Interaction between connection point and procedure nodes must take place through the package network protocol and communication area, it's important. For example the connection point is connection block based on one-board PC. The connection point can be a part of the procedure node (if connection point is a standard port of a PC, for example), but in this case, after the failure of the procedure node access to the managing device would be lost. But it doesn't call any errors and faults in the system. Logical levels: 1. Management system (software) 2. Message 3. Unit 4. Link 5. Data (data segment) Management system - it is a software, written by this package using, installed on required number of procedure nodes and fully ready to work. The system elements of management can be any programs (system and applied), data segment and a group of special objects (gateways, identifiers system tables and etc.). Message - it is an element of MS, existed while system work only. The message mechanism - primary facility of transaction realization between different elements of MS. Messages are dynamical created segments of data or network packets, which has been transferring through communication area, in different phase of existence. Through the communication area, while system working, except messages generated by code, which has been written a programmer, can be transferring other system messages also. For example, all data transactions are transformed to message list. Units - it is logically detached elements of MS, which solving one or more subtasks of management. Unit code is written on units description macro language (OM). Subquantitys of input and output alphabet of MS and conversion input to output messages rules are described in the unit. Facilities of data working are defined in OM language. The unit can interact not only with managing devices, but also with other units. The management system must contain not less one unit, but not more 255. Each working unit is a stand-alone program (in OS UNIX term - process); for more effective work of the system sometimes one unit is become a several parallel processes, but it is hidden for programmer. Link - two or more units, which organize unified subsystem. For united some units to link, it should be written in text of each unit, what units it link. The link of units - it is a one multitask program. Any unit can be included in several links or can be included in no one. The link mechanism bring in system both for more comfortable system structuring and for possibility effective management of dynamic reconfiguring. Data (data segment) - it is a quantity of the scalar or vector variables defined in the system. All variables, which had been included in the data segment are global defined variables, it's mean that they accessible to read and write from any unit or node. The access to data from the units is realize with help of special facilities OM language. 3.1.2. Functional properties The ROSKU allowed: * to create any quantity operator's workplaces consisting of CMS * to include in CMS any quantity of PCs * to organize differentiation of user's access right to elements of management * to keep and to transmit data between CMS PCs in closed (coded) form * to view current data as tables * to organize interaction between any CMSs * to make dynamical reconfiguration of CMS structure, while system is working The software based on ROSKU are using principles of open systems and providing: * possibility of making changes interdependency and raising of the rate of software without vital changes existing software, special software and software of information base directing * protection from unauthorized access to the system * CMS process compatibility of coding, addressing methods and messages format * functional fullness and scaleable of CMS * the ROSKU based on open multitask operation system, which providing local network and internetwork interaction management * the ROSKU is providing to build software of build in management blocks (connection blocks), which providing both problem of official interaction with managing devices and interaction with CMS. 4. OM language Hi-level unit description macro language (OM) was developed for CMS development consist of units writing on this language. OM language at development phase is translating to Java for later interpretation in development environment and to C++ for end-using in ROSKU by OM Implementor. All units written on OM language are using finite automation technology. All units have table of finite states, table of processing procedures calls, list of input and output messages and list of macro variables (variables which can be accessed from any unit). Units interact with each other by messages. Depending on received messages and current state of the unit, processing procedure executing. Current state is changing and messages sending for other units from processing procedures. 5. Development environment The Development environment provides: * to develop and to debug on several workplaces at the same time * visual development of system interface * to debug system before the real managing devices will be connected - device data steam emulation is realized by environment * to generate CMS as a package executable units on C++ * to generate own libraries of the data processing algorithms * automatic controlling of the creating system's parameters on development phase The package conception based on unit distribution architecture. Units - functionally ended elements of CMS, which interacted between one another by data exchanging. Hi-level unit description macro language (OM) using for CMS creation, which optimized for management system development. Facility of interface creation are presented in environment. Interface flexibility allow to manage it from the system units. Tuning mechanisms allow to make changes in interface without recompiling system already built, what provides to minimize quantity of possible errors at development phase. ROSKU emulator and debugger are built in the environment, that provides full debugging of the developing system. Managing device emulator are also built in the environment, that provide to debug system without device connection. 6. CMS creation All facilities needed for CMS developer united into Integrated Development Environment. Creation of MS is beginning from units writing on OM language. After unit have been created, the debugging phase is beginning. Development environment emulate system and not connected devices, developer also can control messages received by units and send any to them. When system fully tested and debugging it translating to C++ and compiling to executable files. Ready for use system installing to PC where ROSKU main functional part is placed. After system execute on each of the procedure nodes several special processes begin to work, mutually recognizable each other, which determine current topology of complex and formed corresponding tables on the nodes. After this units of CMS is running. System determine automatically and dynamically, depending on current node utilization, where each unit will be running (on which node). After units is loaded the system begin to work in regular mode. If one or any of procedure nodes are fault the system change state to special mode "recovery after fault". State change does not visible for units and happen without interrupt. While system is functioning connection of new procedure nodes is allowed. 7. Usage area ROSKU usage for special assignment system of control and management projecting and developing. It provides possibility of CMS projecting in accordance with demands of subject area (for example problem connection organizing), as totally realized solutions for capacities, allocation and forms of information organization (data and algorithms), which acted, kept and processed by CMS while it functioning. This development package provides to developer all mechanisms needed for creation management system. ROSKU was projected for usage in connection and management systems of different level mobile connection points. Universality, effectiveness and simplicity of the system provides use it in automated systems of technology processes management and controlling and monitoring systems. 8. Certification for usage in systems of special assignment Majority of software certification methods for usage in systems of special assignment based on source code analyzing, providing to make the reliable conclusion about absence "bookmarks" and algorithm correctness. * ROSKU based on kernel OS UNIX FreeBSD 2.2.5, source code of it placed at developers and opened for certification * ROSKU can be adapted for any certificated, standard POSIX supported OS * Not accessible source codes weren't used in developing In this way, authors of software have all needed for successful certification of the software. 9. System requirements Personal Computer: 486 or higher, 8 or higher Mb of RAM, 50 Mb free disk space - for system, 486 (Pentium recommended) or higher, 16 (32 recommended) Mb of RAM, 50 Mb free disk space - for Development Environment. Operation System: Unix FreeBSD or other POSIX standard supported Unix OS - for system, any JDK 1.1.5 supported OS - for Development Environment. 2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904090706.LAA00519>