cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <>
Subject Re: vSwitch vs bridge
Date Thu, 15 Aug 2013 18:18:14 GMT
The system vms need a public network, so at least 2 "public" Ips.

On 8/15/13 11:14 AM, "Carlos Reategui" <> wrote:

>Thanks for the response.
>I am a complete novice when it comes to VLANs so hopefully I can pull this
>off.  My hosts/guest physical network is using a Dell PowerConnect 2848
>which says it supports VLAN tags so I'll look at its docs to see what I
>need to do to configure it.
>You mention that the guest and public traffic must be tagged.  Since I
>not be using public IPs (or the notion of a public network) can I skip the
>public network or do I need to define it?  My network is
>already NATed out if the guests need outbound access to the internet.
> Inbound internet traffic is not available.
>On Wed, Aug 14, 2013 at 9:41 PM, Venkata SwamyBabu Budumuru <
>> wrote:
>> Currently CS supports security groups functionality only with bridge
>> networking mode.
>> If you are ok with out security groups  then with advanced shared you
>> be able to achieve what you are looking for. Advanced shared expects
>> tagged VLANs for guest and public traffic types.
>> On 15/08/13 5:35 AM, "Carlos Reategui" <> wrote:
>> >Hi All,
>> >
>> >The Cloudstack docs for XenServer say to use bridge networking when
>> >basic networking.  Is this still the case with CS 4.1 and XS 6.1?
>> >
>> >XS 6.1 introduced LACP which I would prefer to use but it is not
>> >with bridge networking.  I think my storage network would benefit from
>> >
>> >If still required for basic networking then can someone walk me through
>> >how
>> >to setup an advanced network that behaves like a basic, shared, no
>> >security
>> >group network.  I have 8 nics in 2 bonds (4 nics each -- one labeled
>> >storage for NFS SR and the other cloud-public for management/guest
>> >traffic).  The hosts and the guests are in and the
>> >network is isolated on its own in a
>> >
>> >thanks,
>> >Carlos

View raw message