Comments inline. On 14-Nov-2013, at 6:48 pm, Vladimir Melnik <v.mel...@uplink.ua> wrote:
> Dear colleagues, > > > > It seems, I need some help again. > > How to understand what interface should be used as public, private or guest > interface? > > http://shapeblue.com/cloudstack/understanding-cloudstacks-physical-networking-architecture/ should help. :) > > On each hypervisor I have one bonded interface (bond0). Also I have eth0.101 > with 192.168.101.xxx/24 designated for management (192.168.101.0/24 is > designated to be the internal network of the pod). > > When system VMs start they have 192.168.101.11 and 192.168.101.13 addresses > as their "Private IP addresses”. That should be right - one management IP for the management interface (eth1) and the other would be assigned for the “storage” (eth3). See below snippet - 192.168.44.0/24 is my management subnet and 2 addresses from this block is assigned to eth1 and eth3. root@s-1-VM:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 0e:00:a9:fe:02:10 brd ff:ff:ff:ff:ff:ff inet 169.254.2.16/16 brd 169.254.255.255 scope global eth0 inet6 fe80::c00:a9ff:fefe:210/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:40:9a:00:00:02 brd ff:ff:ff:ff:ff:ff inet 192.168.44.82/24 brd 192.168.44.255 scope global eth1 inet6 fe80::440:9aff:fe00:2/64 scope link valid_lft forever preferred_lft forever 4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:20:46:00:00:06 brd ff:ff:ff:ff:ff:ff inet 192.168.21.100/24 brd 192.168.21.255 scope global eth2 inet6 fe80::420:46ff:fe00:6/64 scope link valid_lft forever preferred_lft forever 5: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 06:f0:b2:00:00:03 brd ff:ff:ff:ff:ff:ff inet 192.168.44.83/24 brd 192.168.44.255 scope global eth3 inet6 fe80::4f0:b2ff:fe00:3/64 scope link valid_lft forever preferred_lft forever > > So, did I get this right that bond0.101 should be bridged by some cloudbrX > and this cloudbrX should be stated as private.network.device, right? Here is what I have on my KVM box: eth0 - management - cloudbr0 eth1 - storage - cloudbr1 (but I don’t use it) eth2 - guest - cloudbr2 eth3 - public - cloudbr3 [root@kvm2-1 ~]# brctl show bridge name bridge id STP enabled interfaces cloudbr0 8000.000c293966df yes eth0 cloudbr1 8000.000c293966e9 yes eth1 cloudbr2 8000.000c293966f3 yes eth2 cloudbr3 8000.000c293966fd yes eth3 [root@kvm2-1 ~]# > What interface should be stated as guest.network.device? Some cloudbrX which > will be bridged with the whole bond0, right? So the cloudbrX is just a label. CloudStack uses this to figure out the real interface. As long as you specify the correct label and have a matching brctl entry, cloudstack will create virtual interfaces correctly for instances. [root@kvm2-1 ~]# brctl show bridge name bridge id STP enabled interfaces breth2-215 8000.000c293966f3 no eth2.215 vnet10 vnet7 cloud0 8000.fe00a9fe00dd no vnet0 vnet3 vnet8 cloudbr0 8000.000c293966df yes eth0 vnet1 vnet4 vnet6 cloudbr1 8000.000c293966e9 yes eth1 cloudbr2 8000.000c293966f3 yes eth2 cloudbr3 8000.000c293966fd yes eth3 vnet2 vnet5 vnet9 virbr0 8000.52540068c935 yes virbr0-nic [root@kvm2-1 ~]# > > And what interface should be stated as public.network.device? > Since you have only ONE interface, all the labels will be cloudbr0. Regards. -- @shankerbalan M: +91 98860 60539 | O: +91 (80) 67935867 shanker.ba...@shapeblue.com | www.shapeblue.com | Twitter:@shapeblue ShapeBlue Services India LLP, 22nd floor, Unit 2201A, World Trade Centre, Bangalore - 560 055 CloudStack Bootcamp Training on 27/28 November, Bangalore http://www.shapeblue.com/cloudstack-training/ This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
