[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] replicate a fedora Atomic changes and layered packages to other machines

On Mon, Jun 4, 2018 at 4:22 PM Micah Abbott <miabbott redhat com> wrote:
On 06/02/2018 01:43 PM, arnaud gaboury wrote:
> Here is my situation.
> I have a cluster of 6 VM with all running Fedora 28 server. These VM are
> dedicated to become a Kubernetes HA cluster, each VM being a node with a
> specific role (etcd, worker or controler).
> Until now, the cluster was built with rancher but only a few workloads
> were deployed, mainly to test and learn.  So it is not yet production
> ready and can thus allow changes.
> When upgrading from fedora 27 to 28, I decided to try Atomic on one of
> my machine. What I saw was very exciting and thus decided to install
> Atomic on all the other VM.
> My host provider has Atomic 28 enabled, so installing a bare Atomic 28
> is easy and done by the provider. Now, I am looking for a simple and
> robust way to duplicate the changes I have done on my first machine to
> the others.
> What came to mind first is to rsync. But when looking at all the
> articles about atomic host build server, like these ones [0], [1],
> [2],[3] I wonder now what is  the proper way to go.
> I am looking for advises about how to achieve my goal.

I think the advice you are going to get depends on the kinds of changes
you want to duplicate across the multiple VMs.

For example, if you are just making config changes (i.e. editing files
in /etc), I'd suggest creating an Ansible playbook that can be used to
make the changes after the VMs have been started.

However, if you are trying to include new packages via `rpm-ostree
install`, you would probably be better served by creating your own
compose that includes these packages.

What this means is that you would have a new ostree compose based on
Fedora 28 Atomic Host, but it would also include these new packages you
would like to install.  You could start your VMs and then use
`rpm-ostree rebase` to point them to your new custom compose.

That's the way I will do as I changed some config files and installed new packages. So best seems to build my own ostree.

I will follow one of the cited guide.

Any of the posts you've linked below should help you along towards
creating your own custom compose.

> [0]http://www.projectatomic.io/docs/compose-your-own-tree/
> <http://www.projectatomic.io/docs/compose-your-own-tree/>
> [1]https://github.com/trishnaguha/build-atomic-host
> <https://github.com/trishnaguha/build-atomic-host>
> [2]https://dustymabe.com/2017/10/05/setting-up-an-atomic-host-build-server/
> <https://dustymabe.com/2017/10/05/setting-up-an-atomic-host-build-server/>
> [3]https://trishnag.wordpress.com/2017/03/27/customize-packages-for-atomic-host-ansible-automation/
> <https://trishnag.wordpress.com/2017/03/27/customize-packages-for-atomic-host-ansible-automation/>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]