openSUSE:Appliances events workshop Nuremberg 2010 projects updating appliances

Discussion about updating appliances, collecting requirements, discussing existing solutions, brainstorming about possible improvements, alternative solutions or new better concepts.

Update scenarios

No updates

Use case: Appliance doesn't need updates, e.g. read-only live media or demo appliances

Appliance configuration: Disabling updates

Tooling in appliance: None

External tooling: None

Direct package-based updates

Use case: Appliances making use of standard package sources without additional update QA

Appliance configuration: Configuring update repositories, enabling update stack

Tooling in appliance: Update stack (zypper, YaST, WebYaST, ...), registration for updates which require subscription

External tooling: Repository servers (NCC, Build Service, SMT, ...)

Gated package-based updates

Use case: Appliances making use of standard package sources with additional update QA

Appliance configuration: Configuring of gated update repository, enabling update stack, preparing for registration

Tooling in appliance: Update stack (zypper, YaST, WebYaST, ...), registration with gated updates server

External tooling: Creation of gated updates (SLMS), server for gated update repositories (SLMS, SMT)

Image-based updates

Use case: Appliances with non-packaged updates; major updates with disruptive changes, which can't be reflected in package updates; users who don't want to run the overhead of a package-based update system

Appliance configuration: Preparation for update, e.g. separation of system and user data

Tooling in appliance: Tools for preservation of user data (backup/restore system); tools for configuring external storage for user data; update notification?, ...

External tooling: Image deployment tools; support for backup/restore and external storage systems

Custom updates

Use case: Application specific update mechanisms; non-packaged systems; constrained systems (e.g. low disk space or memory, or restricted network access)

Appliance configuration: custom

Tooling in appliance: Custom updater (e.g. file based updater)

External tooling: Creation of specific update data, external updater?

Hybrid updates

Use case: Mixture of different update scenarios, e.g. package-based updates for minor updates, image-based updates for major updates

Appliance configuration: mixed

Tooling in appliance: mixed

External tooling: mixed

Product use cases

Status of current appliance versions of our products, how to approach in the future, what's needed.

SUSE Studio Onsite

Package-based update for maintenance updates, image-based update for major version upgrades

WebYaST

No updates scenario?

Gaps

Gaps in our tools to support wide range of update scenarios

• Studio configuration of update scenarios doing the appliance configuration
• Image-based update tooling
• Custom update support?