libvirt users - Jun 2013 - VMware distributed port groups..Supported?

Hi,

I installed libvirt on CentOS 6 today, only to find I could create the
volume, create the VM, but could not assign the interface to a distributed
port group. I then downloaded the latest source, compiled, and it looks to
be the same...unless its under a command I'm not recognizing?

Does anybody have the great tip that is going to set me free? I hope?

Everything we use is on the vSwitches, as we run 60-80 VLAN's to each
cluster member.

-- 
Thanks,
Morgan

To clarify, I'm communicating with a VMWare ESX cluster.

Thanks,
Morgan


On Sat, Jun 29, 2013 at 12:22 AM, Morgan McLean <wrx230@gmail.com> wrote:
> Hi,
>
> I installed libvirt on CentOS 6 today, only to find I could create the
> volume, create the VM, but could not assign the interface to a distributed
> port group. I then downloaded the latest source, compiled, and it looks to
> be the same...unless its under a command I'm not recognizing?
>
> Does anybody have the great tip that is going to set me free? I hope?
>
> Everything we use is on the vSwitches, as we run 60-80 VLAN's to each
> cluster member.
>
> --
> Thanks,
> Morgan
>


-- 
Thanks,
Morgan

On 06/29/2013 03:22 AM, Morgan McLean wrote:
> Does anybody have the great tip that is going to set me free? I hope?
Hi,

Distributed Port Groups come from the "vNetwork Distributed Switch"
(vDS); a feature of VMware vCenter.  You just can't throw a non-ESXi
hypervisor into your vCenter datacenter and expect it to work with their
proprietary technology.  The same way you just can't throw an ESXi into
oVirt (the open-source equivalent to vCenter) and expect it to have
access to all the defined networks at the datacenter level
(automatically).  AFAIK, we're not there yet.

I know VMware recently came out with their "vCenter Multi-Hypervisor
Manager" but it only supports Hyper-V and I don't think it integrates
with their vDS.
> Everything we use is on the vSwitches, as we run 60-80 VLAN's to each
> cluster member.
You could use Linux as the hypervisor but you'll have to manually
configure those VLANs and assign them to your VMs to be able to connect
to the VMs running on your vCenter (assuming they'll be sharing the same
layer-2 switch).

Since obviously you're using vCenter, isn't it more easier to add
another ESXi ?

HTH,
Jorge

...

So I thought this was very obvious, but this is a 100% VMware cluster.
Libvirt can communicate with esx.

I get the feeling nobody does this.

Morgan

On Sunday, June 30, 2013, Jorge Fábregas wrote:
> On 06/29/2013 03:22 AM, Morgan McLean wrote:
> > Does anybody have the great tip that is going to set me free? I hope?
>
> Hi,
>
> Distributed Port Groups come from the "vNetwork Distributed
Switch"
> (vDS); a feature of VMware vCenter.  You just can't throw a non-ESXi
> hypervisor into your vCenter datacenter and expect it to work with their
> proprietary technology.  The same way you just can't throw an ESXi into
> oVirt (the open-source equivalent to vCenter) and expect it to have
> access to all the defined networks at the datacenter level
> (automatically).  AFAIK, we're not there yet.
>
> I know VMware recently came out with their "vCenter Multi-Hypervisor
> Manager" but it only supports Hyper-V and I don't think it
integrates
> with their vDS.
>
> > Everything we use is on the vSwitches, as we run 60-80 VLAN's to
each
> > cluster member.
>
> You could use Linux as the hypervisor but you'll have to manually
> configure those VLANs and assign them to your VMs to be able to connect
> to the VMs running on your vCenter (assuming they'll be sharing the
same
> layer-2 switch).
>
> Since obviously you're using vCenter, isn't it more easier to add
> another ESXi ?
>
> HTH,
> Jorge
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users@redhat.com <javascript:;>
> https://www.redhat.com/mailman/listinfo/libvirt-users
>

-- 
Thanks,
Morgan