VCAP-CID Study Notes: Objective 1.1

This is Objective 1.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.

Skills and Abilities

Distinguish between virtualization, automation and cloud computing.

  • Virtualization is basic virtualization of services or applications. Instead of running it on physical machine it is run on a virtual machine on top of hypervisor. At most you have multiple hypervisors (ESXi hosts) in a cluster, managed by a management service (vCenter). Installing new services still require manual work of installing a operating system (OS), either by installing, or by creating from templates, and then installing the application on top of the OS.
  • Automation is a way to automate know workflows, eg. A script that creates a new VM from a template, updates the network config, adds it to a domain, and maybe in some cases installs a application on said VM. There is no real cost analysis, service agreements behind the automation process itself. Just putting some otherwise manual processes together in a script/workflow.
  • Cloud computing is way to change IT to be more service oriented. Instead of focusing on VM’s it has a new focus on services that run on the VM’s. If you compare normal virtualization and simple automation to cloud computing, you can say that cloud computing includes both virtualization and automation but with the goal of further improve cost effciency , quality of service and business agility. What cloud computing services need to offer has been defined by the NIST (National Institute of Standards and Technology):
    • Broad network access – Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin client or thick client platforms.
    • Rapid elasticity – Capabilities can be provisioned to scale out quickly and to be released rapidly—in some cases, automatically. Rapid elasticity enables resources to both scale out and scale in quickly. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
    • Measured service – Cloud systems automatically control and optimize resource usage by leveraging a metering capability at some level of abstraction appropriate to the type of service. Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and the consumer of the utilized service.
    • On-demand self-service – A consumer can unilaterally automatically provision computing capabilities as needed without requiring human interaction with each service’s provider.
    • Resource pooling – The provider’s computing resources are pooled to serve multiple consumers, using a multitenant model with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. A sense of location independence results because the subscriber generally has no knowledge of or control over the exact location of the provided resources, but the subscriber might be able to specify location at a higher level of abstraction.
  • Just to include what VMware believes a IaaS require (from the vCAT Introduction document):
    • A cloud must be built on a pooled, virtual infrastructure. Pools include not only CPU and memory resources, but also storage, networking, and associated services.
    • The cloud should provide application mobility between clouds, allowing the consumer to enter and leave the cloud easily with existing workloads. The ability to use existing consumer tools to migrate workloads to or from the cloud is highly desirable. Mobility of workloads between clouds requires cross-cloud resource management.
    • The cloud should be open and interoperable, allowing the consumption of cloud resources over open, Internet-standard protocols. Access to cloud resources does not require any other specific network protocols or clients.
    • Cloud consumers should pay only for resources they consume or commit to consuming.
    • The cloud should be a secure, trusted location for running cloud consumer workloads.
    • Cloud consumers should have the option and capability to protect their cloud-based workloads from data loss.
    • Cloud consumers are not responsible for maintaining any part of the shared infrastructure and do not need to interact with the cloud provider to maintain the infrastructure. They are not responsible for storage and network maintenance, ongoing cloud infrastructure patches, or business continuity activities. The cloud should be available to run high-availability workloads, and any faults occurring in the cloud infrastructure should be transparent to cloud consumers as a result of built-in availability, scalability, security, and performance guarantees.

Distinguish between private, public, hybrid and community cloud computing.

  • The VMware vCloud Architechture Toolkit (vCAT) Service Defenitions document has this covered:
    • Private vCloud – The vCloud infrastructure is operated solely for an organization and can be managed by the organization or a third party. The infrastructure can be located on-premises or off-premises.
    • Public vCloud – The vCloud infrastructure is made available to the general public or to a large industry group and is owned by an organization that sells vCloud services.
    • Hybrid vCloud – The vCloud infrastructure is a composite of two or more vCloud instances (private and public) that remain unique entities but are bound together by standardized technology. This enables data and application portability, such as cloud bursting for load balancing between vCloud instances. With a hybrid vCloud, an organization gets the advantages of both, with the capability to burst into the public vCloud when needed while maintaining critical assets on-premises.
    • Community vCloud – Several organizations share the vCloud infrastructure. The infrastructure supports a specific community that has shared concerns, such as mission, security requirements, policy, and compliance considerations. It can be managed by the organizations or a third party and can be located on-premises or off-premises.
  • But I really like to include the defenition in the vCAT Introduction document as well as it is even more detailed and explanatory:
    • Private cloud:
      • A private vCloud (also known as an internal vCloud.) operates on private networks, where a single company maintains accessible resources behind the firewall. In many cases, all the tenants share one legal entity. For example, a university might offer IaaS to its medical and business schools, or a company might do the same for various groups or business units. The private vCloud can be managed by the enterprise and hosted on-premise or operated on a dedicated infrastructure provided by a vCloud service provider or systems integrator. In any case, a private vCloud must conform to the organizational security constraints.
    • Public cloud:
      • A public vCloud offers IT resources as a service through external service providers and is shared across multiple organizations or the Internet. This can be viewed as a vCloud infrastructure that one organization operates and that multiple, legally separated organizations use.
      • A public vCloud is provisioned for open access and might be owned, managed, and operated by one or more entities.
      • A public vCloud provider might also support a private, community, or hybrid vCloud.
    • Hybrid cloud:
      • A hybrid vCloud combines the benefits of the private and the public vCloud, with flexibility and choice of deployment methods.
      • A hybrid vCloud consists of multiple, linked vCloud infrastructures. These distinct vCloud infrastructures can be private, community, or public; but they must meet a set of requirements that the providers define and the consumers agree to. Connecting these vCloud instances requires data and application mobility, as well as management.
      • When load-balancing between vCloud instances (cloud bursting), use a consistent monitoring and management approach when migrating an application or data workload. For the theory behind cloud bursting, see the Cloud Bursting document.
    • Community cloud:
      • A community vCloud is a specific public vCloud use case in which the cloud is shared, and typically owned, by a group of organizations with a common set of requirements. In many cases, the organizations also include some level of legal separation. Community vCloud resources are shared, with some parts under central control and other parts with defined autonomy. A vCloud built for government, education, or healthcare is an example of a community vCloud.
      • A community vCloud can be offered by a traditional service provider, by a member of the community, or by a third-party vendor and hosted on one or more sites. It can be placed on-premises at one or more of the organizations’ sites, off-premises at a vCloud provider site, or both on- and off-premises.

Analyze a customer use case to determine how cloud computing can satisfy customer requirements.

  • Lets go over some use cases which in turn represents business problems which can be addressed with vCloud services (and a services definition). These use cases are taken from the vCAT Service Defenitions document and further explained here.

VCAP_CID_UseCase_01

    • The Use Case is modernization, a very general use case, but its further explained in the description. The use case is created to address the problem the organization sees with its current IT infrastructure, which is that the business services, processes and legacy applications are not allowing the business to stay competetive. Or in non-IT terms, its taking to to long finish new projects as the focus is wrong and processes are lacking.
    • Risks are the thing that could happen if the use case is not addressed.
    • As you can see a Use Case is really a problem that that can be addressed with  a set of requirements based on cloud computing definitions, and if the problem isn’t address it could have several negative consequences.
      • Make infrastructure more service oriented – defenition of cloud computing.
      • Modernize applications – map what service applications is offering and how it can be packaged into the XaaS model (dependencies etc)
      • Improve speed to market – Automate known/new processes and application deployment into workflows that can be offered as a service to customers.

