VCAP-CID Study Notes: Objective 2.1

This is Objective 2.1 in the VCAP-CID blueprint Guide 2.8. The rest of the sections/objectives can be found here.

Bold items that have higher importance and copied text is in italic.


  • Identify what can be included in a published catalog.
    • A vCloud Catalog can include several things, most of them vApps of various sizes and ISO files.
      • vApp with one VM.
      • vApp with several VM’s with various level of connection between them.
      • Media files: ISO files for the installtion of new VM’s OS inside a vApp. Floppy disks are also supported. Please note that users will not see the media files unless a Organization admin moves them to their Organization Catalog and shares them with the users.
    • A Published Catalog or a Global Catalog is a catalog where a vCloud admin has made a certain catalog public to all organization in the cloud.
  • Identify what can be included in a private catalog.
    • Same things you can in a published catalog.
    • But you will need to have access to the catalog to be able to create VM’s from it.
  • Identify permission controls for catalogs.
    • This picture is snapped from the vCloud Director Users Guide and says it all:
    • VCAP CID 2-1-1
  • Explain the functionality of a catalog.
    • The best way to explain what a catalog is is to quote the VCAT Consuming a VMware vCloud documentation:
    • Organizations can offer the following types of service catalogs to their users or customers:
      • A vCloud service catalog – Includes predefined vApps, virtual machines, and images (operating systems and applications) that users can deploy within an organization
      • An operational service catalog – Includes operational features such as development of a vCloud service catalog, backup and recovery services, archival services, managed services, and migration services.
    • And then a quote from the vCloud Director User’s Guide:
      • A catalog is a container for vApp templates and media files in an organization. Organization administrators and catalog authors can create catalogs in an organization. Catalog contents can be shared with other users in the organization and can also be published to all organizations in the vCloud Director installation.
      • There are two types of catalogs in vCloud Director; organization catalogs and public catalogs. Organization catalogs include vApp templates and media files that you can share with other users in the organization. If a system administrator enables catalog publishing for your organization, you can publish an organization catalog to create a public catalog. Organization administrators from any organization in the vCloud Director installation can view the vApp templates and media files in a public catalog and copy those files to a catalog in their organization for use by their members.
      • There are two ways to add vApp templates to a catalog. You can upload an OVF package directly to a catalogor save a vApp as a vApp template.
      • Members of an organization can access vApp templates and media files that they own or that are shared to them. Organization administrators and system administrators can share a catalog with everyone in an organization, or with specific users and groups in an organization.

Skills and Abilities

  • Based on application requirements, determine appropriate vApp configuration.
    • Lets start with a short introduction to what a vApp is:
      • A vCloud vApp differs from a vSphere vApp in the way it is instantiated and consumed in the vCloud. A vApp is a container for a distributed software solution and is the standard unit of deployment in vCloud Director. It allows power-on and -off operations to be defined and ordered, consists of one or more virtual machines, and can be imported or exported as an OVF package. A vCloud vApp can have additional vCloud-specific constructs such as networks and security definitions.
    • A vApp can contain a single VM or multiple VM’s that can have various interconnections between them.
    • If using single VM vApps the usual VM design considerations apply
      • Single vCPU unless needed
      • Newest VMware tools
      • Don’t use Reservations and limits unless the design requires it.
      • Use VMXNET3 where supported
      • Secure VM’s like you would physical machines
      • Use naming conventions.
    • Lets say you have a Database, it needs more then 32 vCPU, you should upgrade the virtual hardware version to at least 9.
  • Determine appropriate storage configuration for a given vApp.
    • This most likely is related to where a VM in a vApp should reside.
    • Let’s say a vCloud installation has 3 tiers of storage, Gold, Silver and Bronze. You can select which VM should use each tier. So a database VM should likely go to a Gold tier, while a Development machine would use the Bronze tier.
  • Given customer requirements, determine appropriate catalog design.
    • A Catalog can include vApps, and media files. Access to those catalogs can be controlled.
  • Determine the impact of given security requirements, on a catalog structure.
    • The only sequrity feature with catalog structure is permissions. You can make the changes you need so only a subset of people/deparment can access certain catalogs.

About larushjartar
VMware Specialist and IBM Technician.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: