Difference between revisions of "Aperi CMDB Integration"

Revision as of 16:31, 17 April 2008

Aperi Wiki Home

Next meeting: Thursday, May 01, 2008

Thursday, May 15, 2008

Thursday, May 29, 2008

Thursday, June 12, 2008

Thursday, June 26, 2008

Thursday, July 10, 2008

Thursday, July 24, 2008

Thursday, August 07, 2008

Thursday, August 21, 2008

Thursday, September 04, 2008

Thursday, September 18, 2008

Thursday, October 02, 2008

Thursday, October 16, 2008

Thursday, October 30, 2008

Thursday, November 13, 2008

Thursday, November 27, 2008

Thursday, December 11, 2008

Thursday, December 25, 2008

Continue discussion regarding CMDBf, LIC and COSMOS integration.

Work Page

2008/04/17

• Participants

• Al Heitman
• Bill Muldoon
• Duane Baldwin
• Martine Wedlake

• Status

• Bill and Martine met requirements of April 16 -- Storage Systems and Storage Pools.
• Bill checked code into COSMOS repository.
• Martine has just finished up Disks and will be working on Hosts and Masking/Mapping next; I think I'm on track for the end-Month deadline for "complete" instrumentation.

• Martine to provide a canned image of the Aperi database for COSMOS demos, testing, etc. This should have another device with hosts mapped to volumes.
• COSMOS will have externalised deliverables for the MDR toolkit available somewhere between June and July for eventual release in November. We'd like to integrate this toolkit into Aperi and migrate the "full featured" Aperi MDR into the Aperi codebase around this time period.
• We talked about data content schemas and determined that there may be some value in researching the SML schema because COSMOS has an ability to generate reports through SML. Having Aperi MDR push data up in an SML-Compliant fashion will make it easier to generate reports.

2008/04/03

• Participants

• Bill Muldoon
• Duane Baldwin
• Allen Heitman
• Martine Wedlake

• Today was a status update call to keep folks in the loop.
• Bill and Martine have begun work on the prototype; Bill working on the upper-layer MDR and Martine working on the lower layer AperiDB JDBC query code.
• The StorageSystem object class has been completed end-to-end.
• Martine is working on extending support of lower-level JDBC code to include StoragePools, Disks, Volume, Hosts. He will complete the StoragePool and StoragePool-to-StorageSystem relationship objects first.
• Bill is working on adding more CMDBf query capabilities (constraints, etc.) to the StorageSystem case with an eye to leverage that code for other objects as they become available.

• Action Items
  • Martine to draw UML instance diagram showing the relationships between StorageSystem, StoragePool and Volumes and how they're represented within CMDBf.
  • Martine to work on StoragePool relationships code (and send it to Bill).
  • Bill to work on fleshing out query interface to allow finer-grained constraint-type queries in CMDBf.

2008/03/20

• Participants

• Jack Devine
• Duane Baldwin
• Martine Wedlake

• Spent some time talking about creating the prototype. Jack believes there is a good connection between the Aperi and COSMOS in this effort, especially toward creating a prototype.
• Jack will ask Bill Muldoon work with Martine to help build MDRs (work together on this). Bill is writing a developers guide for COSMOS and will use this experience to help write it -- Aperi gets an MDR, COSMOS gets a real-world MDR example and a developers guide, all together.

2008/03/06

• We discussed the overall strategy for CMDB and integration with CMDBf. In general, it does seem that it's a good idea to work with CMDBf to help define the standard.
• We also discussed the prototype work started by Martine to deploy the Aperi database as a CMDBf MDR (Management Data Repository) and integrate it into the COSMOS query tool. We're looking for help to push the prototype further as it has been difficult for Martine to find time to work on it. If you're interested in helping, please send a note to martinew@us.ibm.com.
• We also discussed a vision of deploying the CMDB to help establish context around a Launch In Context (LIC) operation. The basic idea is that the CMDB contains data services for extracting information about the entire system that can be accessed from multiple points; we can leverage these services to do an in-context hand off between the launch-er and launch-ee. This would allow the launch-ee to provide operational/semantic launch capability instead of just a user-interface launch. Clearly the idea needs to be fleshed out some more; and is a much longer-term view, but is something to consider.