vSphere iSCSi not support VM Cluster? - datastore

I'm building a virtual machine cluster using vSphere 5.1.
I'm finding solution for data storage.
I want iSCSi but when I see information on vsphere documentation I see with iSCSi vSphere don't supports "VM Cluster" but supports HA and DRS. I known HA only enable when create a "Cluster (Host cluster)".
I don't know exactly "VM Cluster" is what.
Please help me explain different of "VM Cluster" and "Host Cluster".
Thanks a lot!

a "VM Cluster" would be a cluster of two virtual machines running Windows MSCS for example. This "VM Cluster" would run on the ESXi hypervizor hosts, or a "Host Cluster".
A "Host Cluster" is a cluster of 2 or more physical machines running ESXi.
The table you found tells you you can't do any form of VM clustering when using Native iSCSI (the ESXi iSCSI initiator) on the ESXi hosts.
You can however do Host clustering using native iSCSI. No problem. Just don't do VM clustering when you use Native iSCSI.
Check http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959 for more info

When you create the iSCSI target, you must check the "Allow multiple concurrent iSCSI connections (Clustering)" option

Related

Deploying Apache Cloudstack with vSphere/vCenter

For a group project in one of my university IT classes, each group is given 3 servers and the professor wants us to get an Apache CloudStack environment running using those three. While initially vague on instructions, he later informed us that we should install the ESXi hypervisor on all 3 of our servers and go from there.
We first installed ESXi on all 3 of our servers. Then we installed vCenter server on one of them in order to combine all the computing resources by adding each as a host in a cluster before we start setting up CloudStack. What we are about to do next is install the CloudStack Management server on a VM created in vCenter server.
I was reading the CloudStack documentation before we start the installation which is where my question stems from. The documentation mentions that a host should not have any running VMs on them before getting added to CloudStack. Here is the exact text:
Ideally clusters that will be managed by CloudStack should not contain any other VMs. Do not run the management server or vCenter on the cluster that is designated for CloudStack use. Create a separate cluster for use of CloudStack and make sure that they are no VMs in this cluster.
So my question is, does that include the management server VM? If it does, would that mean we have to make a separate cluster for just the host server that contains the management server? Cause if that's the case, we can't use any of the other resources on that server that is running the management server. Or does it mean that you can but it's just not recommended?
On top of that, the documentation also mentions the following:
Put all target ESXi hypervisors in dedicated clusters in a separate Datacenter in vCenter.
So would I have to put the ESXi host containing vCenter Server and CloudStack Management Server in both a separate datacenter and cluster?

expose virtualbox vm to network

I have set up several ubuntu VMs using virtualbox. Right now I'm using network type as NAT and have access to it from the host machine, but what are the network changes that are needed to access these VMs through putty from other machines that are connected to the same network(wifi) ?
figured it out myself, first turn off the VM.
- enable two network adapters
- 1) host only - to connect between host and guest machines
- 2) Bridged network - to expose the vm to the network and assign ip address for each vm through dhcp
note: In my case I used vagrant tool to spin up my VMs, hence assigned fixed private ip to each vm,by enabling host only..I could do a headless start and then log in to VMs through putty(using fixed private ip) and get the dynamic bridge network ip.

How bosh set the vm network in vsphere environment?

I am learning the bosh and cloudfoundry , I am curiosity about the vm network setting in the vsphere.
How the bosh setup the network (ip, gateway) for the vm in the vsphere. i know the bosh will fire a bosh-agent/nats-agent in the target vm to change the value, but how it first connect to the agent ?
because i am not familiar with go, ruby , so cannot figure out the code .
https://bosh.io/docs/vsphere-cpi.html explains interactions with VSphere, and related bosh configuration.
How the bosh setup the network (ip, gateway) for the vm in the vsphere.
Are you looking to understand how to configure bosh, or how the CPI interacts with vsphere?
The docs above answer the first part. As for how bosh CPI operates under the cover is uses the vsphere/SDK APIS documented here, https://www.vmware.com/support/developer/vc-sdk/visdk41pubs/ApiReference/index-methods.html

VirtualBox on Freenas vm

I have a FreeNAS vm running in ESXi 6. I have installed VirtualBox jail on FreeNAS and assigned it a static IP.
I can ping that IP from shell in FreeNAS, but not from any of my other virtual machines.
They are all on the same subnet.
What can I try to fix this?
Firstly, FreeNAS should not be installed within a VM environment especially for production systems. This is also mentioned repeatedly on FreeNAS support and forums. I hope you are just conducting testing.
Back to your question, have you checked your firewalls / routing on your ESXi VMs, VB VMs, FreeNAS? I haven't tried this particular configuration before but typically its incorrect network settings that prevent pings. Have you tried dynamic IP?

VM Communicating with Another VM

I have two separate VMs created with VMWare Fusion. One is running Windows 7. The other is running Centos. I have an application on the Centos VM that needs to communicate with resources on the Windows VM. Does anyone know how I can setup communication between the VMs?
Your Fusion virtual machines all get IP addresses from DHCP by default. So, just use what you would to get resources if they were different machines.