incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <>
Subject Re: conserve mode for network offering
Date Wed, 05 Sep 2012 17:01:07 GMT
The 'conserve' mode dictates whether each service (LB/VPN/PF/etc) requires
its own public ip address or whether many services can share the same
public ip address.
For network offerings where different services are offered by different
devices, obviously the public ip addresses cannot be shared.
For network offerings purely supported by the VR, the public IP can be
shared, but then there are possibilities of rule conflicts (PF rule can
conflict with LB rule or FW rule). Also, it rules out upgrade of network
offering to an offering with per-service devices

On 9/4/12 11:27 PM, "Mice Xia" <> wrote:

>Hi, all
>I noticed when 'conserve mode' is not checked for a network offering, the
>guest network created from this offering cannot do port forwarding and
>load balance if sourceNat is enabled.
>After checking network.js and wiki [1], I realized it was by design and
>much complicated than document said:
>    'Conserve mode. Indicate whether to use conserve mode. In this mode,
>network resources are allocated only when the first virtual machine
>starts in the network.'
>Can someone explain why 'conserve mode' behave this way? Thanks.

View raw message