Feature Overview (aka. Goal Summary)  

MicroShift  customers must be able to update (Z-Stream)  and upgrade (Y-Stream) their edge deployments in a secure and stable way.

Goals (aka. expected user outcomes)

MicroShift users are able to update their edge installations.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

• Both rpm based and ostree based installation need to be updateable.
• ostree based installation, due to the inherent greenboot/ostree rollback feature, must also support rollbacks. 
• Updates must be realiable and should never ever brick an installation.
• Updates should be quick, e.g. can be applied in the magnitued of minutes.
• Update can require a reboot to take effect.

Use Cases (Optional):

Questions to Answer (Optional):

The ostree rollback needs special attention, as this is something OpenShift does not. Questions for this:

1. How to integrate with ostree greenboot, i.e. detect the different lifecycle events.
2. How to backup (and on rollback: restore): etcd state (update might include an etcd version change which needs to be undone for rollback)
3. How to integrate with workload? The ostree image might include workload updates, e.g. changes to an workload statefull database, which the workload needs to be able to back/restore - basically the same what the platform needs to do with etcd.

Out of Scope

-

Background

-

Customer Considerations

-

Documentation Considerations

Procedures for updates need to be documented in an easy and simple way.

Interoperability Considerations

-