Bluemix Cloud Foundry is upgrading from the Droplet Execution Agent (DEA) architecture to the new Diego architecture. The DEA architecture served the Cloud Foundry Foundation and Bluemix well, but continued innovation has delivered a broad range of improvements and enhanced the overall operation of the Cloud Foundry platform. As the world’s largest Cloud Foundry implementation, Bluemix benefits substantially from these enhancements.
We’re excited about the role IBM plays in the Cloud Foundry Foundation, the contributions we’ve made to key Cloud Foundry projects like Diego, and our support of Open Technology software like Cloud Foundry. This is a great step for Cloud Foundry and a strong move forward in our Bluemix cloud platform offering.
Get to know Diego
Diego is a new Cloud Foundry architecture with a set of capabilities that enhances the application development experience and features new capabilities for hosting and constructing cloud platforms, like IBM Bluemix. Diego is the path forward for future upgrades, expansions, and features.
The new architecture brings a number of changes to the Cloud Foundry platform that improve the overall operation and performance: an re-write from Ruby to Go allowed improvements to the overall design, a switch from a “DEA node” to a “Diego cell,” a new container management system called Garden that allows diverse operating system containers beyond Linux, the differentiation between single-run and long-running jobs, and an SSH package that allows direct login to the application container. These and many other exciting changes are detailed here.
Although new features have been (and will be) added to the application development capabilities of Cloud Foundry, existing applications don’t need many—if any—changes. But they do need to be deployed to the new Diego architecture on Bluemix.
The initial Bluemix Public generally available deployment of Diego will take place in January 2017. Existing workloads will run undisturbed on the existing infrastructure, with all new deployments occurring on the Diego infrastructure. A comprehensive migration effort is slated for early 2017 to make sure all current customer applications are moved to Diego.
Migrate your application to Diego
For a Bluemix Cloud Foundry application developer to proactively re-deploy applications, the steps are simple. Right now you can optionally deploy to the beta Diego infrastructure by using the command line to do a deploy with a special flag. After Diego becomes the generally available default architecture, all deployments default to Diego and the flag is no longer needed. In early 2017, IBM Bluemix will begin re-deploying un-migrated applications. For more details, see the steps in Application Deployment.
Learn more about Diego
Explore the new Diego infrastructure and dig into the full documentation for the Bluemix Cloud Foundry application operations:
Logs help you troubleshoot issues with your clusters and apps. Sometimes, you might want to send logs somewhere for processing or long-term storage. On a Kubernetes cluster in the IBM Cloud Container Service, you can enable log forwarding for your cluster and choose where your logs are forwarded.
Kubernetes development and adoption continues to grow at a rapid pace, and keeping current can be difficult without the right process and tools. For example, IBM Cloud Container Service launched with support for Kubernetes v1.5.6 earlier this year. Since that initial launch, the Kubernetes community provided 3 minor releases (v1.6, v1.7, and v1.8) and over 25 patch releases. By year's end there's likely to be another minor release and numerous patches. So with all this change, what's the best way to keep your cluster and apps up-to-date and secure?