https://issues.apache.org/jira/browse/CLOUDSTACK-9750
Hi
Ok, wrong wording here, not userVM of course but the public IPs for
isolated networks. But you got the idea :)
Great I am not the one guy with this use case. Filing a feature request
in JIRA. Thanks to all for your inputs!
Regards
René
Hi Will
On 01/17/2017 06:13 AM, Will Stevens wrote:
> Rene, this is probably not going to solve your problem, but I use this
> trick for other use cases. You can setup more than one range. ACS seems
> to always exhaust one range before moving on to the next range. If it is a
> new install, then
I agree with Will's suggestion.
-Wei
2017-01-17 6:13 GMT+01:00 Will Stevens :
> Rene, this is probably not going to solve your problem, but I use this
> trick for other use cases. You can setup more than one range. ACS seems
> to always exhaust one range before moving on to the next range. If
l.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-Original Message-
From: Erik Weber [mailto:terbol...@gmail.com]
Sent: 17 January 2017 08:27
To: dev@cloudstack.apache.org
Subject: Re: Dedicated IP range for SSVM/CPVM
Hi N
Hi Nitin,
There are legit reasons for separating VR public pool from SSVM and CPVM.
For instance if you run a private cloud and don't want to have your
cpvm/ssvm publically available, but still want to have the VRs accessible
Erik
tir. 17. jan. 2017 kl. 05.37 skrev Nitin Kumar Maharana <
nitink
Rene, this is probably not going to solve your problem, but I use this
trick for other use cases. You can setup more than one range. ACS seems
to always exhaust one range before moving on to the next range. If it is a
new install, then you can do a range with only 2 IPs in it and make it
first.
Hi Rene,
The default pool, which means are you mentioning the public IP range?
If it is a public IP range, user VMs won’t be consuming any IP from there.
Only system VMs(CPVM/SSVM/VR) will be consuming. VRs will be providing public
access to the user VMs.
Thanks,
Nitin
> On 16-Jan-2017, at 8:5
