YaST/Research/YaaS

From openSUSE

Revision as of 10:24, 26 June 2008

YaST as a Service

Description

Define a service-oriented architecture for YaST, ideally REST based, and refactor modules toward this architecture. This affects a couple of other research areas, namely

• Make YaST Independent of YCP
• Using CIM from YaST modules
• YaST DBus Service
• YaST PackageKit Service
• YaST Web User Interface

Picture of the architecture

Relevance to YaST/openSUSE

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

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

Describe what is *NOT* part of the project. Use cases and scenarios that remain excluded.

Related technologies

• REST architecture style
• HTTP protocol
• HTML language
• D-Bus

Typical use case

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

Describe the knowledge required for participation and the required skill level for each skill.

ie: Rate the complexity of the project and propose a skill level (entry, mid, advance) for participants.

Dev. environment/equipment

Does working on the project require a specific environment or equipment - besides a workstation with internet connection?

Participants

If you wish to participate, add yourself here (your user page link, hompe, or e-mail or similar).

• kkaempf at suse.de
• cschum at suse.de
• garrett at suse.de
• shaas at suse.de

Division of work and schedule

Describe how work should be divided among participants and a rough schedule for the week.

References

• Building Web Services the REST Way (What is REST actually)
• How to create a REST protocol (Tips 'n Tricks)
• REST bookmarks (collection of references)