cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan Rodriguez <ivan...@gmail.com>
Subject Advanced Network Clarification
Date Thu, 22 Nov 2012 01:31:38 GMT
Dear Fellows,

We are trying to finish our cloudstack setup using advanced zone, and I'm
having some doubts about our network design, initially we allocate vlans
for hypervisor management, for primary storage and for secondary storage,
however we are using blades, and on the blade we only have one interface,
we need to tag our vlans on the interface and then build bridges on top of
that this increase the complexity of the configuration in the host, so my
first question is if we are using only 1 interface
in our host does it make sense to have all this vlan + aliases + bridges? I
was thinking to simplify the design just having 2 vlans the public and the
hypervisor + storage.

This bring my second question, when we add storage network, it will ask for
the the range lets say we allocate 10.1.1.0/24 for storage shall we fill
the whole range into the storage or just a part how many ip addresses
cloudstack needs ??? I haven't found a reference to the doco, it seems to
me that we only need 2 ip addresses for that subnet that will be assigned
to the storage system vm, anyone can explain what this ranges are for ???

And Finally on the documentation the example is using 3 vlans what is the
300 vlan for ?? when we use advanced zone we define a range for vlan ids
that we want cloudstack to use

   1. VLAN 100 for management of the hypervisor
   2. VLAN 200 for public network of the instances (cloudbr0)
   3. VLAN 300 for private network of the instances (cloudbr1)

http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/html/Installation_Guide/hypervisor-kvm-install-flow.html

So far in our setup we don't use cloudbr1 and its been working fine, do we
need cloudbr1 on advanced network configuration ? is it recommended ??

Thanks in advance
Ivan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message