Page MenuHomeSoftware Heritage

Vagrant environment to test puppet locally
ClosedPublic

Authored by vsellier on Sep 16 2020, 6:28 PM.

Diff Detail

Repository
rSENV Puppet Environment
Branch
vagrant
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 15367
Build 23665: arc lint + arc unit

Event Timeline

I think this should be moved to the sysadm-provisioning repository [1] instead.

[1] https://forge.softwareheritage.org/source/swh-sysadmin-provisioning/

I think this should be moved to the sysadm-provisioning repository [1] instead.

[1] https://forge.softwareheritage.org/source/swh-sysadmin-provisioning/

No, I think a puppet-specific thing like this should definitely be in the puppet repository.

In D3967#98011, @olasd wrote:

I think this should be moved to the sysadm-provisioning repository [1] instead.

[1] https://forge.softwareheritage.org/source/swh-sysadmin-provisioning/

No, I think a puppet-specific thing like this should definitely be in the puppet repository.

I agree with @olasd as it will be used by a Vagrantfile defining the configuration of the vms and using the puppet repository to provision them. It's highly coupled with the puppet repository.
If in the future it will be possible to provision a local environment via terraform, it will make sense.

the iso is available on the public annex at this url : https://annex.softwareheritage.org/public/isos/virtualbox/debian/

The next step is to add some doc about the iso creation and the vagrant usage.

prefix the preseed file by the debian version name

add vagrant usage documentation

vsellier retitled this revision from Create the virtualbox image used to instantiate the vagrant environment to Vagrant environment to test puppet locally.Sep 18 2020, 2:54 PM
Add vagrant configuration and documentation

cool.

Thanks for adding some documentation about how to use it ;).

I don't know what's the current state of the diff is (I see quite a lot of commented code, don't know if you want to merge it like this or not, e.g. Vagrantfile).

fyi, you can mark the diff as "planned changes" in the selection box "Add Action" at the bottom of the page (if you have some changes remaining.

Note to self: I definitely need to try this out, that looks nice ;)

README.md
216

with:

:)

Fix plenty of " :" ;)

I don't know what's the current state of the diff is (I see quite a lot of commented code, don't know if you want to merge it like this or not, e.g. Vagrantfile).

I just discover there is still an issue with the network interfaces not configured after a restart of a vm. IMO we can wait for this problem to be solved before landing the diff.

Update the base image to use ethX interfaces

This revision is now accepted and ready to land.Sep 22 2020, 4:24 PM
  • declare site.pp to override the default puppet entrypoint
  • add the inventory vm
  • Add a script to avoid to commit each change before being able to test it (watch-vagrant-conf)
  • Update the documentation accordingly
  • Declare the admin-inventory server

Switch the default test branch to staging