The following series will help you understand vRealize Automation 8 and the new features with the latest edition. This article is getting started with vRealize Automation 8, here is a list of the terminology used.
Projects link users and cloud zones. Think of projects as groups that control who can use what cloud resources. Create projects that support the goals of your organization, ensuring that users have access to the appropriate zones.
Cloud zones associate compute resources with projects and account/regions to form the basis of deployable virtual machines. In addition, they enable you to define capabilities that Cloud Assembly matches with blueprint constraints to define where and how resources are configured for deployments.
Cloud vendors use flavors, or instance types, to express standard deployment sizings such as small (1 CPU,2 GB RAM) or large (2 CPU, 8 GB RAM) for compute resources. When you build a blueprint, you pick a flavor that fits your needs.
Cloud vendors use images to configure a VM based on OS settings, such as an ubuntu-16 configuration. When you build a blueprint, you pick an image that fits your needs. Map an image name to a value for each account/region. You can also add constraints and configuration scripts to further control resource placement.
Blueprints are specifications for the resources that you deploy. You can continuously improve a blueprint after you deploy it.
- Cloud Assembly, where you add and maintain your infrastructure, create application blueprints, and manage deployments.
- Service Broker, where you provide the blueprints and other templates to your consumers in a catalog. Your consumers can manage their deployments. You also create and apply policies.
- Code Stream, where you create and manage your continuous integration and continuous delivery of software.
- vRealize Orchestrator, where you design workflows that can turn anything into a service.
vRA 8 deployment with Easy Installer
Migration of vRSLCM 2.x version to LCM 8
vRA 8 deployment with LCM 8