Skip to content
vWorld
Menu
  • Main Page
  • About
  • Study Guide
    • VCAP-CMA Deploy 2018
Menu

Objective 1.4 – Create and manage property definitions/groups and component profiles

Custom Property

Custom properties are using to add values or override existing for configuring some parameters such as network, agent and other in process of deployment VM.

For creating a custom properties you need to be a

Tenant administrator Customize tenant branding. Manage tenant identity stores. Manage user and group roles. Create custom groups. Manage notification providers. Enable notification scenarios for tenant users. Configure vRealize Orchestrator servers, plug-ins and workflows for XaaS. Create and manage catalog services. Manage catalog items. Manage actions. Create and manage entitlements. Create and manage approval policies. Monitor tenant machines and send reclamation requests.
Fabric administrator Manage property groups. Manage compute resources. Manage network profiles. Manage Amazon EBS volumes and key pairs. Manage machine prefixes. Manage property dictionary. Create and manage reservations and reservation policies in their own tenant. If this role is added to a user with IaaS administrator or system administrator privileges, the user can create and manage reservations and reservation policies in any tenant.

Login to the web page and go to the Administrator –> Property Dictionary –> Property Definitions

In new we need to provide few details about new property.

After creation we are able to add the custom property to the blueprint.

Then this is visible in Request.

Custom Properties can be used for choosing the Reservation profile, network profile or vm placement which can be done by connecting this with vRealize Orchestrator

  • Property Group

Property Group is a set of property which we can be combine in one piece to not adding it one by one

  • Component Profile

Since VMware release vRealize Automation in version 7.3 we are able to use Component Profile which help us to create Profile for VM size or from what image it should be created. We are not able to create the new one but we are able to edit existing.

for example we can edit the size information

After creating we can set this in our blueprint.

Now in request process we are not providing the values for size only choose it from drop down list from specific profiles.

Share with:


Recent Posts

  • From Commit to Cluster: Mastering GitOps with Argo CD on VMware Cloud Foundation
  • The Full Power of VCF Automation in Action: How I Connect the Dots and Build a Multi-Tier App with Kubernetes Objects.
  • From Code to Kubernetes Cluster with Chiselled Ubuntu Images on VMware
  • From Zero to Database-as-a-Service: A Deep Dive into VMware Data Services Manager 9.0 and VCF Automation
  • Complete Guide: Configuring SSO in VMware Cloud Foundation with Active Directory and VCF Automation Integration

Archives

Follow Me!

Follow Me on TwitterFollow Me on LinkedIn

GIT

  • GITHub – vWorld GITHub – vWorld 0
© 2026 vWorld | Powered by Superbs Personal Blog theme