New Installer: Use Cases

Use Cases

boot DVD
go through Wizard
let the installer deploy and configure
After reboot, system is ready to use (or start firstboot sequence, if configured that way)

Using stand alone Installation wizard only to create configuration.

start installer on any machine ('AutoYaST config' way)
boot the installation media and only proceed with wizard, at the end of it (instead of deploying)
let the installer export gathered data, provide the file and (probably) shutdown the machine

Use other tool (Studio, new Web tool, any 3rd party application, Installer Wizard itself) to create configuration file describing target system.

boot media, select option to provide configuration file (network/USB)
unless entering some info is required, the rest should be non-interactive
installer downloads and validates the file
if mandatory parts are missing, opens the Wizard (or only necessary parts of it) and asks user (input is validated)
if the deployment was already done before [can we check it? should it be indicated by user by some option provided during boot or in the config file?], starts with Apply Config phase
installer proceeds with deployment, without user interaction
after the deployment, installer proceeds directly with Apply Config

boot media
register
use Pool (an optionally Updates) as a source of installation repositories
all products including add-ons have to be registered at the end of the installation unless registration is explicitly skipped by the user

boot media
register
get list of compatible/paid add-ons (HAE, HAE-GEO)
select and use them for installation
all products including add-ons have to be registered at the end of the installation unless registration is explicitly skipped by the user

boot media
use new add-on, e.g. OES (possibly from SCC or other online repository)
add-on will extend the installer workflow with some more steps, replace some old ones, etc.
add-on will require some additional packages to extend the current installer and to be used in newly added dialogs
all products including add-ons have to be registered at the end of the installation unless registration is explicitly skipped by the user

boot from media
detect previously installed system
offer for upgrade
contact SCC and get upgrade proposal for add-ons TODO: define 3rd party Add-Ons behavior (different registration URL)
add/upgrade another add-ons manually
solve dependencies
upgrade installed products and software

start installation
configure the installation
save the configuration (the config file) to a removable device or upload it to a server
(finish the installation or abort when just creating the config)
later, when installing a new system or reinstalling the system, add the config file URL to the boot parameters
install the system reusing the values entered in the original installation without asking the user again

Note: More and/or more concrete use cases or user stories to be added.