Resource tiering allows you to provision blueprints depending on demand. After you provision a deployment, you can adjust to changing workload demands by increasing or decreasing the number of instances of virtual or cloud machines in your deployment. In this scenario, you create several different storage reservation policies. According to he business requirements, you can then change the storage for the blueprint.
About this task
For example, assume that deployed a three-tiered application with a clustered application server node, a database node, and a load balancer node. Demand increases, and you find that the two instances of your application server node cannot handle all the traffic. Because your blueprint supports up to ten instances of the application server, and you are entitled to scale actions, you can scale out your application.
You configure three storage policies according to the storage tier that each individual application component requires. You allocate an individual NFS datastore to each storage tier.
This scenario gives detailed information on the procedures for a single-region deployment. You can also use these procedures for Region A of a dual-region deployment. If you want to use the procedures for Region B in a dual-region deployment, you have to use different IP address and machine names and might have to make some other changes.
Prepare for the deployment. See Preparing for Region A Scenario Deployment.
Perform the tasks in Configuring Reservation Policies and Network Policies in Region A.
Perform the tasks in Creating and Publishing Single Machine Blueprints in Region A.