open-port should support port ranges

Some services will even be designed to be dynamic and will need to expose a range, like a bittorent peer for instance.

Big +1 the wishlist'ing.

Just came across the need for this when setting up an FTP server on EC2 that requires a port range for passive transfers.

For now....

for p in `seq $range_start $range_end` ; do
    open-port "$i"
done

Which works but takes forever with any large range and ends up flooding output of 'juju status' with a line for every port in the range.

Copying this bug over to juju-core, as it still doesn't support ranges.