Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "COSMOSEclipseCon2008Presentations"
(→Panel) |
(→Tutorial) |
||
| Line 3: | Line 3: | ||
== Tutorial == | == Tutorial == | ||
| − | + | Introducing the COSMOS Configuration Management Database Federation (CMDBf) Toolkit | |
| − | + | In today’s IT environment, there is a vast collection of tools use to manage the enterprise. Many of these tools are specialized for a specific management domain and focus on a specific set of tasks. It is not uncommon to have one set of tools that manage asset information, another that work on configuration information, and yet another set that concentrate on performance data. These tools come from a wide variety of sources, including commercial vendors, open communities, and home grown solutions. Each of the tools typically work on the same set of IT resources although they model and identify them differently. Consider a machine in a data center. The asset tool may refer to the machine through an asset number that was assigned when the physical box was received while the configuration management tool might use a MAC address. | |
| + | The CMDBf standard defines a the concept of Management Data Repository (MDR). Each MDR must provide an implementation of the APIs that are declared in the specification. These APIs govern how management data can be exchanged between tools. The CMDBf specification is an important step in facilitating cross vendor interoperability. This facilitates the application of higher order management function, e.g. service level agreements, policy, to be implemented across the enterprise. | ||
| − | + | The COSMOS project will provide a set of enabling technologies, a “CMDBf Toolkit”, that facilitate the creation of CMDBf specification compliant Management Data Repositories. The goal of this toolkit is to provide a reusable framework with well-defined extension points that minimizes the work required to implement an MDR. | |
| − | + | Developers that attend this tutorial will learn how to apply the COSMOS “CMDBf Toolkit” to build an example MDR. The MDR will be built on top of a flat file repository provided as part of the COSMOS project. This files in the repository are compliant with the Service Modeling Language (SML) standard. | |
| + | Upon completion of this tutorial, the Developer will have a solid understanding of integration through the use of federating CMDBs, Management Data Repositories, and the Service Modeling Language (SML). | ||
| − | CMDBf | + | References: |
| − | + | CMDBf Specification: http://www.cmdbf.org/ | |
| − | + | Service Modeling Language: http://www.w3.org/Submission/2007/01/ | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Category: Emerging Technology | Category: Emerging Technology | ||
| − | Presenters: Mark, Jimmy, Don | + | Presenters: COSMOS Team, Mark (IBM), Jimmy (CA), Don (Compuware) |
== Long Talk == | == Long Talk == | ||
Revision as of 16:46, 14 November 2007
Contents
Tutorial
Introducing the COSMOS Configuration Management Database Federation (CMDBf) Toolkit
In today’s IT environment, there is a vast collection of tools use to manage the enterprise. Many of these tools are specialized for a specific management domain and focus on a specific set of tasks. It is not uncommon to have one set of tools that manage asset information, another that work on configuration information, and yet another set that concentrate on performance data. These tools come from a wide variety of sources, including commercial vendors, open communities, and home grown solutions. Each of the tools typically work on the same set of IT resources although they model and identify them differently. Consider a machine in a data center. The asset tool may refer to the machine through an asset number that was assigned when the physical box was received while the configuration management tool might use a MAC address.
The CMDBf standard defines a the concept of Management Data Repository (MDR). Each MDR must provide an implementation of the APIs that are declared in the specification. These APIs govern how management data can be exchanged between tools. The CMDBf specification is an important step in facilitating cross vendor interoperability. This facilitates the application of higher order management function, e.g. service level agreements, policy, to be implemented across the enterprise.
The COSMOS project will provide a set of enabling technologies, a “CMDBf Toolkit”, that facilitate the creation of CMDBf specification compliant Management Data Repositories. The goal of this toolkit is to provide a reusable framework with well-defined extension points that minimizes the work required to implement an MDR.
Developers that attend this tutorial will learn how to apply the COSMOS “CMDBf Toolkit” to build an example MDR. The MDR will be built on top of a flat file repository provided as part of the COSMOS project. This files in the repository are compliant with the Service Modeling Language (SML) standard.
Upon completion of this tutorial, the Developer will have a solid understanding of integration through the use of federating CMDBs, Management Data Repositories, and the Service Modeling Language (SML).
References: CMDBf Specification: http://www.cmdbf.org/ Service Modeling Language: http://www.w3.org/Submission/2007/01/
Category: Emerging Technology
Presenters: COSMOS Team, Mark (IBM), Jimmy (CA), Don (Compuware)
Long Talk
"Bringing new management standards to Eclipse"
CMDBf, SML, SDD, WSDM Reference implementation of CMBDf
Focus on what cosmos is and the standards that are used.
SML based resource models
What the standards are, how they work together
Presenters: Mark Weitzel, Jimmy Mohsin
Short Talk
Standards based systems management: An Overview of the COSMOS project Category: Emerging Technology
Presenters:
Poster
I think this is a gimmie... We definitely want to have a poster there. Category: Emerging Technology
Presenters:
BoF
I think this is a gimmie as well. Category: Emerging Technology
Presenters:
Panel
We tried this last year and got nuked.... Maybe if we could get CA/IBM/Groundwork execs there, we might have something...
Please add your thoughts here....
Cast a wide net, try to bring in other projects.
Take a standards angle: Eclipse has joined JCP, W3C Also work with standards for: Oasis, DMTF,