Goals:  

• Support updating systems using image-mode workflows (i.e. update the image, then update the system to the new image)
• Support views of update progress at the image level

Requirements:

• A system admin can update an image-mode RHEL system from Satellite. This includes:
  • Updating to the latest tag for the image used to deploy the system
  • Updating to a chosen tag for the image used to deploy the system
• A system admin cannot directly remediate a host by updating a single package or configuration that should be built into the image (this comes in m3)
• A system admin CAN directly remediate configuration issues that can not / should not be built into the image
• A system admin can see the current update and rollback settings for a host that live on that host
• A system admin can see a list of all deployed images, inferred from system bootc information, including links to the registry where the image is stored 
  • Within that, a system admin can see a list of all of the systems using a given image and the current hash of each
  • (stretch) System admin can see an amazingly awesome super duper chart that shows a distribution of systems by hash, to facilitate tracking of system updates

Open Questions:

• Should image-mode hosts be attached to manifests or manifest lists?
  • Lubos+Ina: bootc implements container native tooling, so whatever the tag is pointing to it will figure things out; thus, we can operate on lists and regular manifests