Archive:Using CIM from YaST modules
This is now part of the Webyast project
Using CIM from YaST Modules
Description
There is a YaST prototype of the NFS server configuration module which is using yast2-cim package to read the configuration via the CIM/XML protocol and CIM model. The concept is functional, but the overall feeling from the implementation is that it is very complicated.
Relevance to YaST/openSUSE
Missing: Describe the project relevance to YaST. Which problem does it solve? How will it bring YaST forward ? How does it help openSUSE (resp. Novell)?
Goal
Missing: Describe the goal of the project, whats the expected outcome? Both long-term and short-term (for the hackweek).
Remember that the project should be doable and have a useful outcome within a week.
Scope
Missing: Describe what is *NOT* part of the project. Use cases and scenarios that remain excluded.
Related technologies
CIM
Typical use case
Missing: Try to describe how the project affects an end user. How would she use the result?
A specific story is *required*.
Required knowledge and skill level
C++, CIM, YaST2 internals
Skill level: medium - high
Dev. environment/equipment
Missing: Does working on the project require a specific environment or equipment - besides a workstation with internet connection?
Participants
- none so far
Division of work and schedule
Missing: Describe how work should be divided among participants and a rough schedule for the week.
References
Missing: Useful documentation and references. Including a link to a extended wiki page.
Willing mentors
- Stanislav Visnovsky
- kkaempf at suse.de
- User:Mvidner