Hello all,
As part of my work on the Atomic SIG I'd like to begin building candidate/testing system images in the CBS using the process I outlined in an earlier mail to this list.
Doing this requires that I use an updated version of the Anaconda installer and give it access to rpm-ostree "composes". Both of these elements need a public (or at least visible to the CBS builders) http location.
In the case of the Fedora Atomic SIG, we've been able to host in-progress work in the "alt" area of the primary download server here:
http://dl.fedoraproject.org/pub/alt/fedora-atomic/
Is there something similar we can arrange for CentOS Atomic content?
-Ian
One thing to note here is the traditional model is:
Lorax(rpms) -> boot.iso ImageFactory(boot.iso, kickstart, rpms) -> cloud image
With Atomic image composes there is an intermediate step:
Lorax(rpms) -> boot.iso rpm-ostree(rpms, treefile) -> ostreerepo ImageFactory(boot.iso, kickstart, ostreerepo) -> cloud image
The model is the ostreerepo can be consumed by clients in the same way that RPMs can, but it means there's another step.
On 13/11/14 21:20, Ian McLeod wrote:
Hello all,
As part of my work on the Atomic SIG I'd like to begin building candidate/testing system images in the CBS using the process I outlined in an earlier mail to this list.
Doing this requires that I use an updated version of the Anaconda installer and give it access to rpm-ostree "composes". Both of these elements need a public (or at least visible to the CBS builders) http location.
In the case of the Fedora Atomic SIG, we've been able to host in-progress work in the "alt" area of the primary download server here:
http://dl.fedoraproject.org/pub/alt/fedora-atomic/
Is there something similar we can arrange for CentOS Atomic content?
we likely can, but will need to workout scope and how it works. We dont really cater to something of this nature, out of the box, at this time.
-
Colin Walters -
Ian McLeod -
Karanbir Singh