Jonathan Lebon be3a677125 vmcheck: create a new deployment instead

In order for vmcheck to be useful for testing, we need the machine to be
in a "clean" state. That is, sitting on a commit, ready for being
manipulated.

This is a small step towards this goal. Instead of overwriting the
files, we use rofiles-fuse to safely install and create a new
deployment.

Closes: #321
Approved by: cgwalters

2016-06-15 13:38:34 +00:00

977 B

Raw Blame History

Using vmcheck

One time setup:

host$ vagrant up
host$ vagrant ssh
vm$ sudo rpm-ostree rebase centos-atomic-continuous:centos-atomic-host/7/x86_64/devel/continuous
vm$ sudo systemctl reboot

Though rebasing on CAHC is not strictly required, it will allow your code to make use of the most recent builds of projects to which rpm-ostree is tightly coupled, such as ostree and libhif.

If you need to test your code with custom ostree or libhif builds, you have no choice for now other than making your own tree (and yum repo for use by the build container). We're hoping to improve this workflow soon.

To synchronize source code on the host system, use:

vagrant rsync

To build and install into the VM:

host$ vagrant ssh
vm$ cd ~/sync/tests/vmcheck
vm$ make build
vm$ make install

At this point, a new deployment containing the new binaries is ready to be used. All that's left is to reboot:

vm$ sudo systemctl reboot

977 B Raw Blame History

Using vmcheck

977 B

Raw Blame History