In order to run openstack commands from the Openstack Management Server Appliance: SSH and login to the Openstack Management Server as the user viouser. SSH to the controller VM using the command: ssh controller01 Go super user: sudo -s Source the cloudadmin.rc file: source /root/cloudadmin.rc Export the OS_PASSWORD environment variable, export OS_PASSWORD=xxxxx Run the Openstack cli commands, for eg. nova list
My VIO lab broke after a power failure. I powered on and brought back the vsphere infrastructure, Openstack Manager and the VIO VM’s, however I was unable to login to Openstack. So I decided to do a clean shut down/start up of the VIO deployment from the VIO plugin in the vsphere web client. The VIO deployment shut down fine. However, powering on the deployment failed with an error pointing to the DB-01 VM....
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/?...
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....
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....