---
# System prepended metadata

title: 20240208_OSBuild-CoreOS-Phase2

---


# 20240208_OSBuild-CoreOS-Phase2


Future Work to Scope:


## Effort 1 (customer facing, now customers get a better UX)
- Complexity HIGH
- Integration with osbuild/images
    - evaluate current image generation using osbuild/images
        - osbuild/images is where IB and other RH tools generate images that are used for production
        - osbuild-mpp is a dev tool, not really used for production
    - add new code to osbuild/images to support creating CoreOS images definitions
        - as part of this understand the architecture of osbuild/images and re-factor things as necessary
    - switch COSA over to using OSBuild/images for image defnition generation
- Integration with Image Builder itself
    - Understand how Image Builder consumes osbuild/images
    - Work with the team to get osbuild/images CoreOS options available in IB
    - Verify that locally set up Image Builder (osbuild-composer??) can create CoreOS disk images
- UI/UX work to get that then implemented in cloud.redhat.com/hosted IB
    - Open tickets with teams to figure out how to get the work we did in IB into cloud.redhat.com

## Effort 2 (customer facing, now customers can create derived ISO image)
- Complexity HIGH: Add support for building the ISO using OSBuild
    - determine what ISO building support exists in OSBuild today
    - evaluate our current ISO features and compare
    - most likely create our completely own separate new stage that creates an ISO like the one we produce today

## Effort 3 (customer facing, now customers can create derived GCP image)
- Complexity LOW-ish: Add support for building cloud image artifacts using OSBuild
    - aws, azure, etc
    - find image formats that OSBuild doesn't know about and add them as stages
        - hopefully almost everything can be done with `org.osbuild.qemu` stage
            - though I'm sure we will need to add support for some options
        - image formats we produce today:
            - raw, qcow2, ova, vmdk, vhdx, tar.gz (GCP weirdness)

## Effort 4 (internal alignment, less maintenance for our teams)
- Complexity HIGH: Add support for building s390x secure execution images (somehow??) using OSBuild
    - Nikita looking into this already

## Effort 5 (internal alignment, less maintenance for our teams)
- Complexity HIGH:
- Start using an osbuild provided library for uploading images to clouds
    - right now we use the mantle/ore code to upload to clouds
    - Image Builder also uploads to clouds
    - We need to not maintain the ore code long term
    - analyze the existing features in osbuild provided image uploading code
    - add features that we need
    - switch our tooling to upload using that library