Lack of documentation about TCP ports used by TripleO Services
Bug #1714214 reported by
Ricardo Noriega
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Incomplete
|
Medium
|
Unassigned | ||
Bug Description
Developing a new service into TripleO we realized that its default port is already used by another service:
https:/
There is no documentation about used ports and it is really difficult to pick one up.
We should have a list of ports to avoid collisions.
| Changed in tripleo: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → queens-1 |
| Changed in tripleo: | |
| milestone: | queens-1 → queens-2 |
| Changed in tripleo: | |
| milestone: | queens-2 → queens-3 |
| Changed in tripleo: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in tripleo: | |
| milestone: | queens-rc1 → rocky-1 |
| Changed in tripleo: | |
| milestone: | rocky-1 → rocky-2 |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
| Changed in tripleo: | |
| milestone: | stein-2 → stein-3 |
Revision history for this message
| Juan Antonio Osorio Robles (juan-osorio-robles) wrote | #1 |
| Changed in tripleo: | |
| milestone: | stein-3 → train-1 |
| Changed in tripleo: | |
| milestone: | train-1 → train-2 |
| Changed in tripleo: | |
| milestone: | train-2 → train-3 |
| Changed in tripleo: | |
| milestone: | train-3 → ussuri-1 |
| Changed in tripleo: | |
| milestone: | ussuri-1 → ussuri-2 |
| Changed in tripleo: | |
| milestone: | ussuri-2 → ussuri-3 |
| Changed in tripleo: | |
| milestone: | ussuri-3 → ussuri-rc3 |
| Changed in tripleo: | |
| status: | Triaged → Incomplete |
| Changed in tripleo: | |
| milestone: | ussuri-rc3 → victoria-1 |
| Changed in tripleo: | |
| milestone: | victoria-1 → victoria-3 |
To post a comment you must log in.
This still seems to be an issue.