These jobs all need TLC and to be moved to the new ansible platform. For
now, we're removing them because if they accidentally get triggered,
they cost a lot of money very quickly, and don't necessarily get us
anything useful if they pass or fail.
Revert "Updating any AWS shape instance to use"
...our existing reserved instance types. This simply ensures if we ever
do run one of these tests it is against existing reserved instances. If
the tests get removed thats OK also."
This reverts commit 69be968d6d.
The idea behind this is to give AWS more information about what
instances we can let it actually instantitate, rather than have it be
one fixed instance type.
e.g., in this case, we are okay with any Graviton instance with at least
2 vCPU and 8 GiB memory.
The easist way to do that is to instead use a launch template, with
ec2_fleets or spot fleets.
I took out the part where we even support on-demand instances. This can
be readded later if it is necessary.
switch perf-able to using same node type we use for other spot instances,
because otherwise it never finds any available capacity.
we switch the perf-able script to use the standard get_value function
instead of direct jq calls.
we try to grab server logs if the restore fails in the hopes of finding
out why the restore very occasionally fails.
* spot instance test
* update outputs.tf to provide spot instances
* uptate outputs.tf data_node_ips
* propogate spot instance request tags to the instances
- terraform scripts to set up cluster
- cloud-formation scripts to set up cluster
- set up ingest node with kafka server and datagen
- set up second ingest node with molecula-consumer-kafka-static
- set up datadog in all nodes (ingest + featurebase)
- set up script to execute different queries
- only run delete test on schedule
