[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dcml-frame] Meeting info
Hello Ajay, We're still in development on our CMDB/CI schema, and I definitely agree with the mapping exercise. On our Apps/Services call yesterday, we too are looking to consider the usage of existing mappings/definitions that have been created by CIM, and add the necessary layers of interrelationships/interdependencies that DCML targets in relating element-to-element->to-ITILprocess-to-ITILprocess->to-Service-to-Service->-t o-etc. The big thing is where we start. We want to make sure we're comprehensive, but in our initial creations, we can clearly articulate the relationship of DCML to element management standards such as CIM being implemented in SMASH/SMIS/etc., and create metadata interfaces that rollup to using ITIL as the framing for element-to-element according to processes invoked according to services instantiated according to business requirements at the BP and Industry layers of IT Services management. Maybe one of our use cases can depict the day in the life of a Industry Service run on be half of a corp (XYZ Corp) that decomposes into the proper processes, elements, CIs/CMDB usage, etc. that would in turn show the ecosystem of the various standards (including DCML's proposal to create ITIL dynamics) invoked to operate the service (and its underlying IT Services) ongoing. It would seem that the various elements we want to reference have been pre-created; even the portions of the app levels (within WSDM, WS-Management, etc.) have provided metadata for our relationship mapping. What's missing is the integration to the operational intelligence that we can deploy to our ITIL strategies. Have you examined SMASH in-depth? What's your impression? What about the MUWS/MOWS construct of WSDM? I'm assuming that WSDM is focused on the manageability of Web Services themselves, not managing through Web Services interfaces - but, I need to catch up. Has anyone else on the Framework team examined both CIM and WSDM and their targets closely? J. Darrel Thomas Chief Technologist, Hosting Electronic Data Systems Corporation 5400 Legacy Drive Mail Stop H3-5A-34 Plano, Texas 75024 972-797-9695 (Office) 972-679-5943 (Cell) Darrel.Thomas@EDS.Com (Email) "Of all the things I've lost, the one I miss the most is my mind..." This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -----Original Message----- From: Ajay Gummadi [mailto:Ajay@opsware.com] Sent: Tuesday, March 15, 2005 12:34 PM To: dcml-frame@lists.oasis-open.org Subject: RE: [dcml-frame] Meeting info Darrel, How far along is your organization in arriving at a reference schema for CMDB and Configuration Items? Ultimately, it would be a worthwhile effort to map out the various components and relationships in CMDB in DCML and expose the same through well defined public interfaces and transport mechanisms. There was some discussion today wrt usage of CIM or borrowing its representation and XML notations, after further investigation. SMASH (which you refer to) is another effort worth looking into. We may be able to leverage each other's expertise here. Regards, Ajay -----Original Message----- From: Thomas, Darrel [mailto:darrel.thomas@eds.com] Sent: Tuesday, March 15, 2005 10:23 AM To: Tim Howes; dcml-frame@lists.oasis-open.org Subject: RE: [dcml-frame] Meeting info Hello All, Sorry I missed the meeting, I was on another call with EDS. One thing we discussed yesterday at the Apps/Services meeting was the beginnings of discussion around modeling to a CMDB/CI construct - where does Framework see our starting point, so we're on the same page? Also, we're planning on providing a reference schema of a CMDB and CI to the group as soon as possible from the EDS team - we'd like to make sure we have a clear strategy on the right starting point for this integration to ITIL. Finally, the use case on the ITIL-CMDB/CI interface may be somewhat abstract now - do we plan to drill down to the exposure of the CI/CMDB/DSL components being exposed to a service and marshaled through the associated Service Desk/Service Support processes of ITIL for completeness? Or, will we start with some level of building block on the foundational aspects of ITIL on top of element management schemes such as CIM (SMI-S, SMASH, etc.) thru to SOA functions such as WSDM that need the process intelligence and integration to our ITIL strategies? Thanks, jDT J. Darrel Thomas Chief Technologist, Hosting Electronic Data Systems Corporation 5400 Legacy Drive Mail Stop H3-5A-34 Plano, Texas 75024 972-797-9695 (Office) 972-679-5943 (Cell) Darrel.Thomas@EDS.Com (Email) "Of all the things I've lost, the one I miss the most is my mind..." This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -----Original Message----- From: Tim Howes [mailto:howes@opsware.com] Sent: Tuesday, March 15, 2005 12:03 PM To: dcml-frame@lists.oasis-open.org Subject: Re: [dcml-frame] Meeting info Attendees: Tim H, Ajay G, Barak P, Fred C, Steve H Actions: - Ajay to flesh out ITIL use case involving CMDB and send to list. Other fleshed out use cases to follow. - All to think about volunteering for document editor, which we will need soon. -- Tim Tim Howes wrote: > Hi all. We will be having our bi-weekly framework working group call > tomorrow, 3/15. Here's the info: > > Time: 9:00am - 10:00am PST > Dial-in: +1 888 772-1825 > International: +1 706 679-9986 > Passcode: 4087447509 > > Agenda: > > - Introduction and roll call > - Agenda review > - Partner recruitment update > - Action item review and clarification > - UML proposal > - ITIL use cases > - Volunteers for document editor > - Any other business > > See you all tomorrow. -- Tim
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]