Yep, you're right, all service traffic in one VLAN,
all guest traffic in another one for pod or all zone.
You are welcome.
2018-05-29 17:09 GMT+07:00 Jon Marshall :
> So everything on one subnet/vlan except guest traffic which has it's own.
>
>
> Man thanks for that.
>
>
> __
So everything on one subnet/vlan except guest traffic which has it's own.
Man thanks for that.
From: Ivan Kudryavtsev
Sent: 29 May 2018 10:49
To: users
Subject: Re: Basic networking setup
Hello, Jon,
Basically following schema is used for a basic zone:
1. sys
Hello, Jon,
Basically following schema is used for a basic zone:
1. system VMs and hardware servers (heads, secondary storages, hypervisors)
use a fake net like 10.0.0.0/16 (I also do NAT all those nodes thru heads
to avoid public IPs, or separate security appliance can be used);
2. guest network
>From the 4.11 documentation -
"When basic networking is used, CloudStack will assign IP addresses in the CIDR
of the pod to the guests in that pod. The administrator must add a Direct IP
range on the pod for this purpose. These IPs are in the same VLAN as the hosts."
It may be the way it is
Keep in mind there is nothing stopping you from nesting your storage in
CloudStack, i.e. you build your cluster nodes as well as a storage VM which
provides NFS or iSCSI – then you can mount the NFS share / iSCSI LUN from the
multiple cluster nodes. You may hit some performance issues with this
