Hi,
I'm confused what "KVM Traffic label" I should use for the guest internal
networks. According to "
http://www.shapeblue.com/cloudstack/understanding-cloudstacks-physical-networking-architecture/
"
...for KVM hosts they refer to the bridges which you will have created...
I'm trying to achieve network design like this:
KVM bridge CS Physical Network KVM physical NIC Network Subnet
Gateway VLAN
TAG CS Traffic Type Network IP Range cloudbr553 cloudbr553-MGMT-PN eth0
172.26.6.64 255.255.255.192 172.26.6.126 553 CS Management 172.26.6.66
- 172.26.6.76 cloudbr601 cloudbr601-STRG-PN eth1 192.168.1.0 255.255.255.0
192.168.1.254 601 CS Storage 192.168.1.1 - 192.168.1.3 cloudVirBr555
cloudVirBr555-Public-PN eth4 172.26.6.192 255.255.255.192 172.26.6.254 555
Public 172.26.6.211 - 172.26.6.229 172.26.6.243 - 172.26.6.247 ???eth5???
eth5-LAB-PN eth5 10.9.1.0 255.255.255.0 10.9.1.254 901 Guest 10.9.1.101 -
10.9.1.200
I'd like guest VMs to have interface connected to cloudVirBr901 (bridge
connected to eth5.901 on KVM host), later one I'throud like to have another
VLAN902 created, bridged to cloudVirBr902 and make available for new VMs
etc.
This is what is called isolated mode if I understand it correctly. What I
don't know is whether the Traffic label should be eth5 or cloudVirBr901 or
something else. Firstly I thought there must be a bridge, but after the
zone is created you can assign VLAN range to this, so I assumed that the
VLANs will be created as virtual interfaces on top of ethX and added to a
bridge automatically by cloudstack-agent. This implies that eth5 should be
the traffic label.
And furthermore I just scanned through announcement of a new feature
https://cwiki.apache.org/CLOUDSTACK/q-in-q-for-isolated-networks-functional-spec.html,
which allows for more isolated networks by creating vlans on top of tagged
interface.
Something like
https://cwiki.apache.org/CLOUDSTACK/cloudstack-advanced-network-tutorial-step-by-step.html,
but for KVM hosts would be much appreciated.
Rendy
