cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@soleks.com
Subject RE: Adding a public range for an account
Date Tue, 24 Apr 2012 18:20:44 GMT
Alena, 
Ok, that is pretty clear and logically, but why when I'm requesting new IP using account with
associated network, provided IP is coming from default network, but not from allocated for
that account. 

> Dan,
>
> When public ip address range is created per account, all ip addresses 
> from this range immediately get allocated to the account . You can't 
> release single ip from account specific range with 
> disassociateIpAddress command. The only one way to release account 
> specific ips - delete the entire range (using deleteVlanIpRange api).
>
> I'll make sure we create document for this feature, and I'll pass it 
> to you/community once it's done.
>
> -Alena.
>
> -----Original Message-----
> From: dan@soleks.com [mailto:dan@soleks.com]
> Sent: Tuesday, April 24, 2012 10:52 AM
> To: cloudstack-users@incubator.apache.org
> Subject: Re: Adding a public range for an account
>
> Clayton, it's borei, can you please post mine
>
> Hi All,
> I created new public network via infrastructure->zone->physical 
> network->public->IP range menu and assigned it to account in non-root 
> domain. Private network was also created for that account. When i use 
> that account and trying to request IP, IP was chosen from default 
> public network, not from created above. Dashboard also shows that all 
> IPs in that new network occupied. I looked into database and found 
> that all IPs are in the "Allocated" state and there is no UUID for 
> them. Can somebody gimme explanation how should it work and what is 
> correct behaviour.
>
>> In CS 3.0.1 with advanced networking.  I was trying to add a new
>> public IP range for a specific account.  I went into the physical
>> network, added a new range and specified the domain and account that
>> it was to belong to.  It was a brand new account so it didn't have any
>> existing instances, nor did it have a virtual router.  When adding the
>> first instance I got the following error:
>>
>> http://paste.cloudstack.org/SSEO/
>>
>> Did I do something wrong?  Is there an additional step I should have
>> done in order to associate a new IP range with a specific account?
>>
>> Thanks,
>> Clayton
>>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message