Aperi Launch in Context Enablement Workgroup

Aperi Wiki Home

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.

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

Work Page

Minutes from previous meetings:

2008/04/16

• Participants

• Martine Wedlake
• Jenny Monesson
• Al Heitman
• Duane Baldwin

• We went over the LIC model again to determine what associations we want to use (where the ??? are now)

• For the LICCapability to RemoteServiceAccessPoint, we determined that ElementCapabilities will work fine.
• For the LICDescriptor to RemoteServiceAccessPoint, we determined that we'd like to use ElementSettingData (which requires LICDescriptor to specialise from SettingData, which makes sense anyway).
• We decided to remove the association between the RemoteServiceAccessPoint and the RegisteredProfile. This link wasn't really adding anything above the capabilities anyway...

• Next Steps:

• Martine to patch up diagram.
• Martine to create concrete examples of LICCapabilities (specialising into separate classes for categories; such as LICVolumeCapabilities, LICPoolCapabilities, LICHostCapabilities, etc.).
• Martine to work on Draft document (following DMTF PUG format; but probably in Word).
• Duane to work on Scoping Document (1 to 2 pages describing the profile and it's benefits, etc.).

2008/03/20:

• We had a good discussion regarding the overall strategy and reviewed the material posted in the work page. In general, the workgroup feels that this is the right general direction.
• There was a discussion about security, and it was felt from the workgroup that we did not want to manage keys/credentials within the CIM Agent, but will need to expose the authentication mechanisms required by the LIC access point.
• John would like to see more discussion about the kinds of things that can be launched to. E.g., what will it do, and how do we want to represent those services? Martine suggests wrapping that activity with an overall use-case discussion where we can tie it back to user actions (e.g., user wants to set various settings of Brocade switch from Aperi, launches to the control panel via LIC, etc.). Pretty trivial to write out the use cases, but they should help communicate to a larger audience what we're trying to define with the "launch types" or whatnot.

Action Items

Martine -- To post instance diagram of the interaction between the LIC point and services/domains

John -- To post instance diagram around the PRP interactions

2008/03/05:

• 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.