Archive | Cloud Computing

VMware vCloud Director 1.0.1 was released for general availability yesterday. The release notes can be found by clicking here I will post further information when I return from PEX.

Working on my home lab today, I discovered that once you have imported a VM from vSphere and created the vApp there wasn’t an option to then import another VM into the same vApp. This really frustrated me as I wanted to import 4 VM’s into the same vApp in the cloud. The easy way I found to do this is as follows: 1) Import the second VM into a new vApp 2) Open up the vApp once the import has completed 3) Right click and select ‘Move To’ 4) Select the Destination vApp 5) Configure the VM Full Name, Computer Name and Networks 6) Check the Networking details 7) Click Finish That’s it, and now you have the second VM imported into the vApp. I really think we need an option within a vApp to import more than one VM, and will mention this next time there is a […]

Working on my home lab the other day, I had forgotten where the log files were kept for VMware vCloud Director. I thought I would document there location and what the purpose of these log files are for. Path to log files:/opt/vmware/cloud-director/logs UPDATE: Path to log files as of vCloud Director 1.5 changed to /opt/vmware/vcloud-director/logs cell.log The first log file that I always use, is the cell.log. This provides information on what status the cell services and application start up are at. Generally I use tail -f to view the live status when starting a vCD Cell. Application startup begins: 1/18/11 10:48 PM Successfully bound network port: 80 on host address: 192.168.10.152 Successfully bound network port: 443 on host address: 192.168.10.152 Application Initialization: 9% complete. Subsystem ‘com.vmware.vcloud.common.core’ started Successfully connected to database: jdbc:oracle:thin:@192.168.10.150:1521/xe Successfully bound network port: 443 on host address: 192.168.10.53 Successfully bound network port: 61616 on host address: […]

A customer of mine found this bug today and thought I would share it with you. I have not seen this error before, as generally most cloud deployments I have worked on have been using vCD-NI network pools When creating a vSphere port group backed network pool, when you go to configure the “Port Group backed pool” there is no VLAN-ID’s shown in any of the fields. As you can see from the second screenshot the Port group has a VLAN tag, so it is a bit of a bug not showing this.