Skip to content

Stands up an entire Vagrant Environment with 1 Master Node, 3 Search heads in a Cluster, and 3 Indexers in a Cluster.

License

Notifications You must be signed in to change notification settings

optionalg/Vagrant_Splunk_Cluster

 
 

Repository files navigation

Let's use vagrant to auto-provision a Splunk Clustered Environment.

  • 1 Master Node
  • 3 Indexers
  • 3 Search Heads

#How-To

First, install Vagrant and Virtualbox (but this could probably use whatever Vagrant has hooks for).

This was built with Vagrant 1.7.2 and Virtualbox 4.2.3.

Simply run init.sh. This takes about 15 minutes on my machine. The virtual machines use an internal network to communicate with each other, but can also communicate to the outside if needed. The subnet is 10.10.50.0/24. You can access each individual machine using its corresponding port based by IP. In other terms, if the machine IP is 10.10.50.130, the local port to access it is 50130. Any number from 50130-5139 is reserved for any other port that may be needed on that machine. These systems are Cent OS 7 (x64) running Splunk 6.2.3. This can be changed by editing the local variables at the top of the Vagrantfile. Each VM can be ssh'd into using the command "vagrant ssh ". In the list below, each is the first bullet point. master, idx1, idx2, etc.

The license is a Trial License, so License Master will not work until you grant a valid license.

The Vagrantfile will stand up the entire Indexer Cluster, Search Head Cluster, and Master Node, and configure each as needed.

The credentials for all systems are: admin/superS3cr3t.

#REQUIREMENTS:

  • vagrant
  • virtualbox

#Run time: real 14m25.687s user 0m22.346s sys 0m10.949s

About

Stands up an entire Vagrant Environment with 1 Master Node, 3 Search heads in a Cluster, and 3 Indexers in a Cluster.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Shell 100.0%