Icinga Vagrant Boxes

Vagrant boxes,包括 Icinga 2, Icinga Web 2, modules, themes,并集成了 Graphite、InfluxDB、Elastic、Graylog 等等。【 Vagrant boxes for Icinga 2, Icinga Web 2, modules, themes and integrations (Graphite, InfluxDB, Elastic, Graylog, etc.) 】

Github stars Tracking Chart

Icinga Vagrant Boxes

Table of Contents

  1. About
  2. License
  3. Support
  4. Requirements
  5. Installation
  6. Configuration
  7. FAQ
  8. Authors
  9. Contributing

About

The Icinga Vagrant boxes allow you to run Icinga 2, Icinga Web 2 and integrations
(Graphite, InfluxDB, Grafana, Elastic Stack, Graylog) in various scenarios.

A simple vagrant up fully installs these VMs and you are ready to explore
the Icinga ecosystem and possible integrations.

You can use these boxes for your own local demos, or to learn how to use Icinga
in your environment. The Puppet provisioner uses official upstream modules
including puppet-icinga2 and puppet-icingaweb2.

Overview

Below are some sample screenshots. Keep in mind that software is under steady
development, so screenshots and features may change.

Visualization

Metrics

Logs and Events

Certificates

Dashboards and Themes

License

Box specific code is licensed under the terms of the GNU General Public License Version 2, you will find a copy of this license in the LICENSE file included in the source package.

Included Puppet modules in the .puppet/modules directory provide their own license details.

Support

These boxes are built for demos and development tests only. Team members and partners
may use these for their Icinga Camp presentations or any other event too.

Join the Icinga community channels for questions.

Note

Boxes can run snapshot builds and unstable code to test the latest and the greatest.

You can also use them to test Icinga packages prior to the next release.

In case you've found a problem or want to submit a patch, please open an issue
on GitHub and/or create a PR.

Requirements

One of these virtualization providers:

Each Vagrant box setup requires at least 2 Cores and 2 GB RAM.
The required resources are automatically configured during the
vagrant up run.

Note

OpenStack VMs are provisioned remotely in your cloud provider.
Please continue here for a full documentation.

Optional:

Linux

VirtualBox

Example on Fedora (needs RPMFusion repository for VirtualBox):

sudo dnf install vagrant
sudo dnf install virtualbox
vagrant plugin install virtualbox

Fedora uses libvirt by default. More details on VirtualBox can be found here.

Example on Ubuntu:

$ sudo apt-get install vagrant
$ sudo apt-get install virtualbox

libvirt

libvirt uses NFS for shared folders in the VMs, nfs_udp: false is already set.

nfs3 needs to be enabled in your local firewall to allow connections.

# firewall-cmd --permanent --add-service=nfs3
# firewall-cmd --reload

macOS

macOS runs best with the Parallels provider, VirtualBox works as well.

Windows

Windows requires VirtualBox as provider. You'll also need the Git package which includes SSH.

Install the Git package and set autocrlf to false.

You can also set the options on the command line afterwards:

C:\Users\michi> git.exe config --global core.autocrlf false

Set the Windows command line as default:

Note

If vagrant up hangs with Vagrant 2.0.0 on Windows 7, you might need to upgrade your Powershell
version. See this note for details.

Providers

Choose one of the providers below. VirtualBox can be used nearly everwhere. If
you have a Parallels Pro license on macOS, or prefer to use libvirt, that's possible
too.

Virtualbox

If Virtualbox is installed, this will be enabled by default.

The Virtualbox provider uses the bento base box.

Parallels

You'll need to install the vagrant-parallels
plugin first:

$ vagrant plugin install vagrant-parallels

The Parallels provider uses the bento base box.

VMware

Both VMware Workstation and the Vagrant plugin require their own license.

The Vagrant plugin installation is described here.

The VMware provider uses the bento base box.

Libvirt

You should have qemu and libvirt installed if you plan to run Vagrant on your local system. Then install the vagrant-libvirt` plugin:

$ vagrant plugin install vagrant-libvirt

The libvirt provider uses the official CentOS base boxes.

Installation

Linux

$ git clone https://github.com/Icinga/icinga-vagrant && cd icinga-vagrant

Change into the directory of the scenario and start the box(es).

$ cd standalone
$ vagrant up

Proceed here for an overview about all available boxes.

Windows

Clone this repository:

C:\Users\michi\Documents> git.exe clone https://github.com/Icinga/icinga-vagrant

Change into the directory of the scenario and start the box(es).

Proceed here for an overview about all available boxes.

Boxes

Each setup comes with the following basic tools installed:

Additionally, specific integrations, tools and modules are prepared for each
scenario.

Standalone

Run Vagrant:

$ cd standalone && vagrant up

Application Interfaces

Application

Overview

Name With OwnerIcinga/icinga-vagrant
Primary LanguageRuby
Program languageRuby (Language Count: 12)
PlatformLinux, Windows
License:GNU General Public License v2.0
Release Count9
Last Release Namev2.2.0 (Posted on )
First Release Namev1.0.0 (Posted on 2015-07-26 20:25:55)
Created At2014-03-31 19:58:46
Pushed At2022-06-11 01:04:16
Last Commit At2020-10-12 17:00:11
Stargazers Count249
Watchers Count30
Fork Count83
Commits Count1.1k
Has Issues Enabled
Issues Count92
Issue Open Count5
Pull Requests Count101
Pull Requests Open Count1
Pull Requests Close Count17
Has Wiki Enabled
Is Archived
Is Fork
Is Locked
Is Mirror
Is Private
To the top