It is feasible, if purely from CloudStack API perspectives, following
steps may help you get there (I didn't really try it in CloudStack UI
though)

1) Create 2 physical networks, in each of these physical networks, add a
guest traffic label, label it to vSwitch2, also tag the physical network,
say, one as DEV, the other one as MGMT
2) Create 2 network service offering, tag the service offering the same as
corresponding physical network, so that when a network is created, it can
direct CloudStack to find the right physical network configuration for
mapping
3) Create 2 shared networks, specify the VLAN you are going to assign
along with a corresponding network offering
4) Deploy guest VM into the selected shared network

Kelven 

On 11/6/12 2:30 PM, "Musayev, Ilya" <imusa...@webmd.net> wrote:

>I promise to document this setup if I can get this to work successfully -
>so other folks like myself don't have to ask the same question twice :)
>
>-----Original Message-----
>From: Musayev, Ilya [mailto:imusa...@webmd.net]
>Sent: Tuesday, November 06, 2012 5:23 PM
>To: cloudstack-dev@incubator.apache.org
>Subject: Advanced network setup with CS and VSphere 5 - is this feasible?
>
>I have a vSphere cluster with 3 nodes I'd like to add to CS
>
>Since we are not using AWS like structure and more of an old fashioned
>typical corporate setup, I'm curious if its at all doable.
>
>My Setup as follows:
>
>3 vSphere hypervisors with following network setup
>
>                vSwitch0 - 2 NON-TRUNKED NICs associated
>                                Management Network No VLAN TAGGING IP
>Range 10.0.1.x/24
>
>                vSwitch 2 - 2 TRUNKED NICs associated
>                                DEV VLAN VLAN TAG ID 1000
>                                                IP Range 10.0.2.x/23
>
>                                MGMT VLAN VLAN TAG ID 1100 IP Range
>10.0.1.x/24 (same as above vSwitch0)
>
>The above is a sample VSPhere architecture I have for Developers Cluster,
>
>The goal is to be able to deploy VMs on both networks - DEV VLAN and MGMT
>VLAN by using Projects or Domains and associating it with CS TAGs.
>
>I tried diving in to advanced networking, but cant seem to get it to work
>right no matter what I try. Hence I'm reaching out for help here.
>
>Pretext:
>I don't use dVs in this setup since CS does not yet support dVs. For sake
>of simplicity - this is a completely new zone. The management nodes of CS
>must reside on MGMT VLAN on vSwitch2.
>
>As always, your feedback is appreciated,
>
>Thanks
>ilya
>

Reply via email to