root@no:~/piyushv/vic# ./vic-machine-linux create -t 192.161.227.55 -u 'Administrator@vsphere.local' -p 'Admin!23' -r VIC -i nfs-ds -b Compute_VDS-Mgmt -n vic-ch --no-tlsverify --insecure-registry 192.161.227.64 --thumbprint 29:43:43:E8:E6:F8:7E:BA:99:EB:D9:F6:DF:0A:29:2E:5A:95:88:C7 May 22 2017 01:12:20.417-07:00 INFO ### Installing VCH #### May 22 2017 01:12:20.417-07:00 WARN Using administrative user for VCH operation - use --ops-user to improve security (see -x for advanced help) May 22 2017 01:12:20.419-07:00 INFO Loaded server certificate vic-ch/server-cert.pem May 22 2017 01:12:20.419-07:00 WARN Configuring without TLS verify - certificate-based authentication disabled May 22 2017 01:12:20.638-07:00 INFO Validating supplied configuration May 22 2017 01:12:20.832-07:00 INFO vDS configuration OK on "Compute_VDS-Mgmt" May 22 2017 01:12:21.050-07:00 INFO Firewall status: DISABLED on "/Datacenter/host/Compute Cluster/192.161.227.51" May 22 2017 01:12:21.081-07:00 WARN Firewall configuration on "/Datacenter/host/Compute Cluster/192.161.227.51" may prevent connection on dst 2377/tcp outbound with allowed IPs: [192.161.227.60] May 22 2017 01:12:21.115-07:00 INFO Firewall status: DISABLED on "/Datacenter/host/Compute Cluster/192.161.227.53" May 22 2017 01:12:21.129-07:00 WARN Firewall configuration on "/Datacenter/host/Compute Cluster/192.161.227.53" may prevent connection on dst 2377/tcp outbound with allowed IPs: [192.161.227.60] May 22 2017 01:12:21.156-07:00 INFO Firewall status: DISABLED on "/Datacenter/host/Compute Cluster/192.161.227.54" May 22 2017 01:12:21.172-07:00 WARN Firewall configuration on "/Datacenter/host/Compute Cluster/192.161.227.54" may prevent connection on dst 2377/tcp outbound with allowed IPs: [192.161.227.60] May 22 2017 01:12:21.204-07:00 INFO Firewall status: DISABLED on "/Datacenter/host/Compute Cluster/192.161.227.52" May 22 2017 01:12:21.216-07:00 WARN Firewall configuration on "/Datacenter/host/Compute Cluster/192.161.227.52" may prevent connection on dst 2377/tcp outbound with allowed IPs: [192.161.227.60] May 22 2017 01:12:21.216-07:00 WARN Unable to fully verify firewall configuration due to DHCP use on management network May 22 2017 01:12:21.216-07:00 WARN VCH management interface IP assigned by DHCP must be permitted by allowed IP settings May 22 2017 01:12:21.216-07:00 WARN Firewall configuration may be incorrect if firewall is reenabled on hosts: May 22 2017 01:12:21.216-07:00 WARN "/Datacenter/host/Compute Cluster/192.161.227.51" May 22 2017 01:12:21.216-07:00 WARN "/Datacenter/host/Compute Cluster/192.161.227.53" May 22 2017 01:12:21.216-07:00 WARN "/Datacenter/host/Compute Cluster/192.161.227.54" May 22 2017 01:12:21.216-07:00 WARN "/Datacenter/host/Compute Cluster/192.161.227.52" May 22 2017 01:12:21.216-07:00 INFO Firewall must permit dst 2377/tcp outbound to the VCH management interface if firewall is reenabled May 22 2017 01:12:21.414-07:00 INFO License check OK on hosts: May 22 2017 01:12:21.414-07:00 INFO "/Datacenter/host/Compute Cluster/192.161.227.51" May 22 2017 01:12:21.414-07:00 INFO "/Datacenter/host/Compute Cluster/192.161.227.53" May 22 2017 01:12:21.414-07:00 INFO "/Datacenter/host/Compute Cluster/192.161.227.54" May 22 2017 01:12:21.414-07:00 INFO "/Datacenter/host/Compute Cluster/192.161.227.52" May 22 2017 01:12:21.424-07:00 INFO DRS check OK on: May 22 2017 01:12:21.424-07:00 INFO "/Datacenter/host/Compute Cluster" May 22 2017 01:12:21.461-07:00 INFO May 22 2017 01:12:21.918-07:00 INFO Creating virtual app "vic-ch" May 22 2017 01:12:22.185-07:00 INFO Creating appliance on target May 22 2017 01:12:22.209-07:00 INFO Network role "client" is sharing NIC with "public" May 22 2017 01:12:22.209-07:00 INFO Network role "management" is sharing NIC with "public" May 22 2017 01:12:32.319-07:00 INFO Uploading images for container May 22 2017 01:12:32.320-07:00 INFO "bootstrap.iso" May 22 2017 01:12:32.320-07:00 INFO "appliance.iso" May 22 2017 01:13:01.030-07:00 INFO Waiting for IP information May 22 2017 01:14:46.755-07:00 INFO Waiting for major appliance components to launch May 22 2017 01:14:47.022-07:00 INFO Obtained IP address for client interface: "192.161.227.67" May 22 2017 01:14:47.022-07:00 INFO Checking VCH connectivity with vSphere target May 22 2017 01:14:49.789-07:00 INFO vSphere API Test: https://192.161.227.55 vSphere API target responds as expected May 22 2017 01:14:58.890-07:00 INFO Initialization of appliance successful May 22 2017 01:14:58.890-07:00 INFO May 22 2017 01:14:58.890-07:00 INFO VCH Admin Portal: May 22 2017 01:14:58.891-07:00 INFO https://192.161.227.67:2378 May 22 2017 01:14:58.891-07:00 INFO May 22 2017 01:14:58.891-07:00 INFO Published ports can be reached at: May 22 2017 01:14:58.892-07:00 INFO 192.161.227.67 May 22 2017 01:14:58.892-07:00 INFO May 22 2017 01:14:58.892-07:00 INFO Docker environment variables: May 22 2017 01:14:58.892-07:00 INFO DOCKER_HOST=192.161.227.67:2376 May 22 2017 01:14:58.893-07:00 INFO May 22 2017 01:14:58.893-07:00 INFO Environment saved in vic-ch/vic-ch.env May 22 2017 01:14:58.894-07:00 INFO May 22 2017 01:14:58.894-07:00 INFO Connect to docker: May 22 2017 01:14:58.894-07:00 INFO docker -H 192.161.227.67:2376 --tls info May 22 2017 01:14:58.895-07:00 INFO Installer completed successfully