docker performs slow registry port discovery (/w containers list) on each spawn/snapshot/etc
Bug #1286171 reported by
Erica Windisch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| nova-docker |
Invalid
|
Low
|
Erica Windisch | ||
Bug Description
While the docker registry port is most likely to be static for any given host during the runtime of the compute service, the registry port is rediscovered on every spawn/snapshot/etc.
While it is possible that the registry container might be relaunched and the port moved, the impact of performing extra list_containers calls is probably not worth it, especially considering that in most cases the code will fallback to the 'default registry port', or that the deployer will choose a static port by launching the registry with '-p 5042:5000'
| Changed in nova: | |
| status: | New → Confirmed |
Revision history for this message
| Erica Windisch (ewindisch) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → Low |
| assignee: | nobody → Eric Windisch (ewindisch) |
| status: | Confirmed → In Progress |
| affects: | nova → nova-docker |
Revision history for this message
| Erica Windisch (ewindisch) wrote | #2 |
| Changed in nova-docker: | |
| status: | In Progress → Invalid |
To post a comment you must log in.
https:/