Configuring IaaS for vSphere
Create credentials store item:
- Log in to vCAC as IaaS administrators
- Navigate to Infrastructure –> Endpoints –> Credentials.
- Select New Credentials.
Configuring IaaS for vSphere – Create vSphere Endpoint:
- Log in to vCAC as IaaS administrators
- Navigate to Infrastructure –> Endpoints –> Endpoints.
- Select New Endpoint –> Virtual –> vSphere.
- Type the URL for the vCenter Server instance in the Address text box. The URL must be of the type: https://hostname/sdk or https://IP_address/sdk. In my example, https://vc02.lab.local/sdk.
[box type=”warning”] If you don’t remember endpoint name provided to the vSphere agent during installation, create temporary endpoint and go to audit logs to determine endpoint name. Infrastructure > Monitoring > Log. You will find an entry in logs: This exception was caught: The attached endpoint ‘vCenter’ cannot be found, vCenter – is the name of endpoint. In my example, endpoint name is vc02.lab.local[/box]
Configuring IaaS for vSphere – Create a fabric group:
- Navigate to Infrastructure –> Groups –> Fabric Groups.
- Click New Fabric Group.
- Type a name in the Name text box.
- Description
- Assign fabric administrators
- Assign compute resources
Configuring IaaS for vSphere – Configure Machine Prefixes
Machine prefixes must conform to the following limitations
- Must contain only the ASCII letters a through z (case-insensitive), the digits 0 through 9 and the hyphen (-).
- Must not begin with a hyphen.
- No other symbols, punctuation characters, or blank spaces can be used.
- Should not be longer than 15 characters, including the digits (to conform to the Windows limit of 15 characters in host names). Longer host names are truncated when a machine is provisioned, and updated the next time data collection is run.
- vCloud Automation Center does not support multiple virtual machines of the same name in a single instance. If you choose a naming convention that causes an overlap in machine names, vCloud Automation Center does not provision a machine with the redundant name. If possible, vCloud Automation Center skips the name that is already in use and generates a new machine name using the specified machine prefix. If a unique name cannot be generated, provisioning fails.
- Navigate to Infrastructure –> Blueprints –> Machine Prefixes
- Add new prefix
Configuring IaaS for vSphere -Create a Business Group
Tenant administrators create business groups to associate a set of services and resources to a set of users. Users must belong to a business group to request machines.
- Log in to the vCloud Automation Center console as a tenant administrator
- Navigate to Infrastructure –> Groups –> Business Groups
- Type name, description
- choose machine prefix
- type manager’s email
- assign users to support and user roles
Configuring IaaS for vSphere -Virtual Reservations
A virtual reservation is a share of the memory, CPU, networking, and storage resources of one compute resource allocated to a particular business group. To provision virtual machines, a business group must have at least one reservation on a virtual compute resource. Each reservation is for one business group only, but a business group can have multiple reservations on a single compute resource, or multiple reservations on compute resources of different types.
In addition to the share of fabric resources allocated to the business group, a reservation can define policies, priorities, and quotas that determine machine placement.
- Log in to the vCloud Automation Center console as a fabric administrator.
- Navigate to Infrastructure –> Reservations –> Reservations.
- Click New Reservation –> Virtual –> vSphere (vCenter)
- In resources tab
Configuring IaaS for vSphere -Initial tenant configuration.
Some actions are required in order to successfully request and deploy virtual machine, create and publish blueprints in service catalogue.
Approvals
Approvals are one of the most important features of vCloud Automation Center. Approvals let administrators, managers of finance department control deployment, life cycle, decommissioning process.
Create a service
Service categories organize catalog items into related offerings to make it easier for users to browse for the catalog items they need.
- Log in to the vCloud Automation Center console as a tenant administrator or service architect.
- Navigate to Administration –> Catalog Management –> Services.
- Click the Add icon.
- Type a name in the Name text box.
- Description
- Choose Icon
- Status:
- Active
- Inactive
- Deleted
- Specify owner and support team
Add Catalogue Item to Service
[box type=”info”] Note: before that step you have to have blueprint created and published[/box]
- Log in to the vCloud Automation Center console as a tenant administrator, business group manager, or service architect.
- Navigate to Administration –> Catalog Management –> Services.
- Locate the service you want to use when adding or removing catalog items.
- In the Actions column, click the down arrow and click Manage Catalog Items.
Create entitlements:
You must specify the entitlement information first. This information includes the name and status of the entitlement and the business group whose selected users and groups are entitled to request the services and catalog items and perform the actions listed in the entitlement.
- Log in to the vCloud Automation Center console as a tenant administrator, business group manager, or service architect.
- Navigate to Administration –> Catalog Management –> Entitlement
- Click the Add icon.
- Type a name in the Name text box.
- Description
- from drop down mane choose status
- from drop down menu choose business group
- assign users and groups
- On Items & Approvals tab
- Add service, service catalogue and actions
vCloud Automation Center 6.0 series
- vCAC 6 series – Part 1 – Architecture
- vCAC 6 series – Part 2 – Prepare for deployment
- vCAC 6 series – Part 3 – Deploy VMware Identity Appliance
- vCAC 6 series – Part 4 – Deploy VMware vCAC Appliance
- vCAC 6 series – Part 5 – Installing IaaS components
- vCAC 6 series – Part 6 – Initial Configuration
- vCAC 6 series – Part 7 – Post Installation Tasks
- vCAC 6 series – Part 8 – Installing vSphere Agent
- vCAC 6 series – Part 10 – Prepare for provisioning
- vCAC 6 series – Part 11 – Create Blueprint
When adding my vCenter Server as an Endpoint, I do not see any compute resources. Do I have to install something on my vCenter server also?