Hello,
Main issue is when any user in basic networking zone can use any IP from
zone's subnet, without any isolation and CS wouldn't know that.
On 2015.07.08. 10:09, Sanjeev N wrote:
If you want CS not to allocate these IPs to any other vm, you can mark
Allocated field in user_ip_address tabl
If you want CS not to allocate these IPs to any other vm, you can mark
Allocated field in user_ip_address table for all the IPs you want to assign
to guest vms manually.
On Mon, Jul 6, 2015 at 12:17 PM, Mārtiņš Jakubovičs
wrote:
> Hello,
>
> In Basic Networking IP address acquisition is not a ma
Hello,
In Basic Networking IP address acquisition is not a manual process but
CS it self give IP's for instances. Problems is that if you configure IP
address pool in zone, user can add all this IP addresses to one instance
without informing CS.
Example:
IP address pool (10.11.11.1 - 10.11.1
What do you mean by IP address is acquired? In Basic Networking we don't
have IP address acquisition concept. Also alias IPs you are manually
configuring on deployed vms should not be overlapped with the Guest IP
address range provided in that zone.
On Fri, Jul 3, 2015 at 7:51 PM, Mārtiņš Jakubovi
Hello,
I test right now infrastructure with base network setup. I faced issue,
if I deploy instance, I am able manually add more public IP's. For
example, I deploy VM, though DHCP I acquire IP, and I can manually add
alias IP addresses without problems and CloudStack still think that I
use on
