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.
Aperi CMDB Integration
| Dial-in number:
Toll Free: 877-421-0030 ; International: 770-615-1247 ; Passcode: 11587 |
| Default schedule:
- Every Two Weeks, Thursday 1-2pm PT/4-5pm ET The Agenda will be posted prior to the next call. |
Contents
Upcoming meetings:
Next meeting: Thursday, March 20, 2008
Thursday, April 03, 2008
Thursday, April 17, 2008
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
Agenda
- Continue discussion regarding CMDBf, LIC and COSMOS integration.
Key Documents Under Discussion
Minutes from previous meetings:
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.