Add image for building base Tendermint instance

[thanethomson]

This adds the Packer/Ansible configuration to build an AMI that contains Tendermint (vanilla config), and includes Telegraf for monitoring. User data is used to configure Telegraf's InfluxDB backend.

[thanethomson]

Since the initial submission here, I've also added in a simple monitoring-only server (i.e. Grafana/InfluxDB), and the tm-bench AMI. These are all used in interchainio/testnets.

[greg-szabo]

Can we put all this under the whitewalker folder, as we discussed in the architecture? The images repo also hosts images unrelated to this experiment, so if we start adding a lot of images, we might want to break it out into its own repository.

Currently, we agreed that we'll have two images: nightking and whitewalker. The whitewalker image will turn into a tm-load-test client or a tendermint node based on its inputs.

We can do it differently, if that makes more sense. Let's discuss.

[thanethomson]

I'd say a better structure would probably be to group the related images, like:

_ got
   |_ nightking
   |_ whitewalker

The images I've been working on here are designed to be operated in a standalone way by anyone (internal or external). They're not specifically related to the GoT project, although I'll be taking parts of them and copying them into GoT.

The only thing that needs to be added to the tendermint and tmbench images would be SignalFX integration, and the ability to switch between InfluxDB and SignalFX.

Other than that, you can run the tendermint image on its own and it provides a simple, unconfigured Tendermint v0.31.7 AMI, ready to receive configuration and ready to submit its metrics to an InfluxDB instance.

The tmbench image is also ready to use, and just provides a simple, standalone AMI that can execute multiple sequential tm-bench requests using predefined parameters from user data.

[mircea-c]

@thanethomson can we close this? 🙂

[thanethomson]

Sure thing! Blast from the past 🙂