[dev.icinga.com #7645] Move Vagrant and Puppet related code to a dedicated repository

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/7645

Created by tgelf on 2014-11-11 23:24:52 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2015-03-31 09:54:43 +00:00 (in Redmine)

---

They are not required to run Icinga Web nor are they a great help in production. Vagrant helps to get a VM with sample-Daemons and config up and running. Puppet modules should know how to install Icinga Web to that box, nothing special here.

So I'd suggest to create a dedicated repository or to join efforts with icinga-vagrant.git.

Best,
Thomas

[icinga-migration]

Updated by mfriedrich on 2014-11-11 23:31:00 +00:00

+1 for icinga-vagrant.git - that's what this repository is all about, including the refactoring of generic puppet modules into git submodules used for all vagrant boxes. That's still an open task, but should be handled with care - neither breaking dev environments nor demo boxes.

[icinga-migration]

Updated by elippmann on 2015-03-31 09:54:43 +00:00

• Subject changed from Move Vagrant/Puppet stuff to a dedicated repo to Move Vagrant and Puppet related code to a dedicated repository
• Target Version set to Backlog

[lippserd]

No progress has been made here. I'll close this issue because it's very old and we have no plans to work on it in the near future. To be honest, we should remove this code completely and push Icinga docker containers instead.