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.
Production Ready Task Force Work Page
This page is for communicating thoughts and ideas on works in progress to the workgroup.
Known Issues
- Deployment Issues -- General issues surrounding the machine infrastructures needed; getting CIM servers in customer lab, setting up and configuring the software, etc, etc.
- Consistency -- Different implementations tend to do things slightly differently even if they don't have to.
- Reliability, Robustness and Stability -- overall problems that need to be addressed in order for SMI-S based management to supersede proprietary implementations. It is not acceptable to customers to have unstable management infrastructures.
- Spec changes too quickly/much -- This makes it difficult for exploiters to code solutions as everything becomes a moving target.
- Scalability and Performance -- like the stability item above, this becomes important when we try to get customers to really use this stuff.
- Stress Testing -- how to we ensure that we've met stability?
- Embedding vs Proxy -- Seems like embedding makes for better, more stable infrastructures but isn't always possible?
- Backwards Compatibility (both within SNIA and for vendor extensions) -- How to ensure that products that use these standards don't end up painted in a corner where they can only work with one version at a time, or can't handle an upgrade of a component, etc.
- Problem Profiles (e.g., not keeping up with other work) -- For example, Copy Services, Host Based Raid, etc.
- Single standardized CIMOM? Do we want to define a single CIMOM that everyone should use?
- Supporting SMI-S for Element Managers -- What kind of changes do we need to be able to allow element managers to get the data they need quickly enough to handle a dynamic real-time customer environment.
- Event Management -- Indications has some problems, we should fix it?
- Bet the farm on SMI-S? When to use SMI-S and when not to; what needs to happen to make SMI-S the primary and obvious choice?
- Lag between device function and SMI-S -- Is somewhat contradictory with earlier requirements/requests for avoiding spec churn and backward compatibility. How do we manage the conflict?
- Need more client software to support SMI-S -- Like the bet the farm idea, what do we do to increase adoption.
- Client software coded for SMI-S vs client software coded for specific device CIM model