Uninstall and cleanup VMware Integrated Openstack

Ran into a known bug and the solution was to completely uninstall and redeploy VMware Integrated Openstack. So how exactly do you uninstall and clean up a VMware Integrated Openstack install? Delete all VM’s deployed by VIO Delete all logical switches, edges and firewall rules that have been created in NSXv/Portgroups in dvSwitch Power off and delete the VIO vApp Unregister the VIO plugin from vCenter Server Login to the following URL, https://< vcenter server ip/FQDN>/mob/?...

May 14, 2015 · 1 min · Jahnin Rajamoni

vRealize Automation Infrastructure tab reports HTTP 503 error

I had setup vRealize Automation sometime back in a lab environment and this had been running fine for a few weeks. I started seeing the HTTP 503 error without much changes to the environment. From the logs on the vRA Appliance it looked like the IAAS machine did not respond to the status api call. - /var/log/vcac/catalina.out 2015-04-28 21:56:05,059 vcac: \[component="cafe:component-registry" priority="WARN" thread="registryServiceNotificationExecutor-21538" tenant=""\] org.springframework.web.client.RestTemplate.handleResponseE rror:581 - GET request for "https://iaas....

April 29, 2015 · 2 min · Jahnin Rajamoni

Messing around with instances in VMware Integrated Openstack

Setting up Openstack with VMware Integrated Openstack(VIO) and VMware NSXv is a breeze as compared to installing and configuring each Openstack component manually. I have been messing around with VIO since its early beta days and have been able to setup the enterprise ready Openstack more than a couple of times without any issues. As deploying VIO itself is quite easy, in this post I will walk through deploying instances in VIO with internal and external networks using the Horizon Dashboard....

April 3, 2015 · 5 min · Jahnin Rajamoni

VMware Integrated Openstack plugin is not visible in the vSphere Client after deploying the vApp

The /var/log/oms/oms.log shows the following error: [2015-03-26T02:07:22.358+0000] INFO localhost-startStop-1| com.vmware.aurora.vc.vcservice.VcService: Registering extension vService at: [https:///vsm/extensionService](https://192.168.0.30/vsm/extensionService) token=0c04c904607229dcd9e60f16872898adefbfbdb7 [2015-03-26T02:07:22.401+0000] ERROR localhost-startStop-1| com.vmware.aurora.vc.vcservice.VcService: Failed Extension registration to [https://vsm/extensionService](https://192.168.0.30/vsm/extensionService)javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: **No subject alternative names matching IP address found** So what does that error mean? The vcenter server ip/fqdn that was specified during the deployment of the VMware Integrated Openstack vAPP does not exist in the common name/subject alternate name of the vCenter Server’s certificate....

March 28, 2015 · 1 min · Jahnin Rajamoni

Failed to connect to server(code:1006)

I have been playing with VMware Integrated Openstack for the last couple of months. After installation I have been able to launch a couple of instances, create networks, create routers, etc. Everything works fine, however I was unable to launch the instance’s console from horizon; it failed every time with the error, "Failed to connect to server(code:1006)". I have been working around this by using the VM’s console from the vSphere client....

March 25, 2015 · 1 min · Jahnin Rajamoni