Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disassociated Floating IPs remain allocated in the project #28

Closed
bhagemeier opened this issue Sep 14, 2012 · 13 comments
Closed

Disassociated Floating IPs remain allocated in the project #28

bhagemeier opened this issue Sep 14, 2012 · 13 comments
Labels

Comments

@bhagemeier
Copy link
Contributor

Hi there,

the workflow of allocating floating IPs is sligthly different in Nova and OCCI. Whereas in OCCI, it is done in one step (action=alloc_float_ip), you need to allocate an IP to the project first and only then associate it with a machine.

When terminating a machine through OCCI (or Nova if you like), the IP remains allocated to the project. A new OCCI alloc_float_ip will allocate a new address to the project, thus consuming all available IPs over time.

The desired behaviour would be to also deallocate IPs from the project, thus making the actions symmetric.

Cheers,
Björn

@bhagemeier
Copy link
Contributor Author

Actually, the problem rather seems to be that when you terminate an instance without deallocating the floating IP first, then the IP remains in the project. Otherwise it will be released. The desired symmetry can as well be created in the client.

A problem arises, if one uses only the OCCI interface and terminates a machine that still has a floating IP associated to it. Then there's no means to release the floating IP from the project afterwards. I'd say, there's room for improvement here, unless I've overlooked something.

@dizz
Copy link
Collaborator

dizz commented Mar 6, 2013

Is this still an issue @bhagemeier ?

@bhagemeier
Copy link
Contributor Author

I'm checking.

@dizz
Copy link
Collaborator

dizz commented Mar 13, 2013

Thanks!

@bhagemeier
Copy link
Contributor Author

Hi Andy,

right now I cannot even list the available floating IP pools as
described in https://wiki.openstack.org/wiki/Occi#List_Floating_IP_Pools

Björn

On 13.03.2013 12:42, Andy Edmonds wrote :

Thanks!


Reply to this email directly or view it on GitHub
#28 (comment).

Dipl.-Inform. Björn Hagemeier
Federated Systems and Data
Juelich Supercomputing Centre
Institute for Advanced Simulation

Phone: +49 2461 61 1584
Fax : +49 2461 61 6656
Email: b.hagemeier@fz-juelich.de
Skype: bhagemeier
WWW : http://www.fz-juelich.de/jsc

JSC is the coordinator of the
John von Neumann Institute for Computing
and member of the
Gauss Centre for Supercomputing



Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,

Prof. Dr. Sebastian M. Schmidt


@tmetsch
Copy link
Owner

tmetsch commented Mar 15, 2013

Ah floating ips are now handled by adding a link between a VM and a public network.

@bhagemeier
Copy link
Contributor Author

From which pool are the floating IPs selected? I don't see any information about floating IP pools from the query interface.

When trying to link instances with a public network like this:

curl -k -v -X POST https://egi-cloud.zam.kfa-juelich.de:8787/networklink/ -H 'Content-Type: text/occi' -H 'X-Auth-token: *****' -H 'Category: networkinterface; scheme="http://schemas.ogf.org/occi/infrastructure#"; class="kind"' -H 'X-OCCI-Attribute: occi.core.source="https://egi-cloud.zam.kfa-juelich.de:8787/compute/d7e612ca-49a6-49a4-beb7-a6ca0d019f12"' -H 'X-OCCI-Attribute: occi.core.target="https://egi-cloud.zam.kfa-juelich.de:8787/network/public"'

I am told that there's no floating IPs available:

NoMoreFloatingIps: Zero floating ips available.

However, I can easily select one using nova tools or Horizon.

Even adding

-H 'X-OCCI-Attribute: org.openstack.network.floating.pool="public_ips"'

does not help.

@bhagemeier
Copy link
Contributor Author

Hi guys,

this is becoming really pressing. Several of our users are asking how to associate floating IPs.

Cheers,
Björn

@tmetsch
Copy link
Owner

tmetsch commented Apr 24, 2013

Hi,

What is the problem than?

Cheers,

-Thijs

On Wed, Apr 24, 2013 at 9:53 AM, Björn Hagemeier
notifications@github.comwrote:

Hi guys,

this is becoming really pressing. Several of our users are asking how to
associate floating IPs.

Cheers,
Björn


Reply to this email directly or view it on GitHubhttps://github.com//issues/28#issuecomment-16912591
.

@bhagemeier
Copy link
Contributor Author

Hi Thijs, please see comment #28 (comment), which is an open question about how to find floating IPs from the right pool and associating it. I don't see the floating IP pools listed in the query interface.

@tmetsch
Copy link
Owner

tmetsch commented Apr 24, 2013

Alright - Just discussed with @dizz about this - I think we have a solution for this...

tmetsch pushed a commit that referenced this issue Apr 29, 2013
tmetsch pushed a commit that referenced this issue Apr 29, 2013
tmetsch pushed a commit that referenced this issue Apr 29, 2013
tmetsch pushed a commit that referenced this issue May 3, 2013
@tmetsch
Copy link
Owner

tmetsch commented May 3, 2013

please check - should be fixed for folsom.

@tmetsch tmetsch closed this as completed May 3, 2013
@bhagemeier
Copy link
Contributor Author

Hi Thijs,

I checked this today and the association of floating IPs works like a charm. Thank you. I'll open a new issue about listing the available floating IP pools.

Björn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants