Somehow, one user can hijack the console of another user.Īll of the above problems don’t stand with WebMKS consoles. This creates a possibility for allocating the same VNC port toĭifferent instances and if these instances end up on the same ESXi host The same nova-compute but there is no way to do this between several Security - we can prevent race conditions for port allocations occurring on Needless to say, this doesn’t scale well. Instance and this is done by querying all allocated ports on the vCenter
Scalability - the Nova driver needs to allocate a unique VNC port for each That will be inaccessible to the cloud users. We rely only on the fact that all ESXi hosts will run on a private network The whole thing creates a huge security risk because Additionally, they need toĬreate and install a special VIB package for the firewall modifications to In the firewall configuration on each ESXi host. There are number of problems with the current approach which provides VNCĬonsoles to instances running on VMware hypervisors:ĭeployment - cloud operators need to open a huge range of ports (5900-6105)
Users will be encouraged to use WebMKS when possible. The existing support for VNC consoles will remain but This will solve some of theĬurrent problems that we have with VNC consoles with respect to deployment,
VSphere 5.5 and later (referred as WebMKS console). This is a proposal to add support for the native HTML5 console available in
0 kommentar(er)
