As a developer, you define the WordPress site in the form of a generic Cloud Assembly blueprint that can be deployed to any cloud vendor.
The use case blueprint consists of a WordPress application server, MySQL database server, and supporting components that are deployable to AWS, Azure, or vSphere-based clouds. The blueprint starts with a few components, and then grows as you modify existing components and add more components.
The examples from the first part of the use case included infrastructure that was set by a cloud administrator:
Two cloud accounts, AWS and Azure.
Three cloud zone environments:
Flavor mappings with small, medium, and large compute resources for each zone.
Image mappings for Ubuntu 16 configured in each zone.
Network profiles with internal and external subnets for each zone: devnets, testnets, prodnets.
Storage to support an archive disk, general storage for development and test, with fast storage for production.
The WordPress project includes all three cloud zone environments plus users who can try the use case.
Be familiar with your infrastructure values. For example, the use case example uses AWS for development and test, and Azure for production. When creating your own blueprint, substitute your own values, typically set by your cloud administrator.