Currently, we can mostly try and run most of the puppet manifests within vagrant.
This allows to exerce and catch early on issues.
We cannot do it yet for all pergamon related manifests.
As pergamon assumes a lot of roles (puppet master, icinga, grafana, annex, ...), this impedes the
feedback loop and the assurance we have when developing manifests related to those roles.
It'd be best if we could lift that limit.
Analysis started and summary is completed along the way in an hedgedoc draft [1]
[1] https://hedgedoc.softwareheritage.org/eOPFh5maS7q6TFEqQSj9nA?view
After some hard time with vagrant internal and pergamon configuration, we finally have a puppet master working.
The collected resources are well detected and applied, for example here, with the logstash0's incinga resources :
Notice: /Stage[main]/Profile::Icinga2::Master/Icinga2::Object::Host[pergamon.softwareheritage.org]/Icinga2::Object[icinga2::object::Host::pergamon.softwareheritage.org]/Concat[/etc/icinga2/zones.d/master/pergamon.softwareheritage.org.conf]/File[/etc/icinga2/zones.d/master/pergamon.softwareheritage.org.conf]/ensure: defined content as '{md5}e98c7cafc5300df8101f591d1c7a708b'
Info: Concat[/etc/icinga2/zones.d/master/pergamon.softwareheritage.org.conf]: Scheduling refresh of Class[Icinga2::Service]
Notice: /Stage[main]/Profile::Grafana::Vhost/Icinga2::Object::Service[grafana http redirect on pergamon.softwareheritage.org]/Icinga2::Object[icinga2::object::Service::grafana http redirect on pergamon.softwareheritage.org]/Concat[/etc/icinga2/zones.d/master/exported-checks.conf]/File[/etc/icinga2/zones.d/master/exported-checks.conf]/content: