-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
8
-
False
-
None
-
False
-
OCPSTRAT-1188 - MCO: move image update path to bootc
-
-
-
MCO Sprint 255, MCO Sprint 256
-
0
-
0.000
Several discussions have happened on the question : is Go binding for bootc a necessity for adapting a bootc update path in the MCO?
-
- Discussion: Currently, bootc does not have go binding which will make it hard to read its status and deployment. It seems that we will need to create a Go library for client side interactions with bootc (similar to: https://github.com/coreos/rpmostree-client-go) Colin has suggested a way to auto-generate it (see comment in https://issues.redhat.com/browse/MCO-1026), which would be the most ideal solution. Workarounds should also be available, making go binding a non-goal item for this enhancement.
- Result: Go bindings for bootc is not a must and, as a result, will be outside of the scope of this enhancement and will not be implemented. The main purpose of creating go bindings for rpm-ostree/bootc is to have an easier way to parse the created json and to read the status of rpm-ostree/bootc. This can be done via creating a simple wrapper function inside of the MCO. It will make sense to separate it out to a standalone helper/library in the future when the demand raises, but is a non-goal for now.
- split from
-
MCO-1184 Investigate the implementation plan of the bootc update path
- Closed
- links to