Only seen it once -- which was enough to cause it to crash and burn, but rare. (With the patch I can see it only affects 1 of 116 instances with quite an eclectic variety.) So I don't think it will affect too many users. If we get evidence that it is a widespread issue then I agree the jclouds API and/or fallbacks should be revisited.
That's far from being the biggest problem with the softlayer provider however! The fact that it is working reveals another big flaw: it takes more than 10m just to list the nodes! Seems to be because it makes several requests for every single guest VM to populate details. A cache (e.g. of product types) would speed that up enormously. Or having an option to `listNodes` with very sparse details -- e.g. to provision a machine it currently does `listNodes()` in `CreateNodesWithGroupEncodedIntoNameThenAddToSet.java` which goes and makes lots of requests to get all the details even though it only needs the names! However: with this patch it is working. Great effort folks. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/199#issuecomment-28256606
