Google Groups

Re: unable to deallocate floating IPs on OpenStack


Jim Glennon Apr 24, 2012 4:46 AM
Posted in group: jclouds (DEPRECATED)
ok. we are talking about two different providers then. and from what i
am seeing, this functionality does not seem to be working correctly
for "hpcloud-compute".

On Apr 23, 3:22 pm, Dirk Hogan <dirkjho...@gmail.com> wrote:
> Jim-
> No - it is the standard "openstack-nova" api pointed at HP cloud (https://region-a.geo-1.identity.hpcloudsvc.com:35357/).
>
> Dirk
>
> On Mon, Apr 23, 2012 at 9:34 AM, Jim Glennon
> <jim.glen...@enterprisedb.com>wrote:
>
>
>
>
>
>
>
> > shoot. i don't know...
>
> > and this is with the hpcloud-compute provider, tested on the HPCloud?
>
> > ~jim
>
> > On Apr 23, 11:59 am, Dirk Hogan <dirkjho...@gmail.com> wrote:
> > > Hi Jim-
> > > For what it's worth, I modified my test app to first disassociate the FIP
> > > from the server prior to deleting the FIP - no difference - in invocation
> > > was successful, and the FIP disappeared from the web-site.
>
> > > Dirk
>
> > > On Mon, Apr 23, 2012 at 7:50 AM, Jim Glennon
> > > <jim.glen...@enterprisedb.com>wrote:
>
> > > > Hi Dirk,
>
> > > > I'm trying to determine why I am seeing different results than you
> > > > are. I am only associating the FIP to one server and then trying to
> > > > release it prior to terminating the instance. The one thing I may be
> > > > doing differently, is removing the FIP from the server prior to
> > > > attempt to deallocate. Should this make a difference?
>
> > > > Thanks.
>
> > > > jim
>
> > > > On Apr 20, 12:27 pm, Dirk Hogan <dirkjho...@gmail.com> wrote:
> > > > > Hi Jim-
> > > > > I'm supposed to integrate the alpha.4 bits into a major release, so
> > your
> > > > > post kind of freaked me out. So I ran a basic test, and got different
> > > > > results. See the relevant code snippet, and the corresponding log.
> > I'm
> > > > not
> > > > > trying to be contentious - I just want to be sure I'm not missing
> > > > > something. Were you doing something different? Prior to this
> > deletion I
> > > > > associated the FIP with a few servers.
> > > > >             try {
> > > > >             System.out.println("The to-be-destroyed FIP: " + ip);
> > > > >                 System.out.println("Pre-deletion: list of account
> > FIPs:
> > > > " +
>
> > client.getFloatingIPExtensionForZone(region).get().listFloatingIPs());
>
> > client.getFloatingIPExtensionForZone(region).get().deallocate(ip.getId());
> > > > >                 System.out.println("Post-deletion: list of account
> > FIPs:
> > > > "
> > > > > +
>
> > client.getFloatingIPExtensionForZone(region).get().listFloatingIPs());
>
> > > > >             } catch (Exception e) {
> > > > >                 System.out.println("Exception caught in cleanup: " +
> > e);
> > > > >                 e.printStackTrace();
> > > > >             }
>
> > > > > The to-be-destroyed FIP: {id=6091, ip=15.185.119.202, fixedIp=null,
> > > > > instanceId=null}
> > > > > Pre-deletion: list of account FIPs: [{id=990, ip=15.185.99.221,
> > > > > fixedIp=null, instanceId=null}, {id=5913, ip=15.185.119.24,
> > > > > fixedIp=10.4.39.119, instanceId=87151}, {id=6091, ip=15.185.119.202,
> > > > > fixedIp=10.4.74.222, instanceId=107133}, {id=6995, ip=15.185.123.82,
> > > > > fixedIp=10.4.68.157, instanceId=103524}, {id=7085, ip=15.185.123.172
> > ,
> > > > > fixedIp=10.4.71.230, instanceId=106058}, {id=7119, ip=15.185.123.206
> > ,
> > > > > fixedIp=10.4.72.38, instanceId=106114}, {id=7121, ip=15.185.123.208,
> > > > > fixedIp=10.4.0.155, instanceId=106092}, {id=7122, ip=15.185.123.209,
> > > > > fixedIp=10.4.71.249, instanceId=106093}, {id=7124, ip=15.185.123.211
> > ,
> > > > > fixedIp=10.4.30.42, instanceId=106100}, {id=7125, ip=15.185.123.212,
> > > > > fixedIp=10.4.72.28, instanceId=106101}, {id=7134, ip=15.185.123.221,
> > > > > fixedIp=10.4.72.41, instanceId=106111}]
> > > > > Post-deletion: list of account FIPs: [{id=990, ip=15.185.99.221,
> > > > > fixedIp=null, instanceId=null}, {id=5913, ip=15.185.119.24,
> > > > > fixedIp=10.4.39.119, instanceId=87151}, {id=6995, ip=15.185.123.82,
> > > > > fixedIp=10.4.68.157, instanceId=103524}, {id=7085, ip=15.185.123.172
> > ,
> > > > > fixedIp=10.4.71.230, instanceId=106058}, {id=7119, ip=15.185.123.206
> > ,
> > > > > fixedIp=10.4.72.38, instanceId=106114}, {id=7121, ip=15.185.123.208,
> > > > > fixedIp=10.4.0.155, instanceId=106092}, {id=7122, ip=15.185.123.209,
> > > > > fixedIp=10.4.71.249, instanceId=106093}, {id=7124, ip=15.185.123.211
> > ,
> > > > > fixedIp=10.4.30.42, instanceId=106100}, {id=7125, ip=15.185.123.212,
> > > > > fixedIp=10.4.72.28, instanceId=106101}, {id=7134, ip=15.185.123.221,
> > > > > fixedIp=10.4.72.41, instanceId=106111}]
>
> > > > > On Fri, Apr 20, 2012 at 9:09 AM, Adrian Cole <
> > adrian.f.c...@gmail.com
> > > > >wrote:
>
> > > > > > Hi, Jim.
>
> > > > > > you mind throwing this in the issues list and mark
> > > > Milestone-1.5.0-alpha.5?
>
> > > > > > We'll do a bug sweep.
>
> > > > > > -A
> > > > > > On Apr 19, 2012 1:17 PM, "Jim Glennon" <
> > jim.glen...@enterprisedb.com>
> > > > > > wrote:
>
> > > > > >> i haven't been able to release floating IPs that have been
> > allocated
> > > > > >> added to servers using the hpcloud-compute provider. i am able to
> > > > > >> remove the IP from the server, but after calling
> > > > > >> FloatIPClient.deallocate, the floating IP address is still
> > present in
> > > > > >> the list of allocated floating IPs (e.g. 'nova floating-ip-list').
> > > > > >> this is problematic since there is a quota on how many floating
> > IPs
> > > > > >> can be allocated. i have just tested this with the latest 1.5.0
> > alpha
> > > > > >> release.
>
> > > > > >> --
> > > > > >> You received this message because you are subscribed to the Google
> > > > Groups
> > > > > >> "jclouds" group.
> > > > > >> To post to this group, send email to jcl...@googlegroups.com.
> > > > > >> To unsubscribe from this group, send email to
> > > > > >> jclouds+u...@googlegroups.com.
> > > > > >> For more options, visit this group at
> > > > > >>http://groups.google.com/group/jclouds?hl=en.
>
> > > > > >>  --
> > > > > > You received this message because you are subscribed to the Google
> > > > Groups
> > > > > > "jclouds" group.
> > > > > > To post to this group, send email to jcl...@googlegroups.com.
> > > > > > To unsubscribe from this group, send email to
> > > > > > jclouds+u...@googlegroups.com.
> > > > > > For more options, visit this group at
> > > > > >http://groups.google.com/group/jclouds?hl=en.
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "jclouds" group.
> > > > To post to this group, send email to jcl...@googlegroups.com.
> > > > To unsubscribe from this group, send email to
> > > > jclouds+u...@googlegroups.com.
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/jclouds?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "jclouds" group.
> > To post to this group, send email to jcl...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > jclouds+u...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/jclouds?hl=en.