On Fri, Jun 1, 2018 at 9:04 PM Jonathan Lebon <jle...@redhat.com> wrote:
> On Fri, Jun 1, 2018 at 10:14 AM, arnaud gaboury > <arnaud.gabo...@gmail.com> wrote: > > So my idea is to "share" what I added in one machine (/etc settings and > > layered packages, let's call the machine "origin") to other machines > > (targeted VM) in an automatic way. > > It seems that articles about automate building atomic host[0] will > indeed do > > the trick. > > Note that blog post is about composing your own Atomic Host, instead of > building on top of what Fedora ships. If you look at the playbook, you > will see > that it does an `rpm-ostree rebase`, which switches you to the built > tree. So then, > e.g. `rpm-ostree upgrade` will not get you updates from Fedora > automatically; you'd > be maintaining your own stream of updates. There's a related issue > upstream about > making "layered" streams easier to create: > > https://github.com/projectatomic/rpm-ostree/issues/442 Honestly, I am lost :-( Not sure if I am on the right path, but I read papers on "build-atomic-host" like these ones[0],[1] or [2] ? Is it the way I shall go to deploy Atomic on all my VM in the cluster? [0]http://www.projectatomic.io/docs/compose-your-own-tree/ [1]https://github.com/trishnaguha/build-atomic-host [2]https://dustymabe.com/2017/10/05/setting-up-an-atomic-host-build-server/
