If port id of a FloatingIP is null, can I decide that the floating IP is not allocated to any instances?

Hi devs, I am using neutron API. How can I decide whether a floating IP is not allocated to any instances. Is $Subject correct approach? In Nova API we had instance id for a floating IP, so we can check whether the instance id is null or not, and decide whether the floating IP is allocated or not

Re: too may files open

On Tue, Nov 18, 2014 at 05:27:48PM -0300, felipe gutierrez wrote: > time ago I asked here why I am getting "too many files open" with jclouds > and the answer was I needed to close my BlobStoreContext. I did but now I > am getting this error again. I believe the context is opening in other > locati

Re: java.net.SocketTimeoutException correlated with old generation GC

So I figured out the http-bio-exec-nn threads are tomcat7's. What are the settings jclouds.user-threads jclouds.io-worker-threads jclouds.scheduler-threads for then? My code is creating one context and hangs onto it for life. On Tue, Nov 18, 2014 at 11:49 AM, Adrian Cole wrote: > A typical le

too may files open

Hi, time ago I asked here why I am getting "too many files open" with jclouds and the answer was I needed to close my BlobStoreContext. I did but now I am getting this error again. I believe the context is opening in other location. This is my code . I close the conte

Re: AWS Ec2 new hardware type, like t2.micro

it is in the main repo now and will be in any next release of jclouds. On Tue, Nov 18, 2014 at 8:13 AM, Vineet Saini wrote: > So I should be pick this fix from 1.8.2 snapshot release only, is that > correct? Also when it will be pushed to repo? > > On Tue, Nov 18, 2014 at 9:58 AM, Andrew Phillips

Re: java.net.SocketTimeoutException correlated with old generation GC

A typical leak is creating a context with ContextBuilder, but never closing it. Could that be the case here? With latest jclouds (and default http driver), the only use of threads are aggregate operations like clearing a container. On Nov 18, 2014 8:34 AM, "Daniel Hsueh" wrote: > Thanks Adrian!

Re: java.net.SocketTimeoutException correlated with old generation GC

Thanks Adrian! In the meantime, I have some more observations. The old-gen GC correlation occurs with incgc (4G Xmx and Xms), cms (4G), and G1 (2G and 1G); G1 with 4G memory sees failures not correlated with any old-gen run (no old-gen runs occurred at all). The glut of threads are all showing u

Re: Removal vcloud and vcloud-director from jclouds in version 1.9.0

Not sure If I read it right, does this mean VCloud support will be removed in 1.8.x onward? This will be big dent for Jcloud users. On Sun, Nov 16, 2014 at 11:26 PM, Adrian Cole wrote: > TL;DR; > > jclouds will stop maintaining vcloud in 1.8.x. We will remove vcloud > (and the vcloud-director

Re: AWS Ec2 new hardware type, like t2.micro

So I should be pick this fix from 1.8.2 snapshot release only, is that correct? Also when it will be pushed to repo? On Tue, Nov 18, 2014 at 9:58 AM, Andrew Phillips wrote: > Do we know if anyone will be working one this anytime soon? >> > > https://github.com/jclouds/jclouds/pull/605 is being r

Re: AWS Ec2 new hardware type, like t2.micro

Do we know if anyone will be working one this anytime soon? https://github.com/jclouds/jclouds/pull/605 is being reviewed right now ;-) Thanks for the ping! ap

Re: AWS Ec2 new hardware type, like t2.micro

looks like there is. Let's keep discussion in that jira for now!

Re: AWS Ec2 new hardware type, like t2.micro

Look like there existing ticket for same: https://issues.apache.org/jira/browse/JCLOUDS-621 Do we know if anyone will be working one this anytime soon? On Mon, Nov 17, 2014 at 3:39 PM, Andrew Phillips wrote: > So here instanceType.T2_MICRO not supported. Only previous generation >> listed her