Arrange compute nodes in hostname order 66/67166/4
authorSam Hague <shague@redhat.com>
Fri, 12 Jan 2018 23:43:48 +0000 (18:43 -0500)
committerSam Hague <shague@redhat.com>
Tue, 16 Jan 2018 18:08:09 +0000 (13:08 -0500)
commit4231773cbac4e6b00a371f597f66c4fa8614305c
treee7ab01cea96b7988ea5658c9e4af592ac69fe36b
parentc792ef4c4c25a8ad8394ccbdf38b1c2ed60d9aa1
Arrange compute nodes in hostname order

The below is how a current job looks. Notice the CMP2_HOSTNAME with -0
maps to COMPUTE_2_IP and smae for the other vm. So we swap the
two HOSTNAME's and then they align with what is passed to pybot.
Without this, mentally when looking at debugs, you have to remember
to swap the two.

OS_CMP1_HOSTNAME: releng-17212-771-2-devstack-ocata-1.vexxhost.net -
OS_CMP1_IP: 10.30.170.121 - OS_COMPUTE_1_IP: 10.30.170.121
OS_CMP2_HOSTNAME: releng-17212-771-2-devstack-ocata-0.vexxhost.net -
OS_CMP2_IP: 10.30.170.13 - OS_COMPUTE_2_IP: 10.30.170.13

Change-Id: Ifab24ca30c24523f35591517338af7e9946d072e
Signed-off-by: Sam Hague <shague@redhat.com>
jjb/integration/integration-get-slave-addresses.sh