Page MenuHomeSoftware Heritage

Vagrantfile: Allow libvirt vm build
ClosedPublic

Authored by ardumont on Oct 4 2020, 1:20 PM.

Details

Summary

This adapts the README to describe the necessary tooling. And adds
a qemutest vm to use libvirt as provider (instead of vbox).

Runs fine as demonstrated in P802.

First iteration failed without the gpg dependency ~> P800 Thus why the
post-install.sh adds it directly as a workaround (in this diff).

Ideally, this should be added in our manifest somewhere or even better in the
puppet module which requires it but I don't know which one is pulling
it ¯\_(ツ)_/¯. In the mean time, that sounds reasonable.

Note: As P801 shows, it is not required for the vbox template and I don't know
why this worked for it.

Depends on D4137

Related to T2606

Test Plan
vagrant destroy qemutest --force; vagrant up qemutest

output: P802

Diff Detail

Repository
rSENV Puppet Environment
Branch
add-libvirt-support
Lint
Lint Skipped
Unit
Unit Tests Skipped
Build Status
Buildable 16146
Build 24840: arc lint + arc unit

Event Timeline

Vagrantfile
196 ↗(On Diff #14584)

details about the network already allowed for vbox which creates friction here...

200 ↗(On Diff #14584)

it's already automounted somehow by the libvirt provider...

Rebase

(P802 updated with successful run)

Note:

I found my "issue" (orally talked about last week). For vagrant-libvirt to
work, we need to use the vagrant version packaged in debian (doc updated with
that "detail"). Using a more recent version (hashicorp packaged vagrant, which
is more recent, this no longer works ¯\_(ツ)_/¯)

ardumont edited the test plan for this revision. (Show Details)
vsellier added inline comments.
Vagrantfile
244 ↗(On Diff #14914)

shouldn't be the global image used on the final version ?

This revision is now accepted and ready to land.Oct 12 2020, 3:37 PM
Vagrantfile
244 ↗(On Diff #14914)

yes, it should.

This revision was automatically updated to reflect the committed changes.