So Cloud Automation Services are here, what’s next? How can I use it?
In our next series of posts Erik and I will explain several technical details of these services and how to use them, starting off with Cloud Assembly and Service Broker. Later we will dive into the world of CI/CD with CodeStream.
Cloud Assembly provides an abstraction layer across multiple clouds using a Cloud API which makes it possible to create declarative templating constructs, which VMware calls ”Blueprints”. Blueprints can deploy cloud agnostic resources (compute, storage, network etc.) across clouds. At this moment Cloud Assembly supports Amazon AWS, Microsoft Azure, VMware Cloud on AWS and vSphere (with or without NSX-V/T).
Service Broker delivers a common catalog that aggregates content in native formats from multiple clouds and platforms including services designed in Cloud Assembly. Service Broker provides simple, self-service access to multi-cloud infrastructure and application resources from a single catalog, without requiring proprietary tools. With Service Broker , operations teams can more effectively govern resource access and use and enforce security, deployment and business policies across multi-cloud environments.
Here’s a list of topics which we want to write about in our new Cloud Automation blog series. This list is not finalized and new topics will be added. So come back regularly to check for new posts!
7 – …
P.S. If you want to evaluate Cloud Assembly or other Cloud Services, go to VMware Cloud.
Other articles in the series Cloud Automation Services:
- So Cloud Automation Services are here, what’s next? How can I use it?
- Deploying a Data Collector for Cloud Assembly
- Setting up a vSphere Cloud Zone in Cloud Assembly
- Designing your first Cloud Assembly blueprint for vSphere
- Integrate Puppet with Cloud Assembly
- How to create a Cloud Agnostic service in Cloud Assembly
- Using input parameters to create dynamic blueprint requests in Cloud Automation Services