| 1 | |
|---|
| 2 | The OpenGnsys Project README |
|---|
| 3 | ================================ |
|---|
| 4 | |
|---|
| 5 | OpenGnsys (pronounced Open Genesis) is based on a modular architecture separated in different service layers which allows its implementation in several educational and organizational IT environments, both in a centralized or distributed way. The main system management is carried out by means of a simple web interface which supports delegated administration. OpenGnsys is also suitable for isolated environments, being able to work under network failure conditions (offline mode). |
|---|
| 6 | |
|---|
| 7 | |
|---|
| 8 | Architecture |
|---|
| 9 | ------------ |
|---|
| 10 | |
|---|
| 11 | From the point of view of clients, OpenGnsys Project is constituted by a set of separate modules in different layers of services. |
|---|
| 12 | |
|---|
| 13 | * The bottom layer is responsible for direct access to client devices and motor functions of cloning. |
|---|
| 14 | * An intermediate layer consisting of a set of tools to perform complex tasks and environment customization. |
|---|
| 15 | * Management module consists of a simple and intuitive web interface that allows common tasks to manage software distribution to clients. |
|---|
| 16 | |
|---|
| 17 | Overall, OpenGnsys is a modular system that integrates a set of interrelated components and can be adapted to a variety of work settings possible. These components consist of standard services (file servers, web, database, DHCP, PXE, ...) and custom-developed tools for the project (cloning engine, console web, browser ad hoc, management demons repository and server, ...) which in combination offer everything OpenGnsys system. |
|---|
| 18 | |
|---|
| 19 | * OpenGnsys Server |
|---|
| 20 | Basic service cloning system (DHCP, NFS/Samba, PXE, database, etc..) Necessary for the boot process and initial configuration of the clients. |
|---|
| 21 | |
|---|
| 22 | * OpenGnsys Administrator |
|---|
| 23 | Centralized management web console (web pages, web services, etc.) with support for delegated administration, allowing control of all system components. |
|---|
| 24 | |
|---|
| 25 | * OpenGnsys Repository Manager |
|---|
| 26 | Manager repository of images for each of the administrative units defined in the module OpenGnSys Administrator. There may be one or more modules depending on the model of the organization defined. |
|---|
| 27 | |
|---|
| 28 | * OpenGnsys Client Agent |
|---|
| 29 | Executing agent of orders in the client, which integrates the following features: |
|---|
| 30 | - Graphical interface to select options predefined by the administrator. |
|---|
| 31 | - Interactive execution of Cloning Engine functions in administrator mode. |
|---|
| 32 | - Execution of the tasks sent from the OpenGnSys Administrator module. |
|---|
| 33 | |
|---|
| 34 | * OpenGnsys Clonning Engine |
|---|
| 35 | Motor function libraries cloning, installation and startup of the client operating systems. |
|---|
| 36 | |
|---|
| 37 | * OpenGnsys Installer |
|---|
| 38 | Software installation, upgrade and removal system which includes the settings generator, the clients boot generator, the component package builder, etc. |
|---|
| 39 | |
|---|
| 40 | |
|---|
| 41 | Scenarios |
|---|
| 42 | --------- |
|---|
| 43 | |
|---|
| 44 | OpenGnsys is a modular system that can be used in different scenarios within an Institution, both educational and organizational. |
|---|
| 45 | |
|---|
| 46 | * Educational Scenarios: OpenGnsys can lend support to some of the educational settings defined by the Working Group-Net Teaching RedIRIS. |
|---|
| 47 | |
|---|
| 48 | - Classroom teaching: allowing the management and implementation of software installation on the computers of teachers, with ability to customize the settings according to user requirements. |
|---|
| 49 | - Classroom teaching ICT Classrooms: implementing methods independent support for PCs of students and teachers. |
|---|
| 50 | - Self-learning ICT Classrooms: methods of deployment computers for students, grouped according to the needs identified for each position or for each user profile. |
|---|
| 51 | |
|---|
| 52 | * Organizational Scenarios: The project can be implemented to provide support in other settings defined in an Institution, such as: |
|---|
| 53 | |
|---|
| 54 | - Information Services. |
|---|
| 55 | - Helpdesk for employment computers. |
|---|
| 56 | - Servers Deployment in Data Center. |
|---|
| 57 | |
|---|
| 58 | |
|---|
| 59 | Origins |
|---|
| 60 | |
|---|
| 61 | OpenGnsys born in May 2009 after the Working Groups RedIRIS held in Malaga as an effort to integrate several projects in development: |
|---|
| 62 | |
|---|
| 63 | * Brutalix, University of Zaragoza |
|---|
| 64 | * Entorno Avanzado de Clonación (EAC), University of Málaga. |
|---|
| 65 | * Web Hidra Interface, University of Seville. |
|---|
| 66 | |
|---|
| 67 | |
|---|
| 68 | OpenGnsys homepage: |
|---|
| 69 | https://opengnsys.es/ |
|---|
| 70 | |
|---|
