packet_net

Provision Humio on packet.net

Requirements

• packet.net account, including
  • Your packet.net API key
• Terraform
• Ansible

Getting started

Start by exporting your packet.net API KEY, as the following environment variables, i.e.

export PACKET_API_TOKEN=Bfse9F24SFtfs423Gsd3ifGsd43sSdfs
export TF_VAR_packet_auth_token=${PACKET_API_TOKEN}

Initialise the workspace

terraform init

Verify that the Terraform is able to communicate with packet

terraform validate
terraform refresh

Spinning up a new environment

The default configuration will spin up three nodes, all with

• Zookeeper
• Kafka
• Humio

To set up the environment run the following command

terraform apply

Verify the configuration and type yes into the console. After a while (usually around 5 minutes) you will have a new project in packet.net named Humio.

Provisioning Humio

First, make sure you have the required Ansible Galaxy roles installed

ansible-galaxy install --role-file=requirements.yml

Finally, the cluster can be provisioned with the site.yml playbook

ansible-playbook site.yml

Once the cluster is up and running, the Humio web interface should be available on TCP port 8080 of any of the hosts in the tag_humios group,

open http://$(./packet_net.py | jq -r '.tag_humios[0]'):8080