Come up with configuration options and instructions for running private Tor networks in testing and simulation environments
(Mostly re-using Roger's words for this ticket description.)
We should try to make TestingTorNetwork smoother and more reliable. That's useful for Shadow et al (Rob keeps running into bugs where his testbed network behaves funny due to TestingTorNetwork), and it would also be useful for setting up large private Tor networks for testing purposes.
#6752 (moved) is an example for problems with TestingTorNetwork. We'd probably find more such bugs if we spent some time running our own Tor networks and knowing how it's supposed to work.
Maybe this is best done by making Chutney better so we can notice problems, or maybe it's best done just by sitting down with a test Tor network, watching what goes wrong, fixing it, repeat.
The current status of Chutney is that it doesn't make any application requests to the Tor network it starts. It doesn't know how to check whether a Tor has bootstrapped correctly, has established a circuit, etc. Linus indicated that he might be interested in stabbing further at Chutney which he already did as part of the IPv6 work.