Hi, I suppose that i have to use advance networking zone, since there are two nics and vlans to be used in the one of them.
On Tue, Apr 15, 2014 at 4:10 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote: > Are you going to use simple or advanced networking zone? > > > > > Pierre-Luc Dion > Architecte de Solution Cloud | Cloud Solutions Architect > 855-OK-CLOUD (855-652-5683) x1101 > - - - > > *CloudOps*420 rue Guy > Montréal QC H3J 1S6 > www.cloudops.com > @CloudOps_ > > > On Tue, Apr 15, 2014 at 8:55 AM, Konstantinos Karampogias < > konstantinos.karampog...@centralway.com> wrote: > >> This is not a lab, it is a rented server in a datacenter, therefore i >> have restricted access to the network components. >> >> I have defined the network labels (which are the name of the bridges >> in the hypervisor) accordingly >> root@ch1-cskvm-1:~# brctl show |grep cs >> cs-guest 8000.001e67a0a1f7 no eth1 >> <-- Guest Traffic >> cs-mgmt 8000.001e67a0a1f7 no eth1.849 >> cs-public 8000.001e67a0a1f6 no eth0 >> <-- Public Traffic >> >> >> In cloudstack i have set two physical networks (Physical-network-eth0 >> and Physical-network-eth1), during the initial adding of a zone. >> >> Later, when I try to add a guest network it gives me only >> physical-network-eth1 and requires a VLAN. Obviously >> that cannot work, is going to the wrong switch. Other experiments >> (e.g. adding another Guest Traffic to cs-public) >> failed because the network offering field is empty. >> >> Thanks for the fast reply! >> >> Konstantinos >> >> >> On Tue, Apr 15, 2014 at 2:39 PM, Pierre-Luc Dion <pd...@cloudops.com> >> wrote: >> > If this is a lab, it will work fine, you will have to define network >> > interface labels in Cloudstack in the networking config of the zone. >> labels >> > are networks name of the hypervisor servers. >> > >> > >> > Pierre-Luc Dion >> > Architecte de Solution Cloud | Cloud Solutions Architect >> > 855-OK-CLOUD (855-652-5683) x1101 >> > - - - >> > >> > *CloudOps*420 rue Guy >> > Montréal QC H3J 1S6 >> > www.cloudops.com >> > @CloudOps_ >> > >> > >> > On Tue, Apr 15, 2014 at 8:29 AM, Konstantinos Karampogias < >> > konstantinos.karampog...@centralway.com> wrote: >> > >> >> I have the following architecture >> >> >> >> (internet) ------(GW)--[ SWITCH A, public IPs address, no vlans] >> >> -------eth0-[ Cloudstack hosts]-eth1------ [SWITCH B, vlans, private >> >> IPs] >> >> >> >> >> >> I want to create a direct public shared network, in which the VMs >> >> will have routable public IP. >> >> (example >> >> >> http://shankerbalan.net/blog/create-a-shared-network-with-public-ips-in-cloudstack/ >> >> ) >> >> >> >> Can I do that given that >> >> -Management Traffic, Guest Traffic are connected to SWITCH B (Physical >> >> Network -eth1), >> >> -Public Traffic connected to SWITCH A (Physical Network-eth0), >> >> -no vlan in SWITCH A? >> >> >> >> What is the original networking set up I should follow? >> >> >> >> I have been experimenting with cloudstack version 4.3 >> >> >> >> >> >> Thanks, >> >> Konstantinos >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Konstantinos Karampogias >> >> >> >> >> >> -- >> Centralway Factory AG | Konstantinos Karampogias, DevOps | LinkedIn | >> + 41 44 578 40 00 >> -- Centralway Factory AG | Konstantinos Karampogias, DevOps | LinkedIn | + 41 44 578 40 00
