cannot run tempest against internal_url endpoint
Bug #1178083 reported by
June Yi
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Wishlist
|
Jordan Pittier |
Bug Description
Sometimes, it is needed to deploy Tempest internally. (i.e. some cloud service does not open their image service endpoint to public.)
Currently, endpoint_url is hard coded as 'publicURL'. It will be better to make it configurable.
description: | updated |
tags: | added: low-hanging-fruit |
Changed in tempest: | |
status: | Triaged → Confirmed |
importance: | Low → Wishlist |
Changed in tempest: | |
assignee: | nobody → Jordan Pittier (jordan-pittier) |
Changed in tempest: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
The default value of this option should be None, and tempest should fall back to the endpoint definitions by default.