Tell os-client-config that tripleo doesn't have neutron

The TripleO cloud does not work when the neutron-based floating ip
logic creates a floating ip directly on a server port. The problem is
that the floating IP is correctly created and correctly associated with
the server, but Nova has no clue that this has happened, so GET calls to
/server do not show that the server has the floating IP. As that's the
way we track success, we can't use it. However, if a floating IP is
created using the nova proxy, it all works - so just configure the cloud
with "has_network: False" so that direct neutron interactions are not
attempted.

Change-Id: Idb90cad36feb99bc5aa19da4874ce97f868681c7
This commit is contained in:
Monty Taylor 2016-04-10 13:14:18 -05:00
parent 7d3981bcf4
commit 749babc4c7
No known key found for this signature in database
GPG Key ID: 3390DB68041A12F0
1 changed files with 1 additions and 0 deletions

View File

@ -37,6 +37,7 @@ clouds:
password: '<%= tripleo_password %>'
project_name: '<%= tripleo_project %>'
auth_url: 'https://ci-overcloud.rh1.tripleo.org:13000/v2.0'
has_network: False
bluebox-sjc1:
auth:
username: '<%= bluebox_username %>'