cloudapi/v2: multi-image composes & a separate build step #40
ondrejbudai
started this conversation in
Ideas
Replies: 0 comments 1 reply
-
This all sounds reasonable to me. However there is one potential issue / complication - packages can be architecture-specific, so defining them on the distribution level can be oversimplification. While I don't think that we have architecture-specific customizations, I think that one could want some differences between architectures (e.g. different partitioning or partition sizes). Unfortunately I can imagine that allowing architecture-specific package and other customizations could complicate the user interface (e.g. of the service) a lot, so we may want to keep things simple anyway. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
multi-image composes
osbuild/osbuild-composer#1912 removed support (that was actually never working) for building multi-image composes. We want to re-introduce it at some point though. It's not yet decided if we can make this before v2 is on Public Beta or if this is to be postponed to v3 API. The new
POST /compose
route should look like this:The following properties are defined on a compose level:
The following properties are defined on the image level:
Open questions:
separate build step
We want to have a separate compose build step. In this setup, a user needs to call two routes to build and upload an image:
POST /compose
- queues a job that depsolves the package sets and returns the manifests. Using the output from the job, a user can review the packages before committing to build a new image.POST /composes/UUID/build
- queues a job that actually builds the manifest from the first step, and uploads it into a selected cloudIt's possible to build one compose multiple times - this can be useful to e.g. upload the image to different regions, or to recreate the image if it was deleted.
In multi-image composes, we agreed that it would be nice to be able to build the images separately - if a user passes e.g. a wrong account, it's not needed to build all of them again.
Beta Was this translation helpful? Give feedback.
All reactions