<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>There is a config value in horizon to autorelease floating ips. Ive never seen nova not autodissassociate on delete. That may be a misconfiguration between nova and neutron? I dont think horizon is involved in that path. Maybe try from the cli to double
check?<br>
<br>
Thanks,<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Erich Weiler<br>
<b>Sent:</b> Monday, November 23, 2015 4:10:45 PM<br>
<b>To:</b> Fox, Kevin M; rdo-list@redhat.com<br>
<b>Subject:</b> Re: [Rdo-list] Possible bug? Horizon/Floating IPs<br>
</font><br>
<div></div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Kevin,<br>
<br>
Thanks for the reply! I think we may be talking about two different <br>
things however... I'm not looking to release the IP back to the public <br>
pool, I'm just looking to disassociate from a deleted VM when the <br>
instance is terminated. After I terminate the instance, it still shows <br>
as stuck to the deleted instance, which is kind of pointless.<br>
<br>
After I disassociate the floating IP via 'neutron <br>
floatingip-disassociate', it releases the IP back to my own allocated IP <br>
list, so I most definitely can re-use that IP for another instance <br>
easily. I agree that if I unallocated it with 'neutron <br>
floatingip-delete', then I may not get it back, but with 'neutron <br>
floatingip-disassociate' I still own it as a user of a project.<br>
<br>
Just checking if the decision was made to stop dissociating the floating <br>
IPs upon instance termination after Icehouse, or if it was overlooked in <br>
Kilo?<br>
<br>
Thanks for the reply!<br>
<br>
cheers,<br>
erich<br>
<br>
On 11/23/2015 03:59 PM, Fox, Kevin M wrote:<br>
> Autorelease is kind of dangerous. There is no way to get an ip back, and<br>
> it may be associated in dns and you may give it back to the pool before<br>
> unregistering. I always have disabled it on all my clouds to fail safe<br>
> for the users.<br>
><br>
> Kevin *<br>
> *<br>
> ------------------------------------------------------------------------<br>
> *From:* rdo-list-bounces@redhat.com on behalf of Erich Weiler<br>
> *Sent:* Monday, November 23, 2015 2:56:07 PM<br>
> *To:* rdo-list@redhat.com<br>
> *Subject:* [Rdo-list] Possible bug? Horizon/Floating IPs<br>
><br>
> Just thought I'd throw this out there as a possible bug... I'm running<br>
> RHEL 7.1 and OpenStack Kilo RDO.<br>
><br>
> It seems that when I terminate an instance through Horizon that has an<br>
> associated floating IP, the floating IP is *not* disassociated upon the<br>
> instance's termination. I have to manually disassociate the floating ip<br>
> after I terminate the instance through Horizon via:<br>
><br>
> neutron floatingip-disassociate e28051c5-7fb1-4887-ade9-f1b062523ad7<br>
><br>
> for example. Then it frees up. Back when I was playing with the<br>
> Icehouse release of RDO OpenStack, the floating IPs were released<br>
> automatically when I terminated an instance through Horizon, so I was<br>
> surprised when I did not see the same behaviour here.<br>
><br>
> [root@os-con-01 ~]# rpm -q python-django-horizon<br>
> python-django-horizon-2015.1.0-5.el7.noarch<br>
><br>
> Just a heads up...<br>
><br>
> cheers,<br>
> erich<br>
><br>
> _______________________________________________<br>
> Rdo-list mailing list<br>
> Rdo-list@redhat.com<br>
> <a href="https://www.redhat.com/mailman/listinfo/rdo-list">https://www.redhat.com/mailman/listinfo/rdo-list</a><br>
><br>
> To unsubscribe: rdo-list-unsubscribe@redhat.com<br>
</div>
</span></font>
</body>
</html>