We are thrilled to announce the immediate availability of our latest cloud pool, namely, the splitter cloud pool. Unlike other cloud pools, which act as easy to use abstractions over various cloud APIs, the splitter pool allows users to easily manage multiple cloud providers as if they are one. It does so by delegating both queries and update commands to the backend cloud pools it is configured to work with.
We are happy to announce the immediate availability of scale.cloudadapters version 1.0.1 on our GitHub page. It addresses two bugs, namely:
To compare JodaTimeDateTime objects for equality, we previously simply ran equals on them. This checks not only that two objects describe the same time (i.e. milliseconds since the epoch), but also that they have the same time zone descriptor (Chronology). For our purposes, and one might be tempted to think that this is often the general case, we only really wanted the first check, not the second.
Amazon imposes a limit on how many filter values one may specify in the call to DescribeInstances, but does not specify how many. In practice, this has turned out to be 200, which we discovered when we (erroneously) tried to query for our instances and supplied the instance identifiers of interest as filter values. This is fine for deployments smaller than 200, but of course, runs into the FilterLimitExceeded error for larger deployments. While at it, support for deployments larger than 1000 was added, by handling Amazon’s implicit pagination/result set chunking with tokens returned from the DescribeInstances operation.
The code for scale.cloudadapters, our open source Java-based cloud adapters, can either be cloned or forked directly on our GitHub page, or be made part of your own projects using your favorite Java dependency management tool, such as Maven, Ivy, or Gradle, by importing it from Maven Central.
We have released a minor bugfix release of scale.commons. The update concerns the commons.util package, and consists of JSON parsing support for Google Guava’sImmutableList. This allows e.g. configuration POJOs to contain ImmutableList rather than mutable ones, which is significantly nicer from a thread safety point of view.
Get the code either from our GitHub page directly, or via your favorite Java dependency management tool such as Maven, Ivy or Gradle from MavenCentral.
We are happy to announce that we have updated our web page to be more modern and mobile-friendly. Our products and professional service offerings have also been updated. Head over there and have a look!