Software Management/Changes/Code9 Code10

From openSUSE

Changes between Code9 and Code10

New patch management

Fixes Code9 bugs and shortcomings

• Code 9 patches are containers
  • Update RPMs are contained within patches
  • No way to access them without YaST
  • Cant install fixed packages directly
  • Customer is forced to YaST

• Code 10 patches are relations
  • Relate fixes to packages, scripts, messages
  • Packages are separately available
  • Tool independance

• Code 9 patches are not idempotent
  • Content determines need
  • All-or-nothing
  • No dependency resolution

• Code 10 patches relate atomic operations
  • Need independent of content
  • Partial install detectable
  • Full dependency resolution

Multiple repositories

• supports driver update process
• Allows 3rd party repositories (ATI, Nvidia, ...)
• Dependencies are solved across all repositories
• Add-on products
• Non-OSS repositories

Registration & Activation

See Novell customer center

• The Update Server knows everything
• The client knows nothing
• Registration: Who ?
• Activation: What ?

Client Systems — User Accounts — Access Rights

ZENworks integration

• Integration of existing Novell technologies
• Command line client
• Desktop tools
• Huge gap
  • YaST installs
  • ZENworks updates
• Mostly targeted at enterprise offerings

NCC — Satellite — Data Center

Patterns

Patterns support package aggregation

• Selections are UI macros only
• Functional grouping needed
• Building blocks

See Patterns on opensuse.org

Future: Packages + Configuration + Workflow