New vCloud DIrector 8.10 (read eight dot ten) is out and with it some little neat features. Let me quickly talk about one of them – the ability to run vCloud Director cell with just 1 IP address.

In the past you always had to configure vCloud Director cell at least with two IP addresses. One for the web interface (providing UI and API) and the other for remote console proxy. The reason was that both services shared the same port 443. In vCloud Director 8.10 there is possibility to specify ports for each service and thus use just one IP address. This helps if your DMZ subnet is too small and you need to deploy more VMs into that network (more cells, databases, etc.).

Note that the configure script will not ask you for ports, instead you need to use unattended installation option or add port entries afterward in global.config file.

Unattended Installation

Here is the example of configure parameters that sets console proxy to the same IP address as http (10.0.1.60) and uses port 8443 instead of the standard 443:



/opt/vmware/vcloud-director/bin/configure" -cons 10.0.1.60 --console-proxy-port-https 8443 -ip 10.0.1.60 --primary-port-http 80 –-primary-port-https 443 -dbhost 10.0.4.195 -dbport 1433 -dbtype sqlserver -dbinstance MSSQLSERVER -dbname vcloud -dbuser vcloud -dbpassword 'VMware1!' -k /opt/vmware/vcloud-director/etc/certificates.ks -w 'passwd' -loghost 10.0.4.211 -logport 514 -g --enable-ceip true -unattended



Global Properties

An alternative option is to edit the /opt/vmware/vcloud-director/etc/global.properties file and add new port entries:

Before:



...

product.version = 8.10.0.3879706

product.build_date = 2016-05-12T20:32:07-0700

vcloud.cell.ip.primary = 10.0.1.60

consoleproxy.host.https = 10.0.1.61

...



After



...

product.version = 8.10.0.3879706

product.build_date = 2016-05-12T20:32:07-0700

vcloud.cell.ip.primary = 10.0.1.60

consoleproxy.host.https = 10.0.1.60

consoleproxy.port.https = 8443

vcloud.http.port.standard = 80

vcloud.http.port.ssl = 443

...



Do not forget to reconfigure your loadbalancer remote console pool to point to the new IP-port combination.