![]() ![]() Existing installation are working as is but the settings should be changed manually in the apps. The Splunk Platform Automator Framework does taking care of this automatically when Splunk version 9.x or higher is installed. The Base Config Apps habe been changed and need to be updated and some apps have been renamed. With Splunk 9.x some configuration terms have been renamed and are considered deprecated. After the upgrade and building of your splunk_config.yml, you can check the new inventory with the ansible-inventory command and compare it with your dump from version 1.x.To upgrade your Splunk Platform Automator, just update your local code from the repo Create an AWS security group and name it for example 'Splunk_Basic' and add the following TCP portsĮxample Basic AWS Security Group 'Splunk_Basic' Inbound Rules Type.Create an ssh key pair described here and store the public key on your disk for later reference in the config file.Add AWS_SECRET_ACCESS_KEY= as environment variable.Add AWS_ACCESS_KEY_ID= as environment variable. ![]() Generate AWS ACCESS Keys, described here.Download the vagrant dummy box for aws: vagrant box add aws-dummy.The last working version of vagrant is 2.3.4 The plugin is not maintained anymore and has issues with newer vagrant versions on OSX. Install the aws vagrant plugin: vagrant plugin install vagrant-aws.Install and configure AWS support (optional) Your directory structure should now look like this:Įxport VAGRANT_WSL_ENABLE_WINDOWS_ACCESS="1"Įxport PATH="$PATH:/mnt/c/Program Files/Oracle/VirtualBox" If you have a Splunk License file, link it to the name Splunk_Enterprise.lic inside the Software directory.Download Splunk Professional Services Best Practices Base Config Apps and extract them into the Software directory.archive for the Splunk Software and put in the Software directory Download and extract a Splunk Platform Automator release here or clone from GitHub when using the master branch: git clone.Create a folder called Vagrant and change into it.For supported Ansible versions check here Install Ansible, I personally prefer Brew (on OSX) which makes it as easy as brew install ansible.Is you are using the AWS plugin, see version hints here If not available for your distro, you can build your own Python version. Make sure you have Python 3.6+ installed.The Framework is currently tested on Mac OSX and Linux, but any other Unix, which is supported by Virtualbox, should work too. Implemented changes are to be found in the Changelog Installation See the upcoming features in the Roadmap Changelog Developed and tested on MacOSX but should support Linux as well.Can deploy Splunk on existing hosts (virtual or physical).Currently supports Virtualbox or AWS Cloud.Virtual hosts can be created by Vagrant.Deployment and configuration done with Ansible.Example configuration files for different setups included.Splunk environment definition stored in one simple yaml file.Configuration done according best practices with configuration apps.Building Cluster Manager, Indexer Clusters, Deployer, Search Head Clusters, Deployment Server, Universal Forwarders, Heavy Forwarders, License Manager and Monitoring Console.Build complex, reproducible Splunk environments in one shot, including all roles available for Splunk Enterprise.I am developing this on best effort in my spare time. Note: This framework is not officially supported by Splunk. Create vitualenv for specific Ansible version.Run Ansible playbooks to deploy and configure the Splunk software.Building Windows Virtual Machine Template.Migrate Environments where ansible only is used.Migrate existing Splunk Platform Automator Environments from 1.x to 2.x.Example Basic AWS Security Group 'Splunk_Basic'.Install and configure AWS support (optional). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |