Recently I participated in a Cloud Computing Meetup in Boise, Idaho and had the opportunity to discuss Cloud Foundry and provide a demonstration of Stackato. Cloud Foundry is an open-source project with which I have been involved with for the past several years.
The Cloud Foundry documentation recommends configuring a wildcard DNS entry so that the routes to all apps deployed to the PaaS will be known by the DNS. But many corporate IT departments and cloud providers prohibit the use of wildcard entries in their DNS services.
One thing that slows developers down, other than the QWERTY keyboard, is running tests. Test-driven development is widely accepted as the best way to write code. Yes, it takes time to write tests, but it is an investment which leads to more resilient code as development progresses.
In this post, I am going to give a step-by-step introduction into how you can do continuous integration testing with Docker. I will be running the rspec test suite of the CloudFoundry project's Cloud Controller component, although the same process can be applied to any Ruby project.
As we conclude 2013 and prepare to start a new year of technological wonder, I thought it would be good to look back at this past year from ActiveState’s point-of-view in the arena of PaaS, Cloud Foundry and other interesting things such as Docker.
Last week, ActiveState released a beta version of the much anticipated Stackato v3.0. This release is a preview of what is to come later this year from the leading Enterprise Platform-as-a-Service (PaaS) solution, Stackato by ActiveState.
In a recent whirlwind trip to Japan, I met with Cloud Foundry users in Tokyo and Osaka. There is deep investment in Cloud Foundry in Japan. For example, NTT Communications providing a Cloud Foundry-based PaaS through its "Cloud N" service.