1 / 12

System Management FW

System Management FW. Author: Miguel Angel Oltra Identification: WP2-SystemManagementFW Partner: Telvent Date: 26 SEPT. 2003 Version: v0.2 Status: draft. 1. Introduction 2. System Management WG 3. Preliminary Planning 4. Partners involved 5. References

jerome
Télécharger la présentation

System Management FW

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Management FW Author: Miguel Angel Oltra Identification: WP2-SystemManagementFW Partner: Telvent Date: 26 SEPT. 2003 Version: v0.2 Status: draft

  2. 1. Introduction 2. System Management WG 3. Preliminary Planning 4. Partners involved 5. References 5. References

  3. Introduction • What is System Management? • Definition I: • The general area of Information Technology (IT) that concerns configuring and managing computer resources, especially network resources. (http://wi-fiplanet.webopedia.com/TERM/S/system_management.html) • Definition II: • Activities performed by a system manager, aiming to minimise the use of excessive, redundant resources to address the overlapping requirements of performance balancing, network management, reducing outages, system maintenance costs, diagnosis and repair, and migration to new hardware and software system versions.(htttp://www.hyperdictionary.com/computing/system+management )

  4. Introduction • Definition III: • System management ensures that different systems within an enterprise network function economically and securely, allowing for optimal use of system resources (product point of view) (http://www.fujitsu-siemens.com/rl/products/software/systemmanagement.html) • Definition IV: • The System Management helps systems administrators rapidly respond to potential and actual system failures, increases system stability, and reduces troubleshooting complexity. It provides a consolidated view of all system health and configuration information and simplifies access to Web-enabled System Management software (product point of view) (http://h18000.www1.hp.com/products/servers/management/agents/description.html)

  5. System Management WG • The Working Group (WG) should define the scope of the proposed model specification • The WG should determine what is included within the scope of the SM framework • Monitoring • Events • State control • Agents • …

  6. System Management (previous scope) • Under SM scope • Component/container monitoring • Statistics • Information • … • Events and alarms notification • Component life cycle (state) control • Management Agents • Configuration Management

  7. System Management (previous scope) • Other SM considerations: • Component life cycle • Management protocols (SNMP, CIM/WBEM, HTTP, ...) • Security management • Resources management • Fault management and recovery • Management Interfaces definition • Management data model definition • Data representation

  8. System Management (previous scope) • Relationships among SM WG and other WGs • Work is close to other WGs (frameworks) • Security WG • Deployment WG • Resources Management WG • Coordination with other WG would be desirable (inputs & outputs from/to other WGs would be included in the final model specification)

  9. Partners involved • Checking list of partners involved in the WG • INRIA • LSR • France Telcom R&D • THALES Communications • Telvent • Telefonica I+D • Univ. Prague • Univ. Politécnica of Madrid • Mailing list (partner subscription) • System-management@objectweb.org

  10. Preliminary Planning • Next three month planning (1st Oct.-31st Dec.) • Scope definition (consensus by all partners) • 1st Oct. - 17th Oct. (3 weeks) • Define what is and what is not included under the umbrella of the WG (what is our vision of a SM framework) • Define TOC of the working document • Define interest area for each partner • Define WG work plan

  11. Preliminary Planning • Review SM state of the art (e.g. Java, Corba, .NET, OSGi, IETF, DMTF...) • 1st Oct.- 31st Oct. (5 weeks) • Define WG requirements template • 20th Oct. – 31st Oct. (2 weeks) • Gather model requirements from partners (platforms and test-beds) • 3rd Nov. – 28th Nov. (4 weeks) • First version of the model specification (draft) • By 31st Dec.

  12. References • J2EE Management Specification (JSR-77) • JMX Instrumentation and Agent Specification v1.2 • OSGi Service Platform Release 3 • IETF (Internet Engineering Task Force) • DMTF (Distributed Management Task Force) • …

More Related