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 "Aperi Launch in Context Enablement Workgroup"
(→Upcoming meetings:) |
(→Agenda) |
||
| Line 66: | Line 66: | ||
== Agenda == | == Agenda == | ||
</FONT> | </FONT> | ||
| − | + | Continue discussion of what the CIM/SMI-S profile would look like. Try to get more information about the descriptor file understood. | |
| + | |||
| + | <FONT COLOR=maroon> | ||
| − | |||
== Key Documents Under Discussion == | == Key Documents Under Discussion == | ||
Revision as of 10:54, 20 March 2008
| Dial-in number:
Toll Free: 877-421-0030 ; International: 770-615-1247 ; Passcode: 111587 |
| Default schedule:
- Every Two Weeks, Wednesday 1-2pm PT/4-5pm ET The Agenda will be posted prior to the next call. |
Contents
Upcoming meetings:
Next meeting: Wednesday, April 02, 2008
Wednesday, April 16, 2008
Wednesday, April 30, 2008
Wednesday, May 14, 2008
Wednesday, May 28, 2008
Wednesday, June 11, 2008
Wednesday, June 25, 2008
Wednesday, July 09, 2008
Wednesday, July 23, 2008
Wednesday, August 06, 2008
Wednesday, August 20, 2008
Wednesday, September 03, 2008
Wednesday, September 17, 2008
Wednesday, October 01, 2008
Wednesday, October 15, 2008
Wednesday, October 29, 2008
Wednesday, November 12, 2008
Wednesday, November 26, 2008
Wednesday, December 10, 2008
Wednesday, December 24, 2008
Agenda
Continue discussion of what the CIM/SMI-S profile would look like. Try to get more information about the descriptor file understood.
Key Documents Under Discussion
Minutes from previous meetings:
2008/03/05: Minutes
- We did a quick kickoff at the start (purpose, process discussion, etc.)
- Process
- Phase 1 -- Education ramp-up and brainstorming.
- Phase 2 -- Develop proposal.
- Phase 3 -- write whitepaper for final delivery to Aperi and SMI-S.
- General Requirements
- Need to support vendor extensions
- Be able to discover element manager capabilities (no a priori knowledge required)
- Need to support general extensibility from general model (not just overrides)
- Single sign-on authentication/authroisation if/when element manager supports it
- Align the LIC enablement with established SMI-S model (whenever possible). This might be through design structure (e.g., how we associate objects in the model) and/or can be achieved by recognizing that this feature bridges the gap between the SMI-S data model and element managers; so we need to stay focussed to use the "language" of SMI-S when appropriate.
- Proposed Mechanism
- Leverage the current Access Points Subprofile to establish linkages to the SMI-S data model; perhaps by additional associations to ProfileRegisteredProfile, ComputerSystem, and/or Service instances.
- Action Items
- Martine -- to create additional Wiki page to contain design ideas/thoughts.
- Martine -- to upload some initial thoughts on the SMI-S modelling.
- Dave -- to upload an overview / description of the LIC descriptor file.