A conversation with some users indicated a couple pain points we can easily address:
The README uses an --expected-traffic of 1 Gbps, which results in a large installation. We should use a smaller number for that example.
Users expect cluster-destroy to destroy everything and are surprised when it doesn't. It is un-obvious to them that they need to supply the --destroy-everything flag to get that behavior. Per @awick suggestion, we can address by adding a --retain-traffic-data flag and requiring users to supply one of the two flags.
Description
A conversation with some users indicated a couple pain points we can easily address:
--expected-traffic
of 1 Gbps, which results in a large installation. We should use a smaller number for that example.cluster-destroy
to destroy everything and are surprised when it doesn't. It is un-obvious to them that they need to supply the--destroy-everything
flag to get that behavior. Per @awick suggestion, we can address by adding a--retain-traffic-data
flag and requiring users to supply one of the two flags.