D-RE (DEOS Runtime Environment)
D-RE is an execution environment with functions that help achieve dependability in a system. It consists of the following subsystems
- D-Visor
- D-System Monitor
- D-Application Manager
- D-Application Monitor
- D-Box
- D-Script Engine
- System Recorder
Datails of each subsystem will be given in a document which is due to be released.
OS in which operation is verified
Ubuntu 12.04 LTS ( i386 / amd64 )
CentOS 6.4 ( x86_64 ) ( i386 is not supported )
Download
Document
- DEOS Programming Reference 1.0
- D-RE Specifications 1.02 (An install guide is included)
- D-RE_APIs Specifications 1.02
- D-RE_Commands Specifications 1.02b
- D-RE_API Sample Programs Manual 1.02
Binary and source code
-
Binary and source code for Ubuntu 12.04 (1.4 MB)
Please refer to the Appendix of D-RE Specitications 1.02 in order to install D-RE using the apt-get command. -
Binary for CentOS 6.4 x86_64 (180 KB)
Please refer to the README.TXT included in the tar file.
Snapshot function and checkpoint function are not supported. -
Source code for CentOS 6.4 x86_64 (1 MB)
Demonstration Movie
Note: Voice narration can be heard.
The demonstration of systems which applied have adopted the concept of DEOS
-> Overview movie of the demonstration system
( 11.4MB 1min40sec )
- Demo Scenario1
In this first scenario, the introduction of a new service has caused the number of accesses to the website to exceed the maximum allowable limit. As part of the Failure Response Cycle, according to the actions described in D-Case, the system was restored to the state prior to the installation of the new service. Then, as part of the Change Accommodation Cycle, the stakeholders board decided upon system reinforcement in order to accommodate the introduction of the new service.
-> Demo Scenario1 ( 6.0MB 2min40sec ) - Demo Scenario2
The server begins to lag. In this second scenario, we demonstrate how, in accordance with the solution previously described by D-Case, an unsuitable batch job is terminated and the system is returned to a normal state.
-> Demo Scenario2 ( 7.7MB 1min15sec ) - Demo Scenario3
In this scenario, it is demonstrated how D-Case can be used when memory usage has exceeded acceptable system values. We demonstrate how, in accordance with the solution described by D-Case, the server is rebooted, a diagnostic module is added, and then the cause is identified.
-> Demo Scenario3 ( 10.8MB 1min42sec ) - Demo Scenario4
In this scenario, when checking whether the system is fit to run at a future time, it is found that services will not be provided properly the following day due to an expired license. This demonstration outlines the scenario up through to the update of the expired license.
-> Demo Scenario4 ( 6.8MB 1min26sec ) - Demo Scenario5
In this scenario, cross-checking next month's staff reassignment list against D-Case, "D-Case Watcher" finds that a node administrator is going to be reassigned.The next administrator is determined and D-Case is updated.
-> Demo Scenario5 ( 3.9MB 1min48sec )
License
The license of D-RE is GPLv2. Please refer to the source code of each subsystem for details.
Contact information
