Feature #2980

Improve management of the VNC Port Range

Added by Tino Vázquez over 5 years ago. Updated over 3 years ago.

Status:ClosedStart date:06/12/2014
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:Release 5.0
Resolution:fixed Pull request:

Description

In VMs with ID 89


Related issues

Related to Feature #2475: Reserve a VNC port number Closed 11/19/2013

Associated revisions

Revision dacb61b1
Added by Ruben S. Montero over 3 years ago

feautre #2980: Add bitmap class to reserve VNC ports.

Revision d474ee4d
Added by Ruben S. Montero over 3 years ago

feature #2980: VNC Bitmap is part of the cluster Object

Revision b1b64e61
Added by Ruben S. Montero over 3 years ago

feature #2980: VirtualMachine get VNC port at deployment time

Revision ccfccb6d
Added by Ruben S. Montero over 3 years ago

feature #2980: get VNC port when the VM is deployed and release it when
the VM is undeployed, stopped or done

Revision 4c35a9fc
Added by Ruben S. Montero over 3 years ago

feature #2980: Fix bugs in BitMap class

Revision 9da66150
Added by Ruben S. Montero over 3 years ago

feature #2980: Release VNC port when VM is deleted. Update VM at DB when
port is assigned

Revision 784a4fc9
Added by Ruben S. Montero over 3 years ago

feature #2980: VNC port tracking. Includes a VNC bitmap for each cluster to
track the ports in use in the cluster and avoid port collision. VNC ports are
assigned when the VM is deployed and released when the VM is stopped, undeployed
or done.

Includes the following:
- 9da66150dc0e3dc2731518d8a215f9598696a999
- 4c35a9fcccf70cbe87d2947403ea815967e7b605
- ccfccb6d2fc40aa1c07eb994f37b8da4fb479082
- b1b64e61a39f4452c7ba00e581de42888e0e84a5
- d474ee4db9ed520bcae743d510be35b25ea988ed
- dacb61b1402da2ec309b6e79bdd285d0d11de84f

Revision 25169d49
Added by Ruben S. Montero over 3 years ago

feature #2980: Add comment to oned.conf

Revision 9c8d5e89
Added by Carlos Martín over 3 years ago

Feature #2980: Fix port assignment

Revision 574d0b7a
Added by Jaime Melis over 3 years ago

Feature #2980: Add VNC bitmap port migrator

Revision d6e69ea9
Added by Jaime Melis over 3 years ago

Feature #2980: Recalculate VNC ports in fsck

Revision c3550dcf
Added by Jaime Melis over 3 years ago

Feature #2980: Fix bug in VNC bitmap port migrator

Revision 86244bfc
Added by Jaime Melis over 3 years ago

Feature #2980: Fix bug in fsck affecting VNC bitmap ports

History

#1 Updated by Ruben S. Montero about 5 years ago

  • Assignee set to Carlos Martín

#2 Updated by Ruben S. Montero about 5 years ago

  • Tracker changed from Bug to Backlog
  • Subject changed from vCenter port clashes with VNC port to Improve management of the VNC Port Range
  • Status changed from New to Pending
  • Assignee deleted (Carlos Martín)
  • Priority changed from Normal to High
  • Target version deleted (Release 4.8)
This affects to:
  • vCenter port clashes with VNC port
  • VM ID clashes with a long-lived VM

#3 Updated by Ruben S. Montero over 4 years ago

#4 Updated by Ruben S. Montero over 3 years ago

  • Tracker changed from Backlog to Feature
  • Status changed from Pending to Closed
  • Target version set to Release 5.0
  • Resolution set to fixed

Also available in: Atom PDF