The team is still pretty busy this sprint supporting various trials, so we’re only able to tackle one substantial item of new functionality. This is to add support for multiple public identities associated with a single private identity, which has been requested by a European mobile operator who needs this to support an important use case for Clearwater in their network. We will also be continuing the work to address
Although much of Clearwater’s development happens on Amazon EC2, it’s always been designed to be cloud-agnostic. A few weeks ago, I attended Angelhack London, where Microsoft was promoting their Windows Azure cloud platform. Given their very generous free trial, I decided to try spinning up Clearwater on it one evening, and it was pretty straight-forward. First of all, despite the word “Windows̶
One of the pieces of collateral damage in getting Clearwater released as open source was support for Metaswitch’s Service Assurance Server (SAS) diagnostic tools. There was some intellectual property in the client library we didn’t want to open source and we couldn’t come up with a way to enable it without falling foul of GPL licensing conditions. SAS is a hugely valuable debugging tool, especially in a distributed h
Choosing film names for sprints has the unfortunate side effect that people might look for parallels between Clearwater development activity and the plot of the respective film. Into the Wild is about a free spirit who goes to live in the remote wilds of Alaska, ultimately with tragic consequences. We’re okay with the free spirit bit, but we can do without the tragic consequences. It’s been exactly two
For the first year or so of Clearwater development we tried to come up with meaningful names for each of our development sprints. If any of you have worked on projects using two week sprints you will know how hard this gets after a while. A few months ago we threw in the towel and decided to move to an arbitrary naming scheme. We settled on film titles, alphabetically sequenced hurricane style, and constrained to t
The projectclearwater.org Web site went live as of 9:00 am UK time this morning. It seems that the news of our impending launch got out a bit earlier than expected, so we know that there are already quite a few people who are keen to know more about Project Clearwater. When you’ve had a chance to look at the site, do please get in touch to give us feedback, ask us questions and tell us what you think.
With the short final sprint prior to letting Clearwater out into the wild now completed, we’re ready to go live. We know there’s a few rough edges here and there, but we think that Clearwater is now ready to play. The team is looking forward to getting some feedback and some questions, so please sign up for the mailing list and share your issues and your successes with Clearwater.
The final sprint before we go live is just 6 working days. We’re doing a little re-factoring of the Sprout and Bono code so the sharing of common functions is a little cleaner, and we’re making sure the high availability aspects of Homer and Homestead work as they should. We’re also doing some work to get Clearwater up and running on an OpenStack-based Cloud environment. The rest of the sprint is