nova-libvirt.yaml vnc port range is very limited (port exhaustion)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Ben Nemec |
Bug Description
On my setup I have compute hosts with 32 physical cpu cores. Using the default cpu overcommit this allows me to run a lot of single vcpu instances on each node. I found this out while trying to test the cpu overcommit ratio:
Sympthom:
After spawning about 250 vms in 50 batches I tried to connect to the console of one of the later ones and failed - Failed to connect to server (code: 1006)
Trying to connect to one of the VMs from the first batch however succeeded.
What I figured out so far:
On https:/
Using the default allocation of 16:1, this range can easily be exhausted using single vcpu flavours on an octactore CPU, something that is not all that uncommon nowadays.
The result when this happens is that it is impossible to connect the horizon supplied console to any vm that is spawned with a vnc port above 5999
And a potential (short term) solution:
Given that the modern CPU architectures are becoming more and more biased towards multicore, with 20 cores becoming a familiar number, I propose expanding this port range.
My initial proposal would be to something closer to 1000 ports, but I would like other's opinions on this.
Changed in tripleo: | |
milestone: | none → pike-1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Fix proposed to branch: master /review. openstack. org/493585
Review: https:/