Underlying CloudStack infrastructure actually does not prevent you from
creating a non-isolated guest network without a VLAN, making VLAN
mandatory for these networks is unfortunately posted at CloudStack
business layer, I think we should fix this problem to make people(like
Outback)'s life  easier.

Kelven  

On 8/13/12 7:02 PM, "Outback Dingo" <outbackdi...@gmail.com> wrote:

>ok we caved in and finally hijacked a vlan capable switch and
>reconfigured our whole environment to comply with CS and its
>requirements for vlans
>We literally reconfigured our whole environment to accommodate the
>forced use of VLANs by cloudstack for advanced networking. Everything
>prior
>ran perfectly with XCP and no VLANs, multi-homed systems, XCP hosts
>and all VMs had a public and a private interface, and backups worked
>fine.
>however adding CS, we have now had to reconfigure everything (65
>machines now require VLAN tags) ...... so consider us assimilated and
>trying to play nice
>it is currently to the point where we wish to configure XCP hosts and
>get them on the vlan...... to no avail.........
>Im sure someones configured XCP hosts for VLANs but we cant find
>anything other really then this
>
>http://ronnybull.com/2011/08/03/xen-cloud-platform-xcp-setting-up-a-vlan/
>
>which we tried and it doesnt appear to work..... after plugging the
>XCP host into a vlan 500 tagged port we couldnt ping the ip
>any hints on how to get past this blocker.............
>So close....... yet soooooooooooooo far..........

Reply via email to