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 SNIA Production Ready Task Force Workgroup
| Dial-in number:
Toll Free: 877-421-0030 ; International: 770-615-1247 ; Passcode: 11587 |
| Default schedule:
- Every Two Weeks, Friday 1-2pm PT/4-5pm ET The Agenda will be posted prior to the next call. |
Contents
Upcoming meetings:
Next meeting: Friday, March 14, 2008
Friday, March 28, 2008
Friday, April 11, 2008
Friday, April 25, 2008
Friday, May 09, 2008
Friday, May 23, 2008
Friday, June 06, 2008
Friday, June 20, 2008
Friday, July 04, 2008
Friday, July 18, 2008
Friday, August 01, 2008
Friday, August 15, 2008
Friday, August 29, 2008
Friday, September 12, 2008
Friday, September 26, 2008
Friday, October 10, 2008
Friday, October 24, 2008
Friday, November 07, 2008
Friday, November 21, 2008
Friday, December 05, 2008
Friday, December 19, 2008
Agenda
- Continue brainstorming issues. In this meeting, I'd like to hear other issues from folks to add to the list and then start to collapse and prioritise the issues. Here is the current list:
- Deployment Issues
- Consistency
- Reliability, Robustness and Stability
- Spec changes too quickly/much
- Scalability and Performance
- Stress Testing
- Embedding vs Proxy
- Backwards Compatibility (both within SNIA and for vendor extensions)
- Problem Profiles (e.g., not keeping up with other work). For example, Copy Services, Host Based Raid, etc.
- Single standardized CIMOM?
- Supporting SMI-S for Element Managers
- Event Management
- Bet the farm on SMI-S?
- Lag between device function and SMI-S
- Need more client software to support SMI-S
- Client software coded for SMI-S vs client software coded for specific device CIM model
Key Documents Under Discussion
Minutes from previous meetings:
2008/03/14
- We added a few items to the list of problems and categorized them into three rough categories: Specification/SMI-S Issues, Technology Issues and Implementation/Adoption Issues.
- Next Steps:
- Continue to add items to the list and categorized them. We need broader input than we have had -- only a handful of people have participated in the workgroup to date, and we really want to try to represent a complete view of Aperi membership. Please send me (martinew@us.ibm.com) your ideas to add, or edit the wiki.
- Prioritise the list.
- Figure out where Aperi can help. For example, providing HDR support in Aperi can help drive momentum in industry, or providing client support can help test providers, etc.
2008/02/29
- We went over the initial list of items to understand what has already been captured.
- The team will now think up new items to add to the list and send them to Martine.
- In our next meeting, we'll start to determine categories of items to group the issues into.