cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Murali Reddy <>
Subject Re: why not share network use the same CIDR mechanism to assign ip to guest vm. but only isolated network?
Date Thu, 28 Feb 2013 10:32:26 GMT
On 28/02/13 2:23 PM, "Wang Fei" <> wrote:

>As Saksham clarify at previous mail. We can fetch some useful
>to convenient, here is some point have clarified by Saksham
>* You can always modify the default setting of CIDR when
>    you create a zone.
>  * You can create isolated guest networks with your custom CIDR by
>    specifying the netmask and gateway. This overrides the zone level
>    setting.
>  * In shared Networks the start IP - end IP range will define the range
>    of IPs from which Cloudstack Guest VMs get IPs, so you restrict the
>    guest Vms to get IPs from this defined range.
>  * IP reservation in Isolated Guest networks is a new feature in
>    CloudStack which allows to use a part of the guest network for
>    Cloudstack guest Vms and remaining part (if you wish to do so) for
>    non Cloudstack purposes.
>but here is some confuse me. why distinguish these two kind of network on
>ip assignment.
>isolated base CIDR, share need set the ip range manually.

In case of 'isolated networks' CloudStack designs the network (decides
CIDR, gateway etc) and provides L3-L7 services (gateway, source NAT etc).
Historically, 'shared network' did not have any services other that DHCP,
DNS and data path for the shared network is controlled by the admin. So In
a way, admin defines the shared network CIDR, gateway etc and configures
them in the CloudStack.

>best regards

View raw message