TASK 3
As the Cloud Administrator, you have been tasked to do the following;
1. Create a new operating system image. 2 Create a new machine size. 3. Add two new Cloud templates:
a Import the first Cloud template from the provided file.
b. Create the second Cloud template based on the imported Cloud Template with the following requirements:
i. Allow the user to pick from a list of operating system images.
ii. Allow the user to pick from a list of machine sizes.
iii. Deployment must use the selected input values.
iv. Ensure you are able to review/compare any previous changes that have been made since the Cloud template was cloned in Cloud Assembly.
NOTE: Do not deploy the Cloud template
Information required to complete the tasks:
• vRealize Automation FODN: vr-automation.corp.local
• Cloud Admin Username: vcapadmin@corp.local
• Cloud Admin Password: VMwarel!
• vRA Project Name: Jupiter
• Flavor Mapping Name: extra large - Flavor Mapping Config:
o Account: vSphere Private Cloud ° Region: Local Datacenter o CPUs: 4 CPU o RAM: 16GB
• Image Mapping Name Windows Server 2019
• Image Mapping Configuration:
o Account: vSphere Private Cloud o Region: Local Datacenter o Image: windows2019
• Imported Cloud template Name: Jupiter Ubuntu Server
• Imported Cloud template File: C:VExam Files\Question 3\jupiter.yaml
• New Cloud template Name: Jupiter Cloned Server
• New Cloud template Size Input:
o Name: size
o Title: Select a Size
o Valid Options: small, medium, extra large
• New Cloud template Image Input:
o Name: image
o Title: Select an OS Image
o Valid Options: Windows Server 2019. Ubuntu18
TASK 1CMA DEPLOY
As the Cloud Administrator. you have been tasked to
1. Create a new Cloud Zone
2 Create a new Project
3. Update the default pricing card.
Information requited to create the Cloud Zone and the Project;
. Account / Region: AWS - US West / us-west-2
• Name: Mercury AWS Cloud Zone
• Placement Policy: Default
• Include only Availability Zones us-west-2a and us-west-2c
• Capability Tags
o Key: region
o Value: us-west
• Project Name: Mercury
• Project Administrators: Project Mercury Admins group
• Project Members: Project Mercury Users group
• Cloud Zones: vRA-Managed vSphere Datacenter. Mercury AWS Cloud Zone
Information required to update the Pricing Card:
• Assign only for project "Mercury"
• Pricing is Rale based, as follows:
o vCPU cost is S10 per vCPU. charge monthly and only charge when powered on
o Memory cost is S5 per GB. charge monthly and only charge when powered on
o Storage cost is S1 per GB. charge monthly and always
TASK 8
As the Cloud Administrator, you must ensure that each virtual machine deployed by the Neptune Project is configured to a standard state.
You have already created a state file in the environment that can be used to meet this requirement.
The following tasks need to be completed:
Update the existing Neptune VMware Cloud Template to ensure that:
• The vRealize Automation SaltStack Config minion is installed during deployment.
• The base configuration state file is always run during deployment. The minion id of the machine should be dynamically assigned using the machine name.
• A secret should be used to ensure the remote access password is not visible within the cloud template.
NOTE: Do not deploy the Cloud template.
The following information has been provided to assist you in these tasks:
The following information has been provided to assist you in these tasks:
• vRA FQDN: vt-aulomation.corp.local
• Cloud Admin Username: vcapadmin@corp.local
• Cloud Admin Password: VMwarel!
• vRA Project Name: Neptune
• Existing Cloud Template Name: Neptune Ubunlu
• vRA-SSC Master Minion Id: saltstack
• vRA-SSC Master Id: saltstack_enterprise_installer
• vRA-SSC Environment: sse
• State File Location: /neptune/base/init.sls
• Remote Access Username: salt-user
• Remote Access Password: VMware1
• Password Secret name: salt-password