VCAP_CID_UseCase_02

    • The Use Case is about increasing business capacity and allowing it scale rapidly. So it takes to long to scale compute/storage/network resources to support seasonal or periodic business demand. So when it holiday season everything slows down due to overutilized capacity of resources.
      • Consumers can scale capacity – using the workload mobility defenition. Users can create the workload in other clouds, which have the same security requirements (eg. hosted private cloud – or a hybrid cloud like it’s called)
      • IT can scale up, down, in and out – IT is no longer based on a finite pool of resources but are consumed with 3 distinct models, Pay-as-you-go, Allocated resources with a change of growth, and reserved resources. So business units can scale as they want. And as for the service provider, adding new computer resources are automated as well for quicker capacity growth (Auto deploy, NSX, vSAN, vVOLs etc…)
      • The last two are a similar to the upper two requirements. It’s all about speeding/automating the process of increasing/decreasing resources.

VCAP_CID_UseCase_03

    • The Use Case is about speeding up provisioning of TEST/DEV services. It takes to long for IT to create TEST & DEV environments that are used develop new products and services.
      • Developers and testers can create the environment needed from a predetermined catalog of services to carry out further development of the application or test it in a closed off environment.
      • It’s about automating the provisioning, but IT(or business units) still needs to approve the process to control the usage of capacity. And cost show-back is used to give business units accountability of the usage of resources.

VCAP_CID_UseCase_04

    • The Use Case is based on creating a cloud environment that runs workloads that need to comply to certain security standards. This might include eg. PCI DSS.
      • By using vCenter Configuration Manager whole environments can be tracked for changes and compliancy to many security standards. But please note this use case will require design requirements for both the logical and physical infrastructure.
      • By using vCloud Network and Security, or NSX network isolation can be achieved. If using network isolation with PCI DSS, please refer to the latest PCI DSS documentation on design considerations for virtual environments.

Given a customer use case, determine the appropriate cloud computing model.

  • Please note the following section is bit of simplification on how to determine a correct cloud model for a use case, as this process involves more than just get a couple of requirements and than picking a cloud model. But still a good practice…
  • Cloud computing models include both deployment models (Private, Public, Community, Hybrid clouds) and service models (IaaS, PaaS, SaaS, DaaS, DRaaS and really just XaaS)
    • To define the most used ones the  vCAT Service Definitions document does a good job:
      • Software as a Service (SaaS) – Business-focused services are presented directly to the consumer from a service catalog.
      • Platform as a Service (PaaS) – Technology-focused services are presented for application development and deployment to application developers from a service catalog.
      • Infrastructure as a Service (IaaS) – Infrastructure containers are presented to consumers to provide agility, automation, and delivery of components.
        • IaaS serves as a foundation of additional service offerings, such as PaaS, SaaS and DaaS.
  • If we use the use cases above:
    • Use Case 1: This use case want to modernize their IT infrastructure from a legacy environment to a cloud environment. A private cloud using IaaS would be a good start (and I’m only basing that on the requirements in this single use case).
    • Use Case 2: This use case is to increase business capacity with faster scaling. A private cloud using IaaS would be a good start. Lots of design decision would be based on this requirement though (use of automation of capacity scaling – adding servers, storage, network, and letting customers control their resource usage)
    • Use Case 3: This use case need TEST/DEV environments to be deployed quicker, self-servicing and automated. More information is needed to determine this one, either a private cloud using IaaS, and on top of that you could go for PaaS solution. Or you can use a public cloud,or even hybrid cloud, it all depends on security requirements, data locality requirements or availability requirements just to name a few.
    • Use Case 4: This use case is about making sure the cloud environment comply to certain security standards. A private cloud is a must, and at least a IaaS. But the design would have a lot thing to consider both in the logical or physical design (layout of infrastructure based requirements of security standards etc.)

VCP-IaaS vs. VCP-Cloud: Cloud Exam Faceoff

Today (and today is 13th February 2013) VMware released the VCP-Cloud exam, which is in turn gives you the right to call yourself VCP-Cloud certified.

Attention! In February 2014 VMware released yet another VCP-Cloud exam, VCPC550 which is based on vCloud Director 5.5 and vCloud Automation Center 5.2.

THIS BLOG POST COMPARES VCP-CLOUD (VCPC510) to VCP-IaaS (VCPVCD510)

But there are two paths to the certification:

  1. If you have VCP-DV, you can take the VCP-IaaS exam and then be VCP-Cloud certified.
  2. If you complete one of the prerequisete courses you can take the VCP-Cloud exam and then be VCP-Cloud Certified.
    • The prerequisetes courses are vCloud Director: Install, Configure, Manage or VMware vCloud: Deploy and Manage the VMware vCloud (v 1.5).

As you can see we have a VCP-Cloud and a VCP-IaaS exam to acquire VCP-Cloud certification.

Comparison:

If we compare the two exams they are similar on some levels, but the amount of sections on each of them to process is HUGELY different. Lets the comparing begin.

Lets start with amount of questions and time you have to complete them:

  • VCP-IaaS: 85 Question and 90 minutes (plus non-english minutes for those applicable)
  • VCP-Cloud: 240 questions and 225 minutes ( note: the blueprint  (v. 2.21) does not state the non-english minutes, but I’m guessing they forgot to add it to the text)

Comment: There is a good reason for this huge difference in the exams, and that’s that VCP-Cloud has 7 extra sections to learn.

Next I want to compare the sections of each exam:

  • VCP-IaaS: 8 sections -> Install&Configure, Users&Roles, Chargeback, Networking, Organizations, Resources, Catalogs, Monitor.
  • VCP-Cloud: 15 sections -> Install&Configure vCenter/ESXi, vSphere Networking, vSphere Storage, Administer VM’s and vApps, Establish and Maintain Service Levels, Troubleshooting&Alarms, Monitor&Alarms, Install&Configure, Users&Roles, Chargeback, Networking, Organizations, Resources, Catalogs, Monitor.
    • The text in bold is all about Infrastructure, and the rest is the same as the IaaS exam.

Comment: As you can see VMware has put a mini VCP-DV exam into the VCP-Cloud exam, as well as the whole of IaaS exam. So you can safely say that its made for people who don’t have the VCP-DV certification.

What? Isn’t that 2 exams in one?

So if VCP-Cloud has a mini-VCP in it, why shouldn’t you just go for the VCP-DV? Let the comparing continue:

  • VCP-DV: Install&Configure vCenter/ESXi, vSphere Networking, vSphere Storage, Administer VM’s and vApps, Establish and Maintain Service Levels, Troubleshooting&Alarms, Monitor&Alarms
  • VCP-Cloud (Infrastructure sections): Install&Configure vCenter/ESXi, vSphere Networking, vSphere Storage, Administer VM’s and vApps, Establish and Maintain Service Levels, Troubleshooting&Alarms, Monitor&Alarms

They look exactly the same,  but when you look closer there are slight differences. Lets take a closer look (red are the same!!!!!):

VCP-DV (Blueprint v. 2.5) VCP-Cloud (Blueprint v. 2.3)
Section 1 – Plan, Install, Configure and Upgrade vCenter Server and VMware ESXi Section 1 – Plan, Install, Configure and Upgrade vCenter Server and VMware ESXi
Objective 1.1 — Install and Configure vCenter Server Objective 1.1 — Install and Configure vCenter Server
Knowledge Knowledge
• Identify available vCenter Server editions • Identify vCenter Server requirements
• Size the vCenter Server database • Identify vCenter Server database requirements
Install vCenter Server into a virtual machine • Install vCenter Server
Deploy the vCenter Appliance • Deploy the vCenter Appliance
• Install additional vCenter Server components • Identify VMware vSphere® Client requirements
• Install/Remove vSphere Client plug-ins • Install/Remove vSphere Client plug-ins
• Enable/Disable vSphere Client plug-ins • Enable/Disable vSphere Client plug-ins
• Determine use case for vSphere Client and Web Client • Determine use case for vSphere Client and Web Client
• Determine availability requirements for a vCenter Server in a given vSphere implementation  
• License vCenter Server  
Objective 1.2 – Install and Configure VMware ESXi Objective 1.2 – Install and Configure VMware ESXi
Knowledge Knowledge
• Perform an interactive installation of ESXi • Perform an interactive installation of ESXi using media or PXE
• Deploy an ESXi host using Auto Deploy • Identify ESXi host requirements
• Configure NTP on an ESXi Host • Configure NTP on an ESXi Host
• Configure DNS and Routing on an ESXi Host  
• Enable/Configure/Disable hyperthreading  
• Enable/Size/Disable memory compression cache  
• License an ESXi host  
Objective 1.3 – Plan and Perform Upgrades of vCenter Server and VMware ESXi Objective 1.3 – Plan and Perform Upgrades of vCenter Server and VMware ESXi
Knowledge Knowledge
• Identify upgrade requirements for ESXi hosts • Identify available vSphere editions and features
• Identify steps required to upgrade a vSphere implementation • Determine appropriate vSphere edition based on customer requirements
• Upgrade a vNetwork Distributed Switch  
• Upgrade from VMFS3 to VMFS5  
• Upgrade VMware Tools  
• Upgrade Virtual Machine hardware  
• Upgrade an ESXi Host using vCenter Update Manager  
• Determine whether an in-place upgrade is appropriate in a given upgrade scenario  
Objective 1.4 –Secure vCenter Server and ESXi
Knowledge
• Identify common vCenter Server privileges and roles
• Describe how permissions are applied and inherited in vCenter Server
• Configure and administer the ESXi firewall
• Enable/Configure/Disable services in the ESXi firewall
• Enable Lockdown Mode
• Configure network security policies
• View/Sort/Export user and group lists
• Add/Modify/Remove permissions for users and groups on vCenter Server inventory objects
• Create/Clone/Edit vCenter Server Roles
• Add an ESXi Host to a directory service
• Apply permissions to ESXi Hosts using Host Profiles
• Determine the appropriate set of privileges for common tasks in vCenter Server
Objective 1.5 – Identify vSphere Architecture and Solutions
Knowledge
• Identify available vSphere editions and features
• Identify the various datacenter solutions that interact with vSphere (View, SRM, Lab Manager, etc)
• Explain ESXi and vCenter Server architectures
• Explain Private/Public/Hybrid cloud concepts
• Determine appropriate vSphere edition based on customer requirements
Section 2 – Plan and Configure vSphere Networking Section 2 – Plan and Configure vSphere Networking
Objective 2.1 – Configure vNetwork Standard Switches Objective 2.1 – Configure vNetwork Standard Switches
Knowledge Knowledge
• Identify vNetwork Standard Switch (vSS) capabilities • Identify vNetwork Standard Switch capabilities
• Create/Delete a vNetwork Standard Switch • Create/Delete a vNetwork Standard Switch
• Add/Configure/Remove vmnics on a vNetwork Standard Switch • Add/Configure/Remove vmnics on a vNetwork Standard Switch
• Configure vmkernel ports for network services • Configure vmkernel ports for network services
• Add/Edit/Remove port groups on a vNetwork Standard Switch • Add/Edit/Remove port groups on a vNetwork Standard Switch
• Determine use case for a vNetwork Standard Switch • Determine use case for a vNetwork Standard Switch
Objective 2.2 – Configure vNetwork Distributed Switches Objective 2.2 – Configure vNetwork Standard and Distributed Switches
Knowledge Knowledge
• Identify vNetwork Distributed Switch (vDS) capabilities • Identify vNetwork Distributed Switch capabilities
• Create/Delete a vNetwork Distributed Switch • Create/Delete a vNetwork Distributed Switch
• Add/Remove ESXi hosts from a vNetwork Distributed Switch • Add/Remove ESXi hosts from a vNetwork Distributed Switch
• Add/Configure/Remove dvPort groups • Add/Configure/Remove dvPort groups
• Add/Remove uplink adapters to dvUplink groups • Add/Remove uplink adapters to dvUplink groups
• Create/Configure/Remove virtual adapters • Create/Configure/Remove virtual adapters
• Migrate virtual adapters to/from a vNetwork Standard Switch • Migrate virtual adapters to/from a vNetwork Standard Switch
• Migrate virtual machines to/from a vNetwork Distributed Switch • Migrate virtual machines to/from a vNetwork Distributed Switch
• Determine use case for a vNetwork Distributed Switch • Determine use case for a vNetwork Distributed Switch
  • Edit general vNetwork Distributed Switch settings
  • Configure dvPort settings
Objective 2.3 – Configure vSS and vDS Policies Objective 2.3 – Configure vSS and vDS Policies
Knowledge Knowledge
• Identify common vSS and vDS policies • Identify common vSS and vDS policies
• Configure dvPort group blocking policies  
• Configure load balancing and failover policies • Configure load balancing and failover policies
• Configure VLAN settings • Configure VLAN settings
• Configure traffic shaping policies  
• Enable TCP Segmentation Offload support for a virtual machine  
• Enable Jumbo Frames support on appropriate components • Enable Jumbo Frames (1600+ MTU) support on appropriate components
• Determine appropriate VLAN configuration for a vSphere implementation • Determine appropriate VLAN configuration for a vSphere implementation
Section 3 – Plan and Configure vSphere Storage Section 3 – Plan and Configure vSphere Storage
Objective 3.1 – Configure Shared Storage for vSphere Objective 3.1 – Configure Shared Storage for vSphere
Knowledge Knowledge
• Identify storage adapters and devices  
• Identify storage naming conventions  
• Identify hardware/dependent hardware/software iSCSI initiator requirements  
• Compare and contrast array thin provisioning and virtual disk thin provisioning  
• Describe zoning and LUN masking practices  
• Scan/Rescan storage • Scan/Rescan storage
• Identify use cases for FCoE  
• Create an NFS share for use with vSphere  
• Connect to a NAS device • Connect to a NAS and/or SAN device
• Enable/Configure/Disable vCenter Server storage filters  
• Configure/Edit hardware/dependent hardware initiators  
• Enable/Disable software iSCSI initiator  
• Configure/Edit software iSCSI initiator settings  
• Configure iSCSI port binding  
• Enable/Configure/Disable iSCSI CHAP  
• Determine use case for hardware/dependent hardware/software iSCSI initiator  
• Determine use case for and configure array thin provisioning  
Objective 3.2 – Create and Configure VMFS and NFS Datastores Objective 3.2 – Create and Configure VMFS and NFS Datastores
Knowledge Knowledge
• Identify VMFS and NFS Datastore properties • Identify VMFS and NFS Datastore properties
• Identify VMFS5 capabilities • Identify VMFS5 capabilities
• Create/Rename/Delete/Unmount a VMFS Datastore  
• Mount/Unmount an NFS Datastore  
• Extend/Expand VMFS Datastores • Extend/Expand VMFS Datastores
• Upgrade a VMFS3 Datastore to VMFS5  
• Place a VMFS Datastore in Maintenance Mode • Place a VMFS Datastore in Maintenance Mode
• Select the Preferred Path for a VMFS Datastore  
• Disable a path to a VMFS Datastore  
• Determine use case for multiple VMFS/NFS Datastores • Determine use case for multiple VMFS/NFS Datastores
• Determine appropriate Path Selection Policy for a given VMFS Datastore  
Section 4 – Deploy and Administer Virtual Machines and vApps Section 4 – Deploy and Administer Virtual Machines and vApps
Objective 4.1 – Create and Deploy Virtual Machines Objective 4.1 – Create and Deploy Virtual Machines
Knowledge Knowledge
• Identify capabilities of virtual machine hardware versions • Identify capabilities of virtual machine hardware versions
• Identify VMware Tools device drivers  
• Identify methods to access and use a virtual machine console • Identify methods to access and use a virtual machine console
• Identify virtual machine storage resources  
• Place virtual machines in selected ESXi hosts/Clusters/Resource Pools  
• Configure and deploy a Guest OS into a new virtual machine • Configure and deploy a Guest OS into a new virtual machine
• Configure/Modify disk controller for virtual disks • Configure/Modify disk controller for virtual disks
• Configure appropriate virtual disk type for a virtual machine  
• Create/Convert thin/thick provisioned virtual disks • Create/Convert thin/thick provisioned virtual disks
• Configure disk shares  
• Install/Upgrade/Update VMware Tools • Install/Upgrade/Update VMware Tools
• Configure virtual machine time synchronization • Configure virtual machine time synchronization
• Convert a physical machine using VMware Converter  
• Import a supported virtual machine source using VMware Converter  
• Modify virtual hardware settings using VMware Converter  
• Configure/Modify virtual CPU and Memory resources according to OS and application requirements • Configure/Modify virtual CPU and Memory resources according to OS and application requirements
• Configure/Modify virtual NIC adapter and connect virtual machines to appropriate network resources  
• Determine appropriate datastore locations for virtual machines based on application workloads • Determine appropriate datastore locations for virtual machines based on application workloads
Objective 4.2 – Create and Deploy vApps Objective 4.2 – Create and Deploy vSphere vApps
Knowledge Knowledge
• Identify vApp settings • Describe a vSphere vApp
• Create/Clone/Export a vApp  
• Add objects to an existing vApp  
• Edit vApp settings  
• Configure IP pools  
• Suspend/Resume a vApp  
• Determine when a tiered application should be deployed as a vApp  
Objective 4.3 – Manage Virtual Machine Clones and Templates Objective 4.3 – Manage Virtual Machine Clones and Templates
Knowledge Knowledge
• Identify the vCenter Server managed ESXi hosts and Virtual Machine maximums  
• Identify Cloning and Template options  
• Clone an existing virtual machine  
• Create a template from an existing virtual machine  
• Deploy a virtual machine from a template  
• Update existing virtual machine templates  
• Deploy virtual appliances and/or vApps from an OVF template  
• Import and/or Export an OVF template • Import and/or Export an OVF template
• Determine the appropriate deployment methodology for a given virtual machine application  
Objective 4.4 – Administer Virtual Machines and vApps Objective 4.4 – Administer Virtual Machines and vApps
Knowledge Knowledge
• Identify files used by virtual machines  
• Identify locations for virtual machine configuration files and virtual disks • Identify locations for virtual machine configuration files and virtual disks
• Identify common practices for securing virtual machines  
• Hot Extend a virtual disk • Hot Extend a virtual disk
• Configure virtual machine options  
• Configure virtual machine power settings  
• Configure virtual machine boot options  
• Configure virtual machine troubleshooting options  
• Assign a Storage Policy to a virtual machine • Assign a Storage Policy to a virtual machine
• Verify Storage Policy compliance for virtual machines • Verify Storage Policy compliance for virtual machines
• Determine when an advanced virtual machine parameter is required  
• Adjust virtual machine resources (shares, limits and reservations) based on virtual machine workloads  
Section 5 – Establish and Maintain Service Levels Section 5 – Establish and Maintain Service Levels
Objective 5.x – Create and Configure VMware Clusters Objective 5.1 – Create and Configure VMware Clusters
Knowledge Knowledge
• Describe DRS virtual machine entitlement • Describe DRS and Storage DRS
• Create/Delete a DRS/HA Cluster • Create/Delete a DRS/HA Cluster
• Add/Remove ESXi Hosts from a DRS/HA Cluster  
• Add/Remove virtual machines from a DRS/HA Cluster • Add/Remove ESXi Hosts from a DRS/HA Cluster
• Configure Storage DRS • Describe Enhanced vMotion Compatibility
• Configure Enhanced vMotion Compatibility  
• Monitor a DRS/HA Cluster • Monitor a DRS/HA Cluster
• Configure migration thresholds for DRS and virtual machines  
• Configure automation levels for DRS and virtual machines  
• Create VM-Host and VM-VM affinity rules  
• Enable/Disable Host Monitoring • Enable/Disable Host Monitoring
• Enable/Configure/Disable virtual machine and application monitoring • Enable/Configure/Disable virtual machine and application monitoring
• Configure admission control for HA and virtual machines • Configure admission control for HA and virtual machines
• Determine appropriate failover methodology and required resources for an HA implementation • Determine appropriate failover methodology and required resources for an HA implementation
Objective 5.2 – Plan and Implement VMware Fault Tolerance
Knowledge
• Identify VMware Fault Tolerance requirements
• Configure VMware Fault Tolerance networking
• Enable/Disable VMware Fault Tolerance on a virtual machine
• Test an FT configuration
• Determine use case for enabling VMware Fault Tolerance on a virtual machine
Objective 5.3 – Create and Administer Resource Pools
Knowledge
• Describe the Resource Pool hierarchy
• Define the Expandable Reservation parameter
• Create/Remove a Resource Pool
• Configure Resource Pool attributes
• Add/Remove virtual machines from a Resource Pool
• Determine Resource Pool requirements for a given vSphere implementation
• Evaluate appropriate shares, reservations and limits for a Resource Pool based on virtual machine workloads
• Clone a vApp
Objective 5.4 – Migrate Virtual Machines Objective 5.2 – Migrate Virtual Machines
Knowledge Knowledge
• Identify ESXi host and virtual machine requirements for vMotion and Storage vMotion • Identify ESXi host and virtual machine requirements for vMotion and Storage vMotion
• Identify Enhanced vMotion Compatibility CPU requirements • Identify Enhanced vMotion Compatibility CPU requirements
• Identify snapshot requirements for vMotion/Storage vMotion migration
• Migrate virtual machines using vMotion/Storage vMotion • Migrate virtual machines using vMotion/Storage vMotion
• Configure virtual machine swap file location  
• Migrate a powered-off or suspended virtual machine  
• Utilize Storage vMotion techniques (changing virtual disk type, renaming virtual machines, etc.)  
Objective 5.5 – Patch and Update ESXi and Virtual Machines
Knowledge
• Identify patching requirements for ESXi hosts and virtual machine hardware/tools
• Create/Edit/Remove a Host Profile from an ESXi host
• Attach/Apply a Host Profile to an ESXi host or cluster
• Perform compliance scanning and remediation of an ESXi host using Host Profiles
• Install and Configure vCenter Update Manager
• Configure patch download options
• Create/Edit/Delete an Update Manager baseline
• Attach an Update Manager baseline to an ESXi host or cluster
• Scan and remediate ESXi hosts and virtual machine hardware/tools using Update Manager
• Stage ESXi host updates
Section 6 – Perform Basic Troubleshooting Section 6 – Perform Basic Troubleshooting and Alarm Management
Objective 6.1 – Perform Basic Troubleshooting for ESXi Hosts Objective 6.1 – Perform Basic Troubleshooting for ESXi Hosts
Knowledge Knowledge
• Identify general ESXi host troubleshooting guidelines • Identify general ESXi host troubleshooting guidelines
• Troubleshoot common installation issues • Troubleshoot common installation issues
• Monitor ESXi system health • Monitor ESXi system health
• Export diagnostic information • Export diagnostic information
Objective 6.2 – Perform Basic vSphere Network Troubleshooting Objective 6.2 – Perform Basic vSphere Network Troubleshooting
Knowledge Knowledge
• Verify network configuration • Verify network configuration
• Verify a given virtual machine is configured with the correct network resources • Verify a given virtual machine is configured with the correct network resources
• Troubleshoot virtual switch and port group configuration issues • Troubleshoot virtual switch and port group configuration issues
• Troubleshoot physical network adapter configuration issues • Troubleshoot physical network adapter configuration issues
• Identify the root cause of a network issue based on troubleshooting information • Identify the root cause of a network issue based on troubleshooting information
Objective 6.3 – Perform Basic vSphere Storage Troubleshooting
Knowledge
• Verify storage configuration
• Troubleshoot storage contention issues
• Troubleshoot storage over-commitment issues
• Troubleshoot iSCSI software initiator configuration issues
• Troubleshoot Storage Reports and Storage Maps
• Identify the root cause of a storage issue based on troubleshooting information
Objective 6.4 – Perform Basic Troubleshooting for HA/DRS Clusters and vMotion/Storage vMotion
Knowledge
• Identify HA/DRS and vMotion requirements
• Verify vMotion/Storage vMotion configuration
• Verify HA network configuration
• Verify HA/DRS cluster configuration
• Troubleshoot HA capacity issues
• Troubleshoot HA redundancy issues
• Interpret the DRS Resource Distribution Graph and Target/Current Host Load Deviation
• Troubleshoot DRS load imbalance issues
• Troubleshoot vMotion/Storage vMotion migration issues
• Interpret vMotion Resource Maps
• Identify the root cause of a DRS/HA cluster or migration issue based on troubleshooting information
Section 7 – Monitor a vSphere Implementation and Manage vCenter Server Alarms Section 7 – Monitor a vSphere Implementation and Manage vCenter Server Alarms
Objective 7.1 – Monitor ESXi, vCenter Server and Virtual Machines Objective 7.1 – Monitor ESXi, vCenter Server and Virtual Machines
Knowledge Knowledge
• Describe how Tasks and Events are viewed in vCenter Server • Describe how Tasks and Events are viewed in vCenter Server
• Identify critical performance metrics • Identify critical performance metrics
• Explain common memory metrics • Explain common memory metrics
• Explain common CPU metrics • Explain common CPU metrics
• Explain common network metrics • Explain common network metrics
• Explain common storage metrics • Explain common storage metrics
• Compare and contrast Overview and Advanced Charts • Compare and contrast Overview and Advanced Charts
• Configure SNMP for vCenter Server • Configure SNMP for vCenter Server
• Configure Active Directory and SMTP settings for vCenter Server • Configure Active Directory and SMTP settings for vCenter Server
• Configure vCenter Server logging options • Configure vCenter Server logging options
• Create a log bundle • Create a log bundle
• Create/Edit/Delete a Scheduled Task • Create/Edit/Delete a Scheduled Task
• Configure/View/Print/Export resource maps • Configure/View/Print/Export resource maps
• Start/Stop/Verify vCenter Server service status • Start/Stop/Verify vCenter Server service status
• Start/Stop/Verify ESXi host agent status • Start/Stop/Verify ESXi host agent status
• Configure vCenter Server timeout settings • Configure vCenter Server timeout settings
• Monitor/Administer vCenter Server connections • Monitor/Administer vCenter Server connections
• Create an Advanced Chart • Create an Advanced Chart
• Determine host performance using resxtop and guest Perfmon • Determine host performance using resxtop and guest Perfmon
• Given performance data, identify the affected vSphere resource • Given performance data, identify the affected vSphere resource
Objective 7.2 – Create and Administer vCenter Server Alarms Objective 7.2 – Create and Administer vCenter Server Alarms
Knowledge Knowledge
• List vCenter default utilization alarms • List vCenter default utilization alarms
• List vCenter default connectivity alarms • List vCenter default connectivity alarms
• List possible actions for utilization and connectivity alarms • List possible actions for utilization and connectivity alarms
• Create a vCenter utilization alarm • Create a vCenter utilization alarm
• Create a vCenter connectivity alarm • Create a vCenter connectivity alarm
• Configure alarm triggers • Configure alarm triggers
• Configure alarm actions • Configure alarm actions
• For a given alarm, identify the affected resource in a vSphere implementation • For a given alarm, identify the affected resource in a vSphere implementation

If you managed to go through the whole list, you can see there are whole section missing in the VCP-Cloud, compared to VCP-DV. It seems you don’t need to know as much about hardware, upgrading, security, design, storage, VM’s, vSphere templates, FT, Resource pools, patching, troubleshooting storage&HA&DRS&vMotion.

For my part it seems as the VCP-Cloud exam is for a VMware admin that is yet to take the VCP-DV but has worked with vSphere environments and has some hands-on experience.

But if you already have the VCP-DV prerequisetes, I highly recommend going for the VCP-DV but, and there’s always a but, if you have the VCP-Cloud prerequisites and the experience you should go for the VCP-Cloud exam.

It’s the famous “It depends” conundrum, which seems to be the answer for most IT questions regarding designs. And a matter of fact I think it’s a great book title for a vSphere design book: “It depends – VMware Designs for the masses”. :)

To sum it all up:

VCP-IaaS + VCP-DV [VCP exam + course prerequisite] = VCP-Cloud certified.

VCP-Cloud [VCP-IaaS + mini VCP-DV] + course prerequisite = VCP-Cloud certified.

Please feel free to comment!

 

VCP-IaaS exam experience

On Tuesday I sat the VCP-IaaS exam and passed.

As you may have seen I’ve been going through the sections of the VCP-IaaS blueprint, creating some notes on procedures and hopefully a helpful summary of the blueprint.

I must say that going through the sections and making the notes really helped, but what really helped is my own experience with the product. I recommend creating a vCloud environment, with vCloud cells, vShield Manager, vCenter, Chargeback and Connector. Just having access to an environment to play with will make this test really manageable.

As far the exam goes, without going into much detail (not that I can),  I found myself struggling with any questions regarding Chargeback, mainly because its easy to install and not a system a VMware admin will have anything to do with after creating a vCloud environment. I recommend using the study notes and go through section 3 with Chargeback Manager open and just click away.

Also vCloud networking is a subject you will have to have figured out as this subject is something that is very important in any vCloud environment. Thankfully many bloggers have posted really helpful posts on this subject.  The vCloud Ultimate Resource Guide is a great list of resources that will help you pass the exam.

Other recommended reads are the vCloud Admin and User Guide (Most of the sections use these two guides). I recommend going through them at least once in case my notes missed anything.

I hope the Study Notes will help anyone studying for this exam and I will update the posts (or just create a new one)  when the Blueprint is upgraded to version 5.1 of vCloud which was released at VMworld USA.

VCP-IaaS Study Notes: Section 8.1

This is Section 8.1 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

Identify vCloud Director interface components used for monitoring

  • Manage and Monitor tab is used for logging Networks and vSphere Resources.
  • Also all logs and tasks for the vCloud infrastructure is in the Manage and Monitor tab.
  • To see logs for individual organization open My Cloud in the organization and select Logs.

Identify the location of logs in vCloud Director

  • vCloud Director provides logging information for each cloud cell in the system. You can view the logs to monitor your cells and to troubleshoot issues.
    • You can find the logs for a cell at /opt/vmware/cloud-director/logs.

  • View Tasks and Events as an System Administrator
    • Procedure
      • Log in to the vCloud Director system as a system administrator.
      • Click the Manage & Monitor tab and click Logs in the left pane.
      • Click the Tasks tab.
        • vCloud Director displays information about each system-level task.
      • Double-click a task for more information.
  • View Organization Events
    • You can view the log for an organization to monitor organization-level events. Failed events and view events are listed by user.
    • You are an organization administrator.
    • Procedure
      • Click the My Cloud.
      • In the left pane, click Logs.
      • Click the Events tab.
        • vCloud Director displays information about each organization-level event.
      • Double-click an event for more information.
      • Only system administrators can view the details about most events.

Monitor CPU, Disk and Memory usage for a Provider vDC

  • Provider vDCs supply compute, memory, and storage resources to organization vDCs. You can monitor provider vDC resources and add more resources if necessary.
  • Procedure
    • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
    • Click the Monitor tab.
    • vCloud Director displays information about CPU, memory, and storage for each provider vDC.

Monitor CPU, Disk and Memory usage for an Organization

  • Organization vDCs supply compute, memory, and storage resources to organizations. You can monitor organization vDC resources and add more resources if necessary.
  • Procedure
    • Click the Manage & Monitor tab and click Organization vDCs in the left pane.
    • Click the Monitor tab.
    • vCloud Director displays information about CPU, memory, and storage for each organization vDC.

Monitor External Network, Organization Networks, and Network Pools

  • External Networks
    • Procedure
      • Click the Manage & Monitor tab and click External Networks
      • There you can see the status, VLAN, Default Gateway, IP allocation, corresponing vSphere Network and to which vCenter it is mapped.
  • Organization Networks
    • Procedure
      • Click the Manage & Monitor tab and click Organization Networks
      • There you can see the status, Default Gateway, Type, Connected to which External Network, What network pool is being used and what Organization owns it.
  • Network Pools
    • Procedure
      • Click the Manage & Monitor tab and click External Network Pools.
      • There you can see status, Type of Network pool, % of IP’s used, to which vDS its connected to and to which vCenter.

Monitor IP allocation utilization

  • External Networks
    • Procedure
      • Click the Manage & Monitor tab and click External Networks
      • Right click the network and select IP-allocation.
  • Organization Networks
    • You can view a list of IP addresses that are currently in use in an organization network IP pool.
    • Procedure
      • Click the Manage & Monitor tab and click Organization Networks in the left pane.
      • Right-click the organization network name and select IP Allocations.
  • Display the IP Allocations for Your vApp Network
    • You can review the IP allocations for the networks in your vApp.
    • Procedure
      • Click My Cloud.
      • In the left pane, selectvApps.
      • Select a vApp, right-click, and select Open.
      • On the Networking tab, select the Show networking detailscheck box.
      • Select a network, right-click, and select IP Allocations.
      • Review your allocations and click OK.

Review and interpret tasks and events in a vCloud

  • See bullet: Identify the location of logs in vCloud Director
  • View the system log to monitor system-level tasks that are in progress, to find and troubleshoot failed tasks, and to view tasks by owner.
  • The log can also include debug information, depending on your vCloud Director settings.
    • You can display debug info in the vCloud Director task log in the settings.
      • Procedure:
        • Click Administration
        • Select General for System Settings.
        • Click Display debug information
        • NOTE: Only System Administrator can view the debug information.

Troubleshoot common resource/event issues in a vCloud

  • First enable debug information in the System Settings
  • Your best chance is to Google the task detail if the error isn’t descriptive enough. Not kidding.

VCP-IaaS Study Notes: Section 7.2

This is Section 7.2 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

Identify frequently used Catalog properties

  • Share
  • Change Owner
    • You can change the owner of a catalog. Before you can delete a user who owns a catalog, you must change the owner or delete the catalog.
    • You are an organization administrator.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the Catalogs tab, right-click a catalog and select Change Owner.
      • Select a user from the list or search for one.
        • You can search for a user by full name or their user name.
      • Click OK.
  • Name

Explain how guest customization works in a vCloud implementation

  • When you customize your guest OS you can set up a virtual machine with the operating system that you want.
  • vCloud Director can customize the network settings of the guest operating system of a virtual machine created from a vApp template. When you customize your guest operating system, you can create and deploy multiple unique virtual machines based on the same vApp template without machine name or network conflicts.
  • I recommend reading the chapter about Guest Operating System Customization, begins at page 105 in the vCloud Director User’s Guide.

Deploy a vApp from a Catalog

  • You can add a vApp template as a vApp from your catalog to My Cloud.
  • You are at least a vApp author.
  • If the vApp template is based on an OVF file that includes OVF properties for customizing its virtual machines, those properties are passed to the vApp. If any of those properties are user-configurable, you can specify the values.
  • Prerequisites
    • A vApp template is available in a published or a locally shared catalog.
  • Procedure
    • Click Catalogs.
    • In the left pane, click on a catalog option.
      • My Organization’s Catalogs
    • Public Catalogs
      • You can access vApp templates in your organization’s shared catalogs or, if you are an organization administrator, from a public catalog.
    • On the vApp Templates tab, select a vApp template, right-click, and select Add to My Cloud.
    • Type a name and optional description for the vApp.
    • Select a runtime and storage lease and click Next.
    • Select a virtual datacenter, configure the virtual machines in the vApp, and click Next.
    • Configure the custom properties, if any, and click Next.
    • Configure the networking options for the vApp and click Next.
    • Review the vApp summary information and click Finish.
  • vCloud Director creates a vApp on the My Cloud > vApps page.

Configure a Catalog to be shared by users in an Organization

  • Share a catalog to make its contents available to users in your organization. Users with the proper rights and access level can use vApp templates and media from the shared catalog to create their own vApps.
  • You are at least a catalog author.
  • Procedure
    • Click Catalogs > My Organization’s Catalogs.
    • Select a catalog, right-click, and select Share.
    • Click Add Members.
    • Select the users and groups with whom you want to share the catalog.

    • Select an access level and click OK

    • The actual actions a user can perform on a catalog and its contents depends on the intersection of the rights of the user and their access level to the catalog. Sharing a catalog with full control does not grant a user rights that the user does not already have.
    • Click OK.

Copy vApp templates and media to/from a Catalog

  • Copy a vApp Template from a Public Catalog to an Organization Catalog
    • You can copy a vApp template from a public catalog to your organization catalog to make it available to users in your organization.
    • You are a vApp author or organization administrator.
    • Prerequisites
      • You have a catalog and vDC.
    • Procedure
      • Click Catalogs.
      • In the left pane, click Public Catalogs.
      • On the vApp Templates tab, select a vApp template, right-click, and select Copy To Catalog.
      • Type a name and optional description for the vApp.
      • Select a destination catalog and vDC.
        • Select a shared catalog to give organization users access to the template.
      • Click OK.
    • vCloud Director copies the vApp template to the organization catalog. The vApp appears on the vApp Templates tab in My Organization’s Catalogs.
  • Copy a vApp Template Between an Organization’s Catalogs
    • You can copy a vApp template from one catalog in your organization to another catalog in the same organization. This is useful if the catalogs are shared with different users and you want both groups of users to have access to the vApp template.
    • You are an organization administrator, catalog author, or vApp author.
    • Prerequisites
      • You must have access to at least two catalogs and a vDC with available space.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the vApp Templates tab, right-click a vApp template and select Copy to Catalog.
      • Type a name and optional description for the vApp template.
      • Select the destination catalog and vDC.
        • If you select a published catalog, the vApp template will be available to all organizations in the vCloud Director installation.
      • Click OK.
  • Download a vApp Template
    • You can download a vApp template from a catalog locally as an OVF file.
      • You are at least a catalog author.
    • Prerequisites
      • The computer from which you are downloading must have Java Plug-in 1.6.0_10 or later installed.
    • Procedure
      • Click Catalogs.
      • In the left pane, click on a catalog option.
        • My Organization’s Catalogs
        • Public Catalogs
        • You can download vApp templates from your organization’s catalogs or, if you are an organization administrator, from a public catalog.
      • On the vApp Templates tab, select a vApp template, right-click, and select Download.
        • Navigate to the local folder where you want to save the OVF file and click Save.
      • You can click the Launch Uploads and Downloads Progress Window button from My Organization’s Catalogs to track the progress.
  • Upload Media Files
    • You can upload media files to a catalog. Users with access to the catalog can use the media files to install applications on their virtual machines.
    • You are at least a catalog author.
    • Prerequisites
      • The computer from which you are uploading must have Java Plug-in 1.6.0_10 or later installed.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the Media tab, click the Upload button.
      • Type the path to the media file path or click Browse, locate the file, and click Upload.
      • Type a name and optional description for the media file.
        • This is the name that appears in vCloud Director.
      • Select the destination vDC and catalog.
      • Click Upload.
        • The media file is uploaded to the specified location. You can click the Launch Uploads and Downloads Progress Window button to track the progress.
  • Copy Media Files to a Catalog
    • You can copy media files to another catalog.
    • You are at least a catalog author.
    • Prerequisites
      • You have access to multiple vDCs.
    • Procedure
      • Click Catalogs.
      • On the Media tab, select a media file, right-click, and select Copy To Catalog.
      • Type a name and description.
      • Select the destination catalog and vDC.
      • Click OK.
    • The media file is copied to and stored in the selected catalog.

Configure Catalog properties

  • You can review and modify your catalog properties.
  • You are at least a catalog author.
  • Procedure
    • Click Catalogs.
    • In the left pane, click My Organization’s Catalogs.
    • Select a catalog, right-click, and select Properties.
    • Review the properties in the General, Sharing, and Publishing tabs.
    • Modify the relevant properties and click OK.

Given requirements, apply the appropriate properties to a Catalog

  • You can publish, share and change its name.

VCP-IaaS Study Notes: Section 7.1

This is Section 7.1 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

Describe the function of vApp templates, media, and catalogs

  • 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.
  • There are two ways to add vApp templates to a catalog. You can upload an OVF package directly to a catalog or save a vApp as a vApp template.
  • You can upload media files directly to a catalog.

Identify the location of vApp templates, media and catalogs

  • Depending on your role in the organization, you can access catalogs in your organization and public catalogs that were published by other organizations.
    • To access a public catalog, you must be an organization administrator .
    • To access a catalog in your organization, you must be at least a vApp author.
  • Procedure
    • Click Catalogs.
    • In the left pane, click on a catalog option.
      • My Organization’s Catalogs
      • Public Catalogs
        • In the right pane, select a catalog, right-click, and select Open.

Identify the format in which vApp templates, media, and catalogs can be stored

  • vApp Templates:
    • You can upload an OVF package as a vApp template to make the template available to other users. vClou Director supports OVF 1.0 and OVF 1.1.
    • vCloud Director supports OVFs based on the Open Virtualization Format (OVF) Specification. If you upload an OVF that includes deployment options, those options are preserved in the vApp template.
    • You can quarantine files that users upload to vCloud Director so that you can process the files before you accept them
  • Media:
    • You can upload an ISO or FLP file to make the media available to other users..

Differentiate between vApp templates, media and catalogs

  • A catalog consists of a list of catalogs, vApp templates, and media files in your organization.
  • When you click the Catalogs button in the menu bar, these tabs appear.
    • Catalogs
    • vApp Templates
    • Media
  • A vApp template is a virtual machine image that is loaded with an operating system, applications, and data.
  • You can upload media files to a catalog. Users with access to the catalog can use the media files to install applications on their virtual machines.

Create/Update a vApp template

  • Create:
    • You can upload an OVF package from remote shares and your local directory to vCloud Director as a vApp template.
    • You are at least a catalog creator.
    • vCloud Director supports OVFs based on the Open Virtualization Format (OVF) Specification. If you upload an OVF file that includes OVF properties for customizing its virtual machines, those properties are preserved in the vApp template.
    • Prerequisites
      • The computer from which you are uploading must have Java Plug-in 1.6.0_10 or later installed.
      • vCloud Director does not support uploading compressed OVF files.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the vApp Templates tab, click the Upload button.
      • Type the name and path of the OVF file to upload, or click Browse, select the OVF file, and click Upload.
      • Type a name and optional description for the vApp template.
      • Select a destination vDC and catalog.
      • Click Upload.
    • You can click the Launch Uploads and Downloads Progress Window button to track the progress.
  • Update:
    • You can modify some basic properties of a vApp template. To make more advanced changes to a vApp template, add it to My Cloud, make the changes, then add it back to the catalog as a new vApp template.
    • You are an organization administrator.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the vApp Templates tab, right-click a vApp template and select Properties.
      • On the General tab, modify the vApp template name and description.
      • Select a vApp creation option.
        • This option applies when creating a vApp based on this template. It is ignored when building a vApp using individual virtual machines from this template.

        • Choose whether or not to mark the vApp template as a Gold Master in the catalog.
        • If you mark a vApp template as a Gold Master, this information appears in the list of vApp templates.
      • To reset the vApp template storage lease, select the Reset lease check box and select a new storage lease.
      • Click OK.

Create/Delete a Catalog

  • Create:
    • You can create catalogs to group your vApp templates and media files.
    • You are at least a catalog author.
    • Procedure
      • Click Catalogs > My Organization’s Catalogs.
      • On the Catalogs tab, click the Add Catalog button.
      • Type a catalog name and optional description and click Next.
      • (Optional) To share the catalog with members of the organization, click Add Members, select users and groups, select an access level, click OK, and click Next.
      • Select a catalog publishing option and click Next..

      • Review the summary and click Finish.
  • Delete:
    • You can delete a catalog from your organization.
    • You are at least a catalog author.
    • Prerequisites
      • The catalog must not contain any vApp templates or media files. You can move these items to a different catalog or delete them.
    • Procedure
      • Click Catalogs.
      • In the left pane, click My Organization’s Catalogs.
      • Select a catalog, right-click, and select Delete.
      • Click Yes.

Publish a catalog to different Organizations

  • You can publish a catalog to make its vApp templates and media files available to all organizations in the installation.
  • Prerequisites
    • Verify that the organization that contains the catalog allows catalog publishing.
  • Procedure
    • Click the Manage & Monitor tab and click Organizations in the left pane.
    • Right-click the organization name and select Open.
    • Click Catalogs and select My Organization’s Catalogs in the left pane.
    • On the Catalogs tab, right-click the catalog name and select Publish.
    • On the Publishing tab, select Publish to all organizations and click OK.
  • The catalog and all of its contents appear under Public Catalogs for all organizations in the vCloud Director installation.

VCP-IaaS Study Notes: Section 6.1

This is Section 6.1 in the VCP-IaaS blueprint Guide 1.2. The rest of the (completed) sections can be found here.

Identify where in the hierarchy a provider VDC resides

  • It right after the vSphere resources (vCenter,ESXi, Datastores and Networks)

Identify where an Provider VDC gets its resources

  • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
  • Click on the Provider vDC.
  • See the list of Organization vDC, Hosts, Datastores, External Networks and Resource pools.

Differentiate Provider and Organization VDCs

  • A provider virtual datacenter (vDC) combines the compute and memory resources of a single vCenter Server resource pool with the storage resources of one or more datastores connected to that resource pool.
  • A provider vDC is the source for organization vDCs.

Explain the concept of a Provider VDC

  • A provider virtual datacenter (vDC) combines the compute and memory resources of a single vCenter Server resource pool with the storage resources of one or more datastores connected to that resource pool.

Explain when and how to Enable/Disable a Provider VDC

  • You can disable a provider vDC to prevent the creation of organization vDCs that use the provider vDC resources.
  • When you disable a provider vDC, vCloud Director also disables the organization vDCs that use its resources. Running vApps and powered on virtual machines continue to run, but you cannot create or start additional vApps or virtual machines.
  • Procedure
    • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
    • Right-click the provider vDC name and select Enable or Disable.

Create/Delete a Provider VDC

  • Create:
    • You can create a provider vDC to register vSphere compute, memory, and storage resources for vCloud Director to use. You can create multiple provider vDCs for users in different geographic locations or business units, or for users with different performance requirements.
    • A provider vDC can only include a single resource pool from a single vCenter Server.
    • If you plan to add a resource pool that is part of a cluster that uses vSphere HA, make sure you are familiar with how vSphere HA calculates slot size. For more information about slot sizes and customizing vSphere HA behavior, see the VMware vSphere Availability Guide.
    • Prerequisites
      • Verify that at least one vCenter Server is attached with an available resource pool to vCloud Director. The resource pool must be in a vCenter cluster that is configured to use automated DRS. The vCenter Server must have the vShield for VMware vCloud Director license key.
    • Procedure
      • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
      • Click New Provider vDC.
      • Type a name and optional description.
        • You can use the name and description fields to indicate the vSphere functions available to the provider vDC, for example, vSphere HA.
      • Select the latest supported hardware version and click Next.
        • This selection determines the latest supported hardware version for virtual machines in organization vDCs based on this provider vDC. Hardware Version 8 requires ESX/ESXi 5.0 hosts. If this provider vDC will use a resource pool that contains ESX/Esxi 5.0 and ESX/ESXi 4.x hosts, select Hardware Version 7.
      • Select a vCenter Server and resource pool and click Next.
        • If the vCenter Server has no available resource pools, no resource pools appear in the list.
      • Select one or more datastores, click Add, and click Next.
        • vCloud Director does not support the use of read-only datastores with provider vDCs. In most cases, readonly datastores do not appear in the list, but some read-only NFS datastores might appear. Do not add these datastores to your provider vDC. Use only shared storage because vSphere DRS cannot migrate virtual machines on local storage.
      • Type the root user name and password for the ESX/ESXi hosts and click Next.
      • Click Finish to create the provider vDC.
  • Delete:
    • You can delete a provider vDC to remove its compute, memory, and storage resources from vCloud Director.
    • The resources remain unaffected in vSphere.
    • Prerequisites
      • Disable the provider vDC.
      • Disable and delete all organization vDCs and organization networks that use the provider vDC.
      • Procedure
        • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
        • Right-click the provider vDC name and select Delete.
        • Click Yes.

Select Resource Pools and Datastores for a Provider VDC

  • Add Storage Capacity to a Provider vDC
    • You can add storage capacity to a provider vDC by adding one or more datastores.
    • Procedure
      • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
      • Right-click the provider vDC name and select Open.
        • Click the Datastores tab.
      • Click Add/Remove.
      • Select a datastore from the list, click Add, and click OK.
        • vCloud Director does not support the use of read-only datastores with provider vDCs. In most cases, readonly datastores do not appear in the list, but some read-only NFS datastores might appear. Do not add these datastores to your provider vDC.
        • Use only shared storage because vSphere DRS cannot migrate virtual machines on local storage.
  • Add a Resource Pool to a Provider vDC
    • You can add additional resource pools to a provider vDC so that pay-as-you-go organization vDCs that the provider vDC provides can expand.
    • When compute resources are backed by multiple resource pools, they can expand as needed to accommodate more virtual machines.
    • Prerequisites
      • Verify that There is one or more available resource pool exists in the same vCenter datacenter as the provider vDC’s primary resource pool.
    • Procedure
      • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
      • Right-click the provider vDC name and select Open.
      • Click the Resource Pools tab.
      • Click Add Resource Pool.
      • Select the resource pool to add and click Finish.
    • vCloud Director adds a resource pool for the provider vDC to use, making all pay-as-you-go organization vDCs backed by the provider vDC elastic.

Explain when and how to Enable/Disable a Provider VDC Host

  • You can disable a host to prevent vApps from starting up on the host. Virtual machines that are already running on the host are not affected.
  • To perform maintenance on a host, migrate all vApps off of the host or stop all vApps and then disable the host.
  • Procedure
    • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
    • Right-click the provider vDC name and select Open.
    • Click the Hosts tab.
    • Right-click the host name and select Enable Host or Disable Host.
    • vCloud Director enables or disables the host for all provider vDCs that use its resources.

Prepare/Unprepare a Provider VDC Host

  • When you add an ESX/ESXi host to a vSphere cluster that vCloud Director uses, you must prepare the host before a provider vDC can use its resources. You can unprepare a host to remove it from the vCloud Director environment.
  • You cannot prepare a host that is in lockdown mode. After you prepare a host, you can enable lockdown mode.
  • Prerequisites
    • Before you can unprepare a host, you must disable it and ensure that no virtual machines are running on the host.
  • Procedure
    • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
    • Right-click the provider vDC name and select Open.
    • Click the Hosts tab.
    • Right-click the host name and select Prepare Host or Unprepare Host.
    • vCloud Director prepares or unprepares the host for all provider vDCs that use its resources.

Upgrade/Repair a Provider VDC Host agent

  • Upgrade:
    • vCloud Director installs agent software on each ESX/ESXi host in the installation. If you upgrade your ESX/ESXi hosts, you also need to upgrade your ESX/ESXi host agents.
    • Procedure
      • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
      • Right-click the provider vDC name and select Open.
      • Click the Hosts tab.
      • Right-click the host name and select Upgrade Host.
      • vCloud Director upgrades the host agent. This upgrade affects all provider vDCs that use the host.
  • Repair
    • If the vCloud Director agent on an ESX/ESXi host cannot be contacted, try to repair the host.
    • Procedure
      • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
      • Right-click the provider vDC name and select Open.
      • Click the Hosts tab.
      • Right-click the host name and select Repair Host.
      • vCloud Director repairs the host. This operation affects all provider vDCs that use the host.

Explain when and how to Enable/Disable a Provider Datastore

  • You can enable or disable a datastore that has been added to a provider vDC. You must disable a datastore before you can remove it from vCloud Director.
  • When you disable a datastore, you cannot start vApps that are associated with the datastore or create vApps on the datastore.
  • Procedure
    • Click the Manage & Monitor tab and click Datastores in the left pane.
    • Right-click the datastore name and select Enable or Disable.
      • vCloud Director enables or disables the datastore for all provider vDCs that use its resources.+

Configure Low Disk Space Warnings

  • You can configure low disk space warnings on a datastore to receive an email from vCloud Director when the datastore reaches a specific threshold of available capacity. These warnings alert you to a low disk situation before it becomes a problem.
  • Procedure
    • Click the Manage & Monitor tab and click Provider vDCs in the left pane.
    • Right-click the provider vDC name and select Open.
    • Click the Datastores tab.
    • Right-click the datastore name and select Properties.
    • Select the disk space thresholds for the datastore.
      • You can set two thresholds, yellow and red. When vCloud Director sends an email alert, the message indicates which threshold was crossed.
    • Click OK.
Follow

Get every new post delivered to your Inbox.

Join 346 other followers