(file) Return to Objectives.dxx CVS log (file) (dir) Up to [Pegasus] / pegasus / doc / DevManual

 1 karl  1.1 /*
 2 karl  1.2 
 3 karl  1.1 */
 4           
 5           /** @name Objectives
 6           
 7           <B>Objectives of the Pegasus Project</B>
 8           
 9           The Pegasus project was initiated by the Open Group to provide a means to
10           define and clarify new standards for the manageability of IT environments.
11           
12           The Project has the following major objectives:
13           <UL>
14           <LI>Creation of a prototype environment for a manageability architecture that
15           uses existing and emerging standards.
16           
17           <LI>Provide a manageability implementation that is sufficiently rich and
18           efficient that it can be used as the basis for production environments.
19           </UL>
20           <UL>Provide a manageability environment that can be used to test and
21           demonstrate components of the manageability architecture.  This would allow us
22           not only to create specifications but to create demonstratable solutions and
23           to test those solutions agains the specifications. We have found in the last
24 karl  1.1 few years that creating standards and specificaitons alone is not enough.
25           These solutions will only be used if there is real supporting code.  Further,
26           we have come to beleive that we cannot really understand the correctness or
27           effectiveness of standards without implementations.
28           <LI> Create standards and specifications for manageability APIs
29           <LI> Contribute back to the DMTF i
30           </UL>
31           
32           <B>Manageability</B>
33           
34           We see the problem of managing IT environments as having several major
35           components:
36           <UL>
37           <LI>The Management environment - This is represented by the systems that
38           perform the tasks of managing our IT environment.  There are a number of major
39           and minor suppliers of systems of this type, either for enterprise wide
40           management or for managemetn of specific tasks, functions, applicaitons,
41           systems, networks, etc.
42           <LI>The Manageability environment - The management the interfaces the managed
43           resources with management.  This includes instrumentation for capture of
44           information, functions to execute tasks within the environment and additional
45 karl  1.1 facilities to make this all available to the Management envirionment
46           <LI>The management/manageability interface - This is the key interface that
47           allows the sepeartion of manageability and management. This interface must
48           define the information and protocols for the passage of management information
49           between the manageability environment and the management environment
50           <LI>The management/Instrumentation Interface - ATTN: Explain this one.
51           </UL>
52           
53           <B>WHY SEPARATE THE TWO</B>
54           
55           ATTN: add this
56           
57           ADDITIONAL COMMENTS THAT NEED TO BE MADE:
58           
59           
60           Today, these two environments are heavily integrated.  Most management systems
61           include thier own manageability components (agents, information capture tools,
62           control tools). Thus, the commitment to a management system is also the
63           commitment to instrumentation.
64           
65           The objective of standards like SNMP and WBEM is to provide the standards to
66 karl  1.1 separate manageability from Management.
67           
68           */

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2