Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)
In Part 1 of this series we walked through how you can use the SovLabs Property Toolkit and Template Engine to configure vRealize Automation (vRA) for our environment input. In this second part of the series, we’re going to walk through setting up the Application and Compliance inputs for our particular use case. If you are starting to see smoke, don’t be alarmed. It’s just our Genie being let out of the lamp.
In Part 1, we determined that the required options for our Application input will be:
- WordPress
- Microsoft SQL
Determine the Outcome
In this scenario, the selection of the application will have a significant impact on the outcome. However, while we need to think about the application, we also need to look at the larger picture. What do I mean by “the bigger picture”? Well, once we figure out the desired outcome for each of these items, we need to think about how each item relates to the environment and the choices we made in Part 1.
What if the requester chooses WordPress as the application and Production as the environment? Alternatively, what if they choose Microsoft SQL and Development? Will the outcome of the application differ based on the environment to which it is being deployed?
Some things to consider:
- Do the workload specs change based on the environment selection?
- Do development, test, and production instances have the same CPU and Memory requirements?
- Do any of the integrations change based on application and environment?
- Do WordPress and Microsoft SQL have the same backup requirements?
- Does this requirement change based on which environment the workload is being deployed to?
- What else could affect the outcome?
To read the entire article please see the original article on the SovLabs Blog.