deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ronelle Landy (JIRA)" <>
Subject [jira] [Closed] (DTACLOUD-361) fgcp: return actual IP address instead of dummy when creating new address
Date Wed, 13 Mar 2013 15:02:13 GMT


Ronelle Landy closed DTACLOUD-361.

Closing issue as fixed (before) deltacloud commit version: 56c1c7f56a99b83169c7cb945f4c746ece549cf1
> fgcp: return actual IP address instead of dummy  when creating new address
> --------------------------------------------------------------------------
>                 Key: DTACLOUD-361
>                 URL:
>             Project: DeltaCloud
>          Issue Type: Improvement
>          Components: Server
>            Reporter: Dies Koper
>            Assignee: Michal Fojtik
>            Priority: Minor
>         Attachments: 0001-fgcp-return-IP-address-immediately-also-add-argument.patch,
> There is a difference between Deltacloud and FGCP API regarding public IP address allocation:
> In Deltacloud you allocate an IP address, it is returned immediately, and then you assign
it to an instance.
> In FGCP, you allocate an IP address, nothing is returned immediately - you have to wait
and poll the list of IP addresses until you notice a new one has been added and hope no one
else allocated another one in the meantime as you won't know which was yours - then you need
to enable the IP address, which is also an asynchronous operation, and then you can assign
it to an instance.
> In the current Deltacloud implementation, you allocate an IP address and need to poll
the list to find it. When you try to assign it to an instance the first time, you'll get an
error back. It will however enable the IP address so if you retry the operation a minute later
it will properly assign the IP address to a machine.
> Should try to bring the fgcp api into the fold.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message