Earlier in my programming days, my go-to example would have been foo.com. Well, not always. If we had any inside jokes on the team, I might put something clever in there for fun. On the Cloud Foundry backend team, one of our current inside jokes includes a picture of Bob Ross in the free space on one of our CI boards, so maybe in that case I would have gone with bobross.com or paintingclouds.com, just for fun, if I needed a fake URL for a test.
I think it was Ken Mayer who taught me that example.com is actually meant to be used in documentation and tests. example.com isn’t just some domain that some private party is using for the greater good; The Internet Engineering Task Force published RFC2606 which specifically says that example.
In early March we introduced our vision for the Cloud Foundry Open Platform-as-a-Service project at Pivotal, and laid out a strategy of furthering our broad ecosystem with deep engineering partnerships with external organizations.
“Adding full-time external committers has always been a goal of the team, and we are engaged with several organizations around putting dedicated resources on the extended engineering team”
As of today’s major collaboration announcement with IBM, we can now be explicit about one of the organizations we were already working with in March. Working with IBM and other external organizations over the last several months we have learned more about what it will take to scale our thriving community.
IBM has just announced it is joining the Cloud Foundry project and making it a component of their open cloud architecture. Pivotal and IBM has jointly announced a series of actions to further engage the community in Cloud Foundry.
A guest blog by Rachel Reinitz, an IBM Distinguished Engineer in IBM Software Services
As one of the IBMers who have been engaging with Pivotal, I’ve really enjoyed the collaboration and certainly learned a lot. So, I’d like to tell you about the IBM/Pivotal collaboration around developing an IBM Java and Liberty buildpack.
Buildpacks offer Great Potential
A key part of the Cloud Foundry architecture is the use of buildpacks to specify and compose runtime environments for a class of applications. Cloud Foundry has adopted buildpacks from Heroku.
This is a guest blog post by anynines, a Cloud Foundry hosted cloud provider from Europe.
In the past few years, the perception of cloud hosting has been revolutionized by the growth of IaaS and PaaS environments. However, many of the major hosting companies are US-based. In order to assure that data subject to European Union data privacy regulations stays in the EU, it might be important for some users to choose an IaaS that is completely EU-based (unlike AWS, for example).
We are committed to solving this challenge. Say “hello” to anynines – a solution for European cloud enthusiasts (or any others!) looking for safe, 100% European PaaS hosting.
Matching IaaS to your PaaS
Firstly, we needed an IaaS that was EU-based and that worked with our PaaS.