Hello Pierre-Luc, thanks for the reply. I need for other reasons to stay in advance configuration. I know that i do not need to have a definition for cs-mgmt but I am keeping it because in the future management network will be separated also.
What I am trying to do to achieve my objective 1. command listPhysicalNetworks #to get the eth0 2. command addTrafficType physicalnetworkid=e84a8626-3106-4486-9a3f-87b7a435a967 traffictype=Guest kvmnetworklabel=cs-public #Same bridge as the public network 4. command createNetworkOffering displaytext=ExternalNetworkOffering name=ExternalNetworkOffering guestiptype=Shared specifyipranges=false specifyvlan=false traffictype=Guest supportedservices="" 5. command createNetwork displaytext=ExternalNetwork name=ExternalNetwork networkofferingid=512b1b05-50f2-4200-b74d-b8b3c37adc3f zoneid=8cb722f3-33ec-4686-aa4f-68237125c943 startip=192.168.100.2 endid=192.168.100.100 gateway=192.168.100.1 netmask=255.255.255.0 vlan=830 physicalnetworkid=e84a8626-3106-4486-9a3f-87b7a435a967 FAILED because "431: SpecifyVlan should be true if network offering's type is Shared" "431: SpecifyIpRanges should always be true for Shared network offerings" To sum up my objective is to create : a shared guest network, in a specific bridge (which is the same as the public), without vlans, without any service and in the advance networking setup. (internet) [ SWITCH A, public IPs address, no vlans] - -eth0- - [ Cloudstack Hypervisor] - -eth1- - [SWITCH B, vlans, private IPs] Any idea where I am doing it working Thx! On Tue, Apr 15, 2014 at 7:25 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote: > you can use simple networking zone if you want, if you use advanced > networking zone you should skip the network definition for cs-mgmt > 8000.001e67a0a1f7 no eth1.849 > in cloudstack. Instead when you will define IP range for the management > network of the POD you will specify a vlanID > > so you should define in cloudstack 2 nic: > ex: > eth0 with label cs-public and traffic type=public > eth1 with label cs-guest and traffic type=guest,management > > > > > > 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 11:19 AM, Konstantinos Karampogias < > konstantinos.karampog...@centralway.com> wrote: > >> 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 >> -- Centralway Factory AG | Konstantinos Karampogias, DevOps | LinkedIn | + 41 44 578 40 00