Wiki Navigation

Introduction

The Linux Management Console is included into the OpenDRIM project.

Purpose and Scope of this Document

In The Opendrim project,there are many remote management tools based on OpenWBEM.There is a need to centralize those tools as a uniform interface.

Source of the this Document

The goal of Linux Management Console is to minimize the cost of administering RedFlag?-based Linux environments, and to provide a simple, consistent, and integrated administration user interface and administration model. It also addresses the varying levels of server administration that are possible.

Anticipate Reader of this Document

Project Manager,Senior Manager,Related Developers and testers.

Nomenclature List

Module: a single tool which may be run as a opendrim child tool but is a

element in this framwork, is a dynamic library module according to the special format functions as defined.

Frame Work: the main window of this tool,and hold all the modules in its

own library.

SDK: Software Development Kit.

Function Requirement

Provide SDK

Developers could develop his own library modules according to the existed tools of the project opendrim with the SDK defined in this work.Besides,the module libraries should be taken up by the framework if needed.the framework is invisible to the developers,so they need not pay any more attentions to the skins and surrounding facilities.What they must do is to implement most of the interfaces of the module according to the SDK.

Uniform Interfaces

Every module in the framework keeps to the same interfaces of the GUI.they share the uniform style status bar,tool bar and menu bar.Besides,there is a unifore skins' setting,that will ensure only one uniform style at a time.

Interactive Requirement

Interactive Scene Description

Every time while the framework is started,the whole tool does not contain

any module.

Click "load module",then load in a new module from a dynamic library module

directed by dialog box if the module file keeps to the statndard interfaces defined by framework.

Make use of the module's function.
Click "unload module",then unload a existed module from the framework by

dialog box if the user do not need the module.

Of course,It is not necessary to unload a exist module because all the

modules in the framedwork will be unloaded automatically when the tool is shutdown.

System Event(Massage) Description

The SDK provides a series of interfaces about GUI. Besides,it define a set

of event-proceeding,which give out a series of standard events. So the module's could register and use more special events and signals in this tool for more functions. for example,mouse clicked in different scope view,action activated,and so on.

Environment Requirement of System

Software Environment

Asianux-based operation system >= 2.0

Hardware Ebvironment

Normal PC which supports Asianux 2.0 at least.

Performance Requirement

The time of startup should be less than 1 second. The whole framework should not expend too much cpu and memory. Reference level as following: cpu% < 2% ; mem < 4M.

Standard Requirement

The more requirement has been mentioned by opendrim project.

Special Requirement from Users

Authentication and Security

Every module should control its own Authentication and Security. And this framework tool should not contain any security leak.

Reliability,Backup and Recover

Because this framework does not refer to any important configuration file

or so and It is blind to its module's functions.

Every module should consider its own reliability,backup and recover.

User Manual and Help Documnet

Provide a complete user manual and a help document with no training.

Download in other formats:

Plain Text