You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by "Corey, Mike" <mi...@sap.com.INVALID> on 2021/09/01 12:52:56 UTC
RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
RE: Console Proxy & VMware 7
Posted by "Corey, Mike" <mi...@sap.com.INVALID>.
Wei,
I get what you are saying/implying. However, I'm going off what the error log is telling me regarding the SSL certificate issue using IP vs FQDN. See below snippet...
2021-08-31 13:00:58,366 INFO [cloud.consoleproxy.ConsoleProxyNoVncClient] (Thread-109:null) Connect to VNC over websocket URL: wss://10.x.x.x:443/ticket/a0155dcb1eaa3383
2021-08-31 13:00:58,383 ERROR [consoleproxy.websocket.WebSocketReverseProxy] (WebSocketConnectReadThread-154:null) Error on connection to websocket: No subject alternative names matching IP address 10.x.x.x found
2021-08-31 13:00:58,386 INFO [consoleproxy.websocket.WebSocketReverseProxy] (WebSocketWriteThread-155:null) Closing connection to websocket: reason= code=-1 remote=true
How else should I be deciphering the error log?
-----Original Message-----
From: Wei ZHOU <us...@gmail.com>
Sent: Tuesday, September 7, 2021 11:24 AM
To: users <us...@cloudstack.apache.org>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
The SSL certificate and wildcard domain name are configured in SSVM and
CPVM. These two systemvms are accessible from the internet.
However, each systemvm (CPVM, SSVM) has a management IP, the communication
between CPVM and hosts is over management networks which are internal. May
I ask why you want to use secure communication on an internal network ?
-Wei
On Tue, 7 Sept 2021 at 17:05, Corey, Mike <mi...@sap.com.invalid>
wrote:
> Thanks for providing the code - but I need a workaround as I need to prove
> out the full functionality of ACS with VMware for my organization. Secure
> console access is required and I don't understand why ACS would use IP
> instead of FQDN, especially since we are specifying the wildcard domain
> name in Global Settings and for the SSL certificate of the console.
>
> Is it as simple as changing the java code from "summary.getHostIp" to
> "summary.getHostName" or similar???
>
> I will put in the githup request today for this.
>
> Thanks!
>
> Mike
>
> From: Nicolas Vazquez <Ni...@shapeblue.com>
> Sent: Monday, September 6, 2021 8:29 AM
> To: Corey, Mike <mi...@sap.com>; David Jumani <
> David.Jumani@shapeblue.com>; users@cloudstack.apache.org
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mke,
>
> The websocket URL is created by CloudStack. The host parameter is being
> pulled from Vmware as the VM's running host IP (
> https://github.com/apache/cloudstack/blob/4.15.1.0/vmware-base/src/main/java/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java#L1137-L1154
> )
>
> I've not seen any work on improving it, can you please raise a new
> improvement request on https://github.com/apache/cloudstack/issues?
>
>
> Regards,
>
> Nicolas Vazquez
>
>
>
>
>
> ________________________________
> From: Corey, Mike <mi...@sap.com>>
> Sent: Friday, September 3, 2021 8:24 AM
> To: David Jumani <David.Jumani@shapeblue.com<mailto:
> David.Jumani@shapeblue.com>>; Nicolas Vazquez <
> Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>;
> users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: RE: Console Proxy & VMware 7
>
>
> Thank you both for the reply.
>
>
>
> Is there a plan to "fix" how the wss url is created so that it uses the
> host FQDN instead of IP address?
>
>
>
> Is this a NoVNC / websockify created url or ACS?
>
>
>
> The "host" parameter is being pulled from somewhere so it must be editable
> to use FQDN.
>
>
>
> Thanks!
>
>
>
>
>
>
>
> From: David Jumani <David.Jumani@shapeblue.com<mailto:
> David.Jumani@shapeblue.com>>
> Sent: Friday, September 3, 2021 12:52 AM
> To: Corey, Mike <mi...@sap.com>>;
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: Re: Console Proxy & VMware 7
>
>
>
> Hi Corey,
>
>
>
> +1 on what Nicolas has said since that's the way it works with the new
> vSphere 7 VNC Server removal.
>
>
>
> As for the workarounds, the best option is to change the SSL Certificate
> since an insecure console isn't a good idea. Setting novnc.console.default
> to false might not work since it still requires a WebSocket connection with
> vSphere 7 which might hit the same certificate issues.
>
>
>
>
>
> ________________________________
>
> From: Corey, Mike <mi...@sap.com>>
> Sent: Thursday, September 2, 2021 8:10 PM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; David
> Jumani <Da...@shapeblue.com>>
> Subject: RE: Console Proxy & VMware 7
>
>
>
> Thanks Nicolas,
>
> Yes, I saw that about VMware 7 and VNC support. Is there a config
> parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when
> creating the url instead of HOST IP?
>
> Otherwise the workaround options I see are:
>
> 1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com
> (have not done)
> 2 - Change console settings to go unsecured (non-ssl) (have not done,
> prefer not to be unsecure)
> 3 - Change novnc.console.default to false (have not tried)
>
> Any other options?
>
> Mike
>
> -----Original Message-----
> From: Nicolas Vazquez <Nicolas.Vazquez@shapeblue.com<mailto:
> Nicolas.Vazquez@shapeblue.com>>
> Sent: Thursday, September 2, 2021 9:42 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> David Jumani <David.Jumani@shapeblue.com<mailto:David.Jumani@shapeblue.com
> >>
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mike,
>
> Adding a few cents on the topic. Vmware has deprecated the VNC server in
> version 7 as explained in the 'Removal of VNC Server from ESXi' section in
> the release notes:
> https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html.
> To support it, CloudStack has been extended to acquire VM tickets and
> compose a websocket URL with the format:
> 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
>
> In that case <ESXI_HOST_IP> should support host FQDN as well which is a
> limitation at the moment
>
>
> Regards,
>
> Nicolas Vazquez
>
> ________________________________
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Thursday, September 2, 2021 9:34 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; David
> Jumani <Da...@shapeblue.com>>
> Subject: RE: Console Proxy & VMware 7
>
> Thank you for the reply.
>
> I don't know why NoVNC/ACS would use IP address of the host.
>
> The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources
> as FQDN.
>
> Hopefully David can provide more clarity on this and a solution so the
> console url is created with the FQDN of the host.
>
> MC
>
>
>
>
> -----Original Message-----
> From: Rohit Yadav <rohit.yadav@shapeblue.com<mailto:
> rohit.yadav@shapeblue.com>>
> Sent: Thursday, September 2, 2021 8:02 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> David Jumani <David.Jumani@shapeblue.com<mailto:David.Jumani@shapeblue.com
> >>
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mike,
>
> I think CloudStack creates the URL based on the IP address of the host, I
> don't remember if there's a way to override that unless the host is added
> with a FQDN in vCenter. Let me ping my colleague @David Jumani<mailto:
> David.Jumani@shapeblue.com> who has worked on the integration/feature for
> VMware7 to advise us.
>
>
> Regards.
>
> ________________________________
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Wednesday, September 1, 2021 18:22
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: RE: Console Proxy & VMware 7
>
> Hello Community,
>
> Is there anyone who might know how to make NoVNC or Websockify use FQDN
> instead of IP address of the host?
>
> Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has
> console access working?
>
> Many thanks for your input!
>
> Mike
>
>
>
>
> -----Original Message-----
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Monday, August 30, 2021 12:01 PM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: [CAUTION] RE: Console Proxy & VMware 7
>
> To add a little more context.
>
> In the cloud.log of the console proxy vm I see the error
> "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No
> subject alternative names matching IP address <ESXi host IP> found".
>
> My console proxy is setup using a wildcard SSL certificate. For example
> when I go to the console url provided in the management-server.log "Compose
> console url" (example: https://<public-IP>.<domain<https://%3cpublic-IP%3e.%3cdomain>
> suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>)
> my wildcard SSL cert is valid.
>
> I honestly don't know what the console proxy behavior was prior to the
> 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN
> for the ESXi host IP.
>
> Also, for the record, I did destroy and recreate the system VMs after the
> upgrades so they should be running the correct version of the system vms.
>
> Thanks!
>
> Mike
>
>
>
>
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Monday, August 30, 2021 10:51 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: [CAUTION] Console Proxy & VMware 7
>
> Hi,
>
> I am running ACS 4.15.1 and it was originally configured with ESXi 6.7
> hypervisor. I recently upgraded to ESXi 7 and have noticed that console
> proxy is no longer working.
>
> I CANNOT say for certain that the upgrade of the hypervisor caused this
> console proxy issue though. I CAN say that it was working in July (ESXi
> 6.7) - and the only change to the environment that I am aware of is the
> VMware upgrade to version 7.
>
> Could anyone out there verify they have console proxy access working with
> their VMware ESXi 7 hypervisor hosted VM instances???
>
> Many thanks!
>
> Mike
>
>
>
>
> Mike Corey
>
> Technology Senior Consultant, IT CS CTW Operation & Virtualization Service
> US
>
> SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United
> States
>
> T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<mailto:
> mike.corey@sap.com>
>
>
> [cid:image001.png@01D79D8C.E3CB4210]
>
Re: Console Proxy & VMware 7
Posted by Wei ZHOU <us...@gmail.com>.
Hi Mike,
The SSL certificate and wildcard domain name are configured in SSVM and
CPVM. These two systemvms are accessible from the internet.
However, each systemvm (CPVM, SSVM) has a management IP, the communication
between CPVM and hosts is over management networks which are internal. May
I ask why you want to use secure communication on an internal network ?
-Wei
On Tue, 7 Sept 2021 at 17:05, Corey, Mike <mi...@sap.com.invalid>
wrote:
> Thanks for providing the code - but I need a workaround as I need to prove
> out the full functionality of ACS with VMware for my organization. Secure
> console access is required and I don't understand why ACS would use IP
> instead of FQDN, especially since we are specifying the wildcard domain
> name in Global Settings and for the SSL certificate of the console.
>
> Is it as simple as changing the java code from "summary.getHostIp" to
> "summary.getHostName" or similar???
>
> I will put in the githup request today for this.
>
> Thanks!
>
> Mike
>
> From: Nicolas Vazquez <Ni...@shapeblue.com>
> Sent: Monday, September 6, 2021 8:29 AM
> To: Corey, Mike <mi...@sap.com>; David Jumani <
> David.Jumani@shapeblue.com>; users@cloudstack.apache.org
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mke,
>
> The websocket URL is created by CloudStack. The host parameter is being
> pulled from Vmware as the VM's running host IP (
> https://github.com/apache/cloudstack/blob/4.15.1.0/vmware-base/src/main/java/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java#L1137-L1154
> )
>
> I've not seen any work on improving it, can you please raise a new
> improvement request on https://github.com/apache/cloudstack/issues?
>
>
> Regards,
>
> Nicolas Vazquez
>
>
>
>
>
> ________________________________
> From: Corey, Mike <mi...@sap.com>>
> Sent: Friday, September 3, 2021 8:24 AM
> To: David Jumani <David.Jumani@shapeblue.com<mailto:
> David.Jumani@shapeblue.com>>; Nicolas Vazquez <
> Nicolas.Vazquez@shapeblue.com<ma...@shapeblue.com>>;
> users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: RE: Console Proxy & VMware 7
>
>
> Thank you both for the reply.
>
>
>
> Is there a plan to "fix" how the wss url is created so that it uses the
> host FQDN instead of IP address?
>
>
>
> Is this a NoVNC / websockify created url or ACS?
>
>
>
> The "host" parameter is being pulled from somewhere so it must be editable
> to use FQDN.
>
>
>
> Thanks!
>
>
>
>
>
>
>
> From: David Jumani <David.Jumani@shapeblue.com<mailto:
> David.Jumani@shapeblue.com>>
> Sent: Friday, September 3, 2021 12:52 AM
> To: Corey, Mike <mi...@sap.com>>;
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: Re: Console Proxy & VMware 7
>
>
>
> Hi Corey,
>
>
>
> +1 on what Nicolas has said since that's the way it works with the new
> vSphere 7 VNC Server removal.
>
>
>
> As for the workarounds, the best option is to change the SSL Certificate
> since an insecure console isn't a good idea. Setting novnc.console.default
> to false might not work since it still requires a WebSocket connection with
> vSphere 7 which might hit the same certificate issues.
>
>
>
>
>
> ________________________________
>
> From: Corey, Mike <mi...@sap.com>>
> Sent: Thursday, September 2, 2021 8:10 PM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; David
> Jumani <Da...@shapeblue.com>>
> Subject: RE: Console Proxy & VMware 7
>
>
>
> Thanks Nicolas,
>
> Yes, I saw that about VMware 7 and VNC support. Is there a config
> parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when
> creating the url instead of HOST IP?
>
> Otherwise the workaround options I see are:
>
> 1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com
> (have not done)
> 2 - Change console settings to go unsecured (non-ssl) (have not done,
> prefer not to be unsecure)
> 3 - Change novnc.console.default to false (have not tried)
>
> Any other options?
>
> Mike
>
> -----Original Message-----
> From: Nicolas Vazquez <Nicolas.Vazquez@shapeblue.com<mailto:
> Nicolas.Vazquez@shapeblue.com>>
> Sent: Thursday, September 2, 2021 9:42 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> David Jumani <David.Jumani@shapeblue.com<mailto:David.Jumani@shapeblue.com
> >>
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mike,
>
> Adding a few cents on the topic. Vmware has deprecated the VNC server in
> version 7 as explained in the 'Removal of VNC Server from ESXi' section in
> the release notes:
> https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html.
> To support it, CloudStack has been extended to acquire VM tickets and
> compose a websocket URL with the format:
> 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
>
> In that case <ESXI_HOST_IP> should support host FQDN as well which is a
> limitation at the moment
>
>
> Regards,
>
> Nicolas Vazquez
>
> ________________________________
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Thursday, September 2, 2021 9:34 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>; David
> Jumani <Da...@shapeblue.com>>
> Subject: RE: Console Proxy & VMware 7
>
> Thank you for the reply.
>
> I don't know why NoVNC/ACS would use IP address of the host.
>
> The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources
> as FQDN.
>
> Hopefully David can provide more clarity on this and a solution so the
> console url is created with the FQDN of the host.
>
> MC
>
>
>
>
> -----Original Message-----
> From: Rohit Yadav <rohit.yadav@shapeblue.com<mailto:
> rohit.yadav@shapeblue.com>>
> Sent: Thursday, September 2, 2021 8:02 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>;
> David Jumani <David.Jumani@shapeblue.com<mailto:David.Jumani@shapeblue.com
> >>
> Subject: Re: Console Proxy & VMware 7
>
> Hi Mike,
>
> I think CloudStack creates the URL based on the IP address of the host, I
> don't remember if there's a way to override that unless the host is added
> with a FQDN in vCenter. Let me ping my colleague @David Jumani<mailto:
> David.Jumani@shapeblue.com> who has worked on the integration/feature for
> VMware7 to advise us.
>
>
> Regards.
>
> ________________________________
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Wednesday, September 1, 2021 18:22
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <
> users@cloudstack.apache.org<ma...@cloudstack.apache.org>>
> Subject: RE: Console Proxy & VMware 7
>
> Hello Community,
>
> Is there anyone who might know how to make NoVNC or Websockify use FQDN
> instead of IP address of the host?
>
> Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has
> console access working?
>
> Many thanks for your input!
>
> Mike
>
>
>
>
> -----Original Message-----
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Monday, August 30, 2021 12:01 PM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: [CAUTION] RE: Console Proxy & VMware 7
>
> To add a little more context.
>
> In the cloud.log of the console proxy vm I see the error
> "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No
> subject alternative names matching IP address <ESXi host IP> found".
>
> My console proxy is setup using a wildcard SSL certificate. For example
> when I go to the console url provided in the management-server.log "Compose
> console url" (example: https://<public-IP>.<domain<https://%3cpublic-IP%3e.%3cdomain>
> suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>)
> my wildcard SSL cert is valid.
>
> I honestly don't know what the console proxy behavior was prior to the
> 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN
> for the ESXi host IP.
>
> Also, for the record, I did destroy and recreate the system VMs after the
> upgrades so they should be running the correct version of the system vms.
>
> Thanks!
>
> Mike
>
>
>
>
> From: Corey, Mike <mike.corey@sap.com.INVALID<mailto:
> mike.corey@sap.com.INVALID>>
> Sent: Monday, August 30, 2021 10:51 AM
> To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
> Subject: [CAUTION] Console Proxy & VMware 7
>
> Hi,
>
> I am running ACS 4.15.1 and it was originally configured with ESXi 6.7
> hypervisor. I recently upgraded to ESXi 7 and have noticed that console
> proxy is no longer working.
>
> I CANNOT say for certain that the upgrade of the hypervisor caused this
> console proxy issue though. I CAN say that it was working in July (ESXi
> 6.7) - and the only change to the environment that I am aware of is the
> VMware upgrade to version 7.
>
> Could anyone out there verify they have console proxy access working with
> their VMware ESXi 7 hypervisor hosted VM instances???
>
> Many thanks!
>
> Mike
>
>
>
>
> Mike Corey
>
> Technology Senior Consultant, IT CS CTW Operation & Virtualization Service
> US
>
> SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United
> States
>
> T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<mailto:
> mike.corey@sap.com>
>
>
> [cid:image001.png@01D79D8C.E3CB4210]
>
RE: Console Proxy & VMware 7
Posted by "Corey, Mike" <mi...@sap.com.INVALID>.
Thanks for providing the code - but I need a workaround as I need to prove out the full functionality of ACS with VMware for my organization. Secure console access is required and I don't understand why ACS would use IP instead of FQDN, especially since we are specifying the wildcard domain name in Global Settings and for the SSL certificate of the console.
Is it as simple as changing the java code from "summary.getHostIp" to "summary.getHostName" or similar???
I will put in the githup request today for this.
Thanks!
Mike
From: Nicolas Vazquez <Ni...@shapeblue.com>
Sent: Monday, September 6, 2021 8:29 AM
To: Corey, Mike <mi...@sap.com>; David Jumani <Da...@shapeblue.com>; users@cloudstack.apache.org
Subject: Re: Console Proxy & VMware 7
Hi Mke,
The websocket URL is created by CloudStack. The host parameter is being pulled from Vmware as the VM's running host IP (https://github.com/apache/cloudstack/blob/4.15.1.0/vmware-base/src/main/java/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java#L1137-L1154)
I've not seen any work on improving it, can you please raise a new improvement request on https://github.com/apache/cloudstack/issues?
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com>>
Sent: Friday, September 3, 2021 8:24 AM
To: David Jumani <Da...@shapeblue.com>>; Nicolas Vazquez <Ni...@shapeblue.com>>; users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Subject: RE: Console Proxy & VMware 7
Thank you both for the reply.
Is there a plan to "fix" how the wss url is created so that it uses the host FQDN instead of IP address?
Is this a NoVNC / websockify created url or ACS?
The "host" parameter is being pulled from somewhere so it must be editable to use FQDN.
Thanks!
From: David Jumani <Da...@shapeblue.com>>
Sent: Friday, September 3, 2021 12:52 AM
To: Corey, Mike <mi...@sap.com>>; users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: Re: Console Proxy & VMware 7
Hi Corey,
+1 on what Nicolas has said since that's the way it works with the new vSphere 7 VNC Server removal.
As for the workarounds, the best option is to change the SSL Certificate since an insecure console isn't a good idea. Setting novnc.console.default to false might not work since it still requires a WebSocket connection with vSphere 7 which might hit the same certificate issues.
________________________________
From: Corey, Mike <mi...@sap.com>>
Sent: Thursday, September 2, 2021 8:10 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thanks Nicolas,
Yes, I saw that about VMware 7 and VNC support. Is there a config parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when creating the url instead of HOST IP?
Otherwise the workaround options I see are:
1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com (have not done)
2 - Change console settings to go unsecured (non-ssl) (have not done, prefer not to be unsecure)
3 - Change novnc.console.default to false (have not tried)
Any other options?
Mike
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>>
Sent: Thursday, September 2, 2021 9:42 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain<https://%3cpublic-IP%3e.%3cdomain> suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
Re: Console Proxy & VMware 7
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
Hi Mke,
The websocket URL is created by CloudStack. The host parameter is being pulled from Vmware as the VM's running host IP (https://github.com/apache/cloudstack/blob/4.15.1.0/vmware-base/src/main/java/com/cloud/hypervisor/vmware/mo/VirtualMachineMO.java#L1137-L1154)
I've not seen any work on improving it, can you please raise a new improvement request on https://github.com/apache/cloudstack/issues?
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com>
Sent: Friday, September 3, 2021 8:24 AM
To: David Jumani <Da...@shapeblue.com>; Nicolas Vazquez <Ni...@shapeblue.com>; users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Thank you both for the reply.
Is there a plan to “fix” how the wss url is created so that it uses the host FQDN instead of IP address?
Is this a NoVNC / websockify created url or ACS?
The “host” parameter is being pulled from somewhere so it must be editable to use FQDN.
Thanks!
From: David Jumani <Da...@shapeblue.com>
Sent: Friday, September 3, 2021 12:52 AM
To: Corey, Mike <mi...@sap.com>; users@cloudstack.apache.org
Subject: Re: Console Proxy & VMware 7
Hi Corey,
+1 on what Nicolas has said since that's the way it works with the new vSphere 7 VNC Server removal.
As for the workarounds, the best option is to change the SSL Certificate since an insecure console isn't a good idea. Setting novnc.console.default to false might not work since it still requires a WebSocket connection with vSphere 7 which might hit the same certificate issues.
________________________________
From: Corey, Mike <mi...@sap.com>>
Sent: Thursday, September 2, 2021 8:10 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thanks Nicolas,
Yes, I saw that about VMware 7 and VNC support. Is there a config parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when creating the url instead of HOST IP?
Otherwise the workaround options I see are:
1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com (have not done)
2 - Change console settings to go unsecured (non-ssl) (have not done, prefer not to be unsecure)
3 - Change novnc.console.default to false (have not tried)
Any other options?
Mike
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>>
Sent: Thursday, September 2, 2021 9:42 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain<https://%3cpublic-IP%3e.%3cdomain> suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
RE: Console Proxy & VMware 7
Posted by "Corey, Mike" <mi...@sap.com.INVALID>.
Thank you both for the reply.
Is there a plan to "fix" how the wss url is created so that it uses the host FQDN instead of IP address?
Is this a NoVNC / websockify created url or ACS?
The "host" parameter is being pulled from somewhere so it must be editable to use FQDN.
Thanks!
From: David Jumani <Da...@shapeblue.com>
Sent: Friday, September 3, 2021 12:52 AM
To: Corey, Mike <mi...@sap.com>; users@cloudstack.apache.org
Subject: Re: Console Proxy & VMware 7
Hi Corey,
+1 on what Nicolas has said since that's the way it works with the new vSphere 7 VNC Server removal.
As for the workarounds, the best option is to change the SSL Certificate since an insecure console isn't a good idea. Setting novnc.console.default to false might not work since it still requires a WebSocket connection with vSphere 7 which might hit the same certificate issues.
________________________________
From: Corey, Mike <mi...@sap.com>>
Sent: Thursday, September 2, 2021 8:10 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thanks Nicolas,
Yes, I saw that about VMware 7 and VNC support. Is there a config parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when creating the url instead of HOST IP?
Otherwise the workaround options I see are:
1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com (have not done)
2 - Change console settings to go unsecured (non-ssl) (have not done, prefer not to be unsecure)
3 - Change novnc.console.default to false (have not tried)
Any other options?
Mike
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>>
Sent: Thursday, September 2, 2021 9:42 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>; David Jumani <Da...@shapeblue.com>>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org> <us...@cloudstack.apache.org>>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain<https://%3cpublic-IP%3e.%3cdomain> suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org<ma...@cloudstack.apache.org>
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
Re: Console Proxy & VMware 7
Posted by David Jumani <Da...@shapeblue.com>.
Hi Corey,
+1 on what Nicolas has said since that's the way it works with the new vSphere 7 VNC Server removal.
As for the workarounds, the best option is to change the SSL Certificate since an insecure console isn't a good idea. Setting novnc.console.default to false might not work since it still requires a WebSocket connection with vSphere 7 which might hit the same certificate issues.
________________________________
From: Corey, Mike <mi...@sap.com>
Sent: Thursday, September 2, 2021 8:10 PM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>
Subject: RE: Console Proxy & VMware 7
Thanks Nicolas,
Yes, I saw that about VMware 7 and VNC support. Is there a config parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when creating the url instead of HOST IP?
Otherwise the workaround options I see are:
1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com (have not done)
2 - Change console settings to go unsecured (non-ssl) (have not done, prefer not to be unsecure)
3 - Change novnc.console.default to false (have not tried)
Any other options?
Mike
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>
Sent: Thursday, September 2, 2021 9:42 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
RE: Console Proxy & VMware 7
Posted by "Corey, Mike" <mi...@sap.com.INVALID>.
Thanks Nicolas,
Yes, I saw that about VMware 7 and VNC support. Is there a config parameter that I can change for ACS/NoVNC/WebSockify to use FQDN when creating the url instead of HOST IP?
Otherwise the workaround options I see are:
1 - Change my SSL wildcard cert to IP and/or domain 10.* or *.domain.com (have not done)
2 - Change console settings to go unsecured (non-ssl) (have not done, prefer not to be unsecure)
3 - Change novnc.console.default to false (have not tried)
Any other options?
Mike
-----Original Message-----
From: Nicolas Vazquez <Ni...@shapeblue.com>
Sent: Thursday, September 2, 2021 9:42 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
Re: Console Proxy & VMware 7
Posted by Nicolas Vazquez <Ni...@shapeblue.com>.
Hi Mike,
Adding a few cents on the topic. Vmware has deprecated the VNC server in version 7 as explained in the 'Removal of VNC Server from ESXi' section in the release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html. To support it, CloudStack has been extended to acquire VM tickets and compose a websocket URL with the format: 'wss://<ESXi_HOST_IP>:443/ticket/<TICKET_ID>' to connect to the console.
In that case <ESXI_HOST_IP> should support host FQDN as well which is a limitation at the moment
Regards,
Nicolas Vazquez
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Thursday, September 2, 2021 9:34 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>; David Jumani <Da...@shapeblue.com>
Subject: RE: Console Proxy & VMware 7
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
RE: Console Proxy & VMware 7
Posted by "Corey, Mike" <mi...@sap.com.INVALID>.
Thank you for the reply.
I don't know why NoVNC/ACS would use IP address of the host.
The ESXi hosts are in vCenter by FQDN and added to the ACS Zone resources as FQDN.
Hopefully David can provide more clarity on this and a solution so the console url is created with the FQDN of the host.
MC
-----Original Message-----
From: Rohit Yadav <ro...@shapeblue.com>
Sent: Thursday, September 2, 2021 8:02 AM
To: users@cloudstack.apache.org; David Jumani <Da...@shapeblue.com>
Subject: Re: Console Proxy & VMware 7
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]
Re: Console Proxy & VMware 7
Posted by Rohit Yadav <ro...@shapeblue.com>.
Hi Mike,
I think CloudStack creates the URL based on the IP address of the host, I don't remember if there's a way to override that unless the host is added with a FQDN in vCenter. Let me ping my colleague @David Jumani<ma...@shapeblue.com> who has worked on the integration/feature for VMware7 to advise us.
Regards.
________________________________
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Wednesday, September 1, 2021 18:22
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: RE: Console Proxy & VMware 7
Hello Community,
Is there anyone who might know how to make NoVNC or Websockify use FQDN instead of IP address of the host?
Is there anyone out there who is running VMware 7 with ACS 4.15.1 who has console access working?
Many thanks for your input!
Mike
-----Original Message-----
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 12:01 PM
To: users@cloudstack.apache.org
Subject: [CAUTION] RE: Console Proxy & VMware 7
To add a little more context.
In the cloud.log of the console proxy vm I see the error "(WebSocketConnectReadThread-124:null)Error on connection to websocket: No subject alternative names matching IP address <ESXi host IP> found".
My console proxy is setup using a wildcard SSL certificate. For example when I go to the console url provided in the management-server.log "Compose console url" (example: https://<public-IP>.<domain suffix>/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows<https://%3cpublic-IP%3e.%3cdomain%20suffix%3e/resource/noVNC/vnc.html?autoconnect=true&port=8080&token=jBwbg4....guest=windows>) my wildcard SSL cert is valid.
I honestly don't know what the console proxy behavior was prior to the 4.15.1 or ESXi 7 upgrades. I don't understand why it is looking for a SAN for the ESXi host IP.
Also, for the record, I did destroy and recreate the system VMs after the upgrades so they should be running the correct version of the system vms.
Thanks!
Mike
From: Corey, Mike <mi...@sap.com.INVALID>
Sent: Monday, August 30, 2021 10:51 AM
To: users@cloudstack.apache.org
Subject: [CAUTION] Console Proxy & VMware 7
Hi,
I am running ACS 4.15.1 and it was originally configured with ESXi 6.7 hypervisor. I recently upgraded to ESXi 7 and have noticed that console proxy is no longer working.
I CANNOT say for certain that the upgrade of the hypervisor caused this console proxy issue though. I CAN say that it was working in July (ESXi 6.7) - and the only change to the environment that I am aware of is the VMware upgrade to version 7.
Could anyone out there verify they have console proxy access working with their VMware ESXi 7 hypervisor hosted VM instances???
Many thanks!
Mike
Mike Corey
Technology Senior Consultant, IT CS CTW Operation & Virtualization Service US
SAP AMERICA, INC. 3999 West Chester Pike, Newtown Square, 19073 United States
T +1 610 661 0905, M +1 484 274 2658, E mike.corey@sap.com<ma...@sap.com>
[cid:image001.png@01D79D8C.E3CB4210]