Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of outbackdingo@gmail.com
 designates 209.85.161.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALFpzo4GJNFbpwEU0DkT2-q1Sww55-jJ-DCcAcJHW8r-z59-CA@mail.gmail.com>
References: 
 <CAKYr3zz_w8xvWT-L5oUUmpfH4pxrHEefgHSuQ_AjM+KT2hJWTg@mail.gmail.com>
	<61AE1E2837A06D4A8E98B796183842D401292FF6B469@SJCPMAILBOX01.citrite.net>
	<CALFpzo4GJNFbpwEU0DkT2-q1Sww55-jJ-DCcAcJHW8r-z59-CA@mail.gmail.com>
Date: Wed, 8 Aug 2012 13:32:28 -0400
Message-ID: 
 <CAKYr3zzD74o=xveRndw3b5nF0SoTT35EunXKh68Jx62xinoLhQ@mail.gmail.com>
Subject: Re: VLANS in Advance Networking NOT NEEDED.
From: Outback Dingo <outbackdingo@gmail.com>
To: cloudstack-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Aug 7, 2012 at 9:05 PM, Marcus Sorensen <shadowsor@gmail.com> wrote:
> SDN is more or less an alternative for vlans, which he doesn't want to use
> anyway. He has separate network segments already.
>
> There isn't very much good documentation for cloudstack networking. I
> wanted to do something similar a few months back and ended up frustrated. I
> had vlans, but wanted my VMS to have a public interface on a shared network
> and a private interface on a shared network. In the GUI, you can only do
> isolated networks in advanced mode. Once I realized that I had to create my
> network through the API I realized that I could do pretty much whatever I
> wanted with advanced networking.
>
> Outback Dingo, you should be able to do what you want by explicitly setting
> the traffic labels to the bridge devices you want. Cloudstack *should* then
> forego trying to create a new tagged interface and bridge. You will have to
> also create a new shared networking offering through the api that only
> provides DHCP and userdata. Then create a new network with that offering,
> and VMs attached to that will work on your shared network. I know these are
> vague instructions but I'm away from the PC.

We have tried this and it seems that any attempt to create a shared
network offering fails with requiring a vlan