# 20230131_large-coreos-proposed-changes

# Agreed would be useful

- OSTree Native Containers + Layering
- updates in a container native world (for FCOS/zincati)
- tooling to build a bootimage from a container
- Integrating our CoreOS pieces more into Fedora/RHEL
- CI as far upstream as possible (rawhide, bodhi, etc)
- deriving OSTree variants from a CORE minimal OSTree, etc
- maybe the variants use container layering to create their derivative!
- Creates challenges around chunking for large derivatives (Kinoite is big for example)

NOTE: These are large initiatives ^^

# Still Discussing

- what teams are responsible for which pieces?
- install workflow
- do we still create our own images?
- bootc style versus coreos-installer style
- do we create our own bootimages or re-use anaconda/RHEL cloud image?
- do we do storage customization via image builder?
- update model for ostree containers
- future role of Ignition
- migration path for current users

# Goals

- improve or maintain customer UX
- can cut features that we deem we don't want
- reduce team load

# Investigate

- image builder
- Fedora Cloud SIG plans for image support

# Requests

Is there a plan in coreos-installer to allow something like `--image-url ostree-unverified-registry:http://registry.example.com:5000/my-r4e:stable` ?