Comment 1 for bug 1233045

Once swift-dispersion-populate is run once, do we even want it to be able to run a second time? Running it twice, should in theory double the partition coverage required in the dispersion.conf file (is this desired behaviour) but as pointed out in this bug, there can be overlaps with partitions.

Could a potential solution here be to add an "--override" option to the swift-dispersion-populate tool which would remove all the containers/objects from the previous populate run and keep the coverage percentage consistent with the dispersion.conf file.

As an adition or alternative to this, a check could be added to the code where if "swift-dispersion-populate" has been run before, it will not populate again.