IPv4 address sorting is nonsensical

[Nicolas Simonds]

Horizon uses the default IP address sorter provided with jquery-tablesorter, which was apparently written by throwing tennis balls at a keyboard from across the room and saving the results. It gets things preposterously wrong.

To Reproduce:

1. Create a bunch of VMs on a large-ish network, say a /23 or /21
2. Sort the Instances DataTable by IP address

Expected Behavior:

Sensible sorting by IP address.

Actual Behaviour:

Hilarity ensues. Screenshot attached.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/107140

[Thai Tran (tqtran)]

Nick's fix seems to not work. Where is the reason why that might be.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/107140
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=7b68ebe2e34ed9d0a1ea0672721c397b9d3f4106
Submitter: Jenkins
Branch: master

commit 7b68ebe2e34ed9d0a1ea0672721c397b9d3f4106
Author: Nicolas Simonds <email address hidden>
Date: Tue Jul 15 11:25:14 2014 -0700

    Add a proper IPv4 sorter for jquery-tablesort

    The default implementation provided with tablesorter uses a busted
    regex and nonsensical formatter. Add an explicit IPv4 parser/formatter
    to Horizon and use it instead.

    Closes-Bug: 1342266
    Change-Id: I13c709f6171f8e7214b8a3ef15ddf441806df4c2