Cloud Foundry on Azure support for Diego and open source service brokers
Following the general availability of Cloud Foundry on Azure last November, we introduced new Cloud Foundry on Azure capabilities to support Diego, running .Net workloads, multiple open source service brokers, and optimized Bosh-Setup ARM template.
Diego support on Azure
Deploy Diego on Azure Cloud Foundry
With this release Diego is fully supported on Azure as an advanced option. For those who are new to Diego, Diego is a new elastic runtime for Cloud Foundry, it serves as an app execution, container-based pluggable scheduler and health check manager, replacing the DEAs and Health Manager. For more background information, please visit the GitHub repository.
Follow this guidance to deploy Diego on Azure for your Linux workloads.
Running .NET workloads with Diego
Another highly anticipated feature Diego brings to us is the support for .NET workloads. Follow this guidance to push your first .NET application to Cloud Foundry on Azure.
Service brokers for open source services
Cloud Applications typically depend on services (like database, messaging and other SaaS services) to run, store data, and communicate. A service can be integrated with Cloud Foundry via a service broker that enables developers to provision service instances and bind the credentials to developers’ applications. For detailed background, check out this document on deployment and configuration of Service Brokers.
Cloud Foundry community provided a rich set of service brokers for many popular open source services, that work with any Cloud Foundry enabled cloud platforms. For example, you can find the release for MySQL service broker, or community contributed services for multiple service brokers including MongoDB.
Deploying MySQL and MongoDB Services on Azure
Utilizing community service broker releases listed above, MySQL and MongoDB can be deployed on Azure using Bosh, and configured for cloud applications. For detailed step-by-step guidance, please check the links below.
Additional Open Source Service Brokers
With a similar approach, you can deploy other open source services on Azure. You will need to replace the platform specific parameters with Azure settings before deployment.
Here we use community contributed services as example. This release provides the following service brokers: Elastic Search, Memcached, MongoDB, PostgreSQL, RabbitMQ, Redis, Bblob , Swift.
Refer to this guidance for generating the manifest for Azure settings, then follow the community guidance to deploy the above service brokers.
Service brokers for Azure services are coming soon!
Enhancements to the Azure Resource Manager template
The Azure Bosh-Setup ARM template is updated, addressing customer feedback after GA:
- Utilize xip.io for DNS service, avoiding the dependency on local VM for DNS service
- Support creating the dev-box with SSH Key for enhanced security
- Automatically download and configure the manifest of Bosh and Cloud Foundry, based on the parameters user has entered
- Support automatically completing Bosh deployment, so user only needs to start with CF deployment
- Optimize the user experiences by reducing the number of parameters, and enhancing the value validating and error handling
Advanced networking configurations
More advanced features are available to enable enterprise scenarios for high availability support, including integrating Azure DNS service, Availability Set, Multiple HAProxy with Cloud Foundry on Azure, please check the “Advanced Configurations and Deployments” section in the GA guidance.
As always we look forward to hearing your feedback and suggestions.
Source: Microsoft Azure News