OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dcml-appserv message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dcml-frame] Groups - Joint DCML TC call 6/7/05 modified


Please find a write up of a possible use case attached.

Regards,
Andre

-----Original Message-----
From: SBarbuscia@inventures.com [mailto:SBarbuscia@inventures.com] 
Sent: 04 June 2005 01:21
To: dcml-frame@lists.oasis-open.org
Cc: dcml-appserv@lists.oasis-open.org
Subject: [dcml-frame] Groups - Joint DCML TC call 6/7/05 modified


Joint DCML TC call 6/7/05 has been modified by Mrs Sarah Barbuscia

Date:  Tuesday, 07 June 2005
Time:  09:00am - 10:00am PT

Event Description:
Dial-in:   (888) 772-1825
Passcode:  4087447509

Agenda:
1. Review of High Level Use Cases
-Reminder - please submit use cases for review to the TC list
2. Charter Status

Minutes:


This event is one in a list of recurring events.
Other event dates in this series:

Tuesday, 18 January 2005, 09:00am to 10:00am PT
Tuesday, 01 February 2005, 09:00am to 10:00am PT
Tuesday, 15 February 2005, 09:00am to 10:00am PT
Tuesday, 01 March 2005, 09:00am to 10:00am PT
Tuesday, 15 March 2005, 09:00am to 10:00am PT
Tuesday, 29 March 2005, 09:00am to 10:00am PT
Tuesday, 12 April 2005, 09:00am to 10:00am PT
Tuesday, 26 April 2005, 09:00am to 10:00am PT
Tuesday, 10 May 2005, 09:00am to 10:00am PT
Tuesday, 24 May 2005, 08:30am to 09:30am PT
Tuesday, 21 June 2005, 09:00am to 10:00am PT
Tuesday, 05 July 2005, 09:00am to 10:00am PT
Tuesday, 19 July 2005, 09:00am to 10:00am PT
Tuesday, 02 August 2005, 09:00am to 10:00am PT
Tuesday, 16 August 2005, 09:00am to 10:00am PT
Tuesday, 30 August 2005, 09:00am to 10:00am PT
Tuesday, 13 September 2005, 09:00am to 10:00am PT
Tuesday, 27 September 2005, 09:00am to 10:00am PT
Tuesday, 11 October 2005, 09:00am to 10:00am PT
Tuesday, 25 October 2005, 09:00am to 10:00am PT
Tuesday, 08 November 2005, 09:00am to 10:00am PT
Tuesday, 22 November 2005, 09:00am to 10:00am PT
Tuesday, 06 December 2005, 09:00am to 10:00am PT
Tuesday, 20 December 2005, 09:00am to 10:00am PT
Tuesday, 03 January 2006, 09:00am to 10:00am PT
Tuesday, 17 January 2006, 09:00am to 10:00am PT

View event details:
http://www.oasis-open.org/apps/org/workgroup/dcml-frame/event.php?event_
id=6897

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able
to
copy and paste the entire link address into the address field of your
web
browser.

Title: Merger & Acquisition by Management and Automation

 

Merger & Acquisition by Management and Automation

A Use Case Proposal for DCML

Andre Kramer, Citrix (R&D) Ltd

6th June 2005

 

Following the predictable industry consolidation trend, the agile, technologically innovative, entrant YGene was acquired by the larger XGenetics. Y, though an early adopter of Grid computing technology, lacked the IT process maturity of X, which uses ITIL to deliver IT as a service. Here X was leading, due to its advanced IT management automation, based on the OASIS DCML framework.

 

Two challenges presented themselves: Y employees, contractors and partners had to be migrated to X’s IT systems. This involved a manual audit of all accounts at Y, clarifying the “role” each user had in the system and constructing a DCML (variously known as Data Center Markup/Model language or Datacenter Configuration Management Language) model describing these high-level business relationships, translating these into equivalent serviced roles in the new joint organization.

 

This document (i.e. the model of the joint IT system) was submitted as input to X’s service provisioning systems, which automatically determined the personalised services required by each “new” employee and partner. This derived information was stored into, and used to update, X’s DCML-based CMDB (ITIL Configuration Management Database). Note that, this caused new user profiles to be created and likely future loads to be determined, resulting in service software installation (including licensing updates etc) and servers, networks and storage (virtual and or hardware) to be provisioned. Company X had done such M&A before, so knew the value of DCML, as a model of its data center operations and its good integration with high level ITIL services, facilitating automation of service life cycle management.

 

The second challenge was a reverse of the top down service provisioning problem. Y’s Grid operated over a large collection of heterogeneous systems (different hardware, software and even organizations). Only a schematic view of the “virtual organizations” formed on the Grid existed (on the back of an envelope). Ys admins, with help of Xs data center automation experts (a new recognized IT discipline) were able to use diverse distributed systems discovery and management tools to obtain configuration data for the Grids resources. However, the collected information was in multiple (pre-DCML, of course) formats.

 

Different virtual and real Grid components and their management systems use diverse modelling approaches (WSDM, CIM, UML and other object models, as well as relational and other more basic (resource/attribute/value) tables, as well as ad-hoc models). Such model data were included in a DCML document as legacy models, and were initially referenced from DCML statements and subsequently  refined (tool and manual conversion to DCML model schema),  until the admins could claim control of the resulting integrated computing resource grid.

The resulting refined description was stored in the central CMDB and represented the joint companies “virtual data center”. At this point it became the central locus for all IT change management.

 

The resulting joint organizations IT operated in an automated service based manner. The fact that large parts of the resulting virtual data center was outsourced, as services provided by utility computing vendors, or contributed to virtual organizations spanning the research Grid, did not concern anyone, as the DCML model was owned, change controlled and stored at XY. Subsequent incremental changes used the same update mechanisms (change notification, rules etc, effectors etc) that the bulk updates utilized.

 

Having one solution (DCML) which can address and span both the top down and the bottom up IT management processes, in a single framework was a major winner for the Merger & Acquisition by Management and Automation, one that played a large part in making the joint company a success.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]