vCloud Director

- January 03, 2016
  1. Components of vCloud Director :
  3. Key Terms you should know :
    • Cell – The individual vCloud Director Servers that make up a logical vCloud Director instance or cluster
    • vCNS – vCloud Network and Security (formerly vShield)
    • vCD – vCloud Director
    • vDC – Virtual Data Center
    • PvDC – Provider Virtual Data Center
    • OvDC – Organization Virtual Data Center
  4. Planning and Design:
    • Object Identities
      • –2 IP Addresses
        • •One for the HTTP service
        • •One for the console proxy service
      • –DNS A records
      • –VM Logical names
    • Requirements
      • –vCloud Director 5.1.1 installation bin file
      • –Red Hat Enterprise Linux (RHEL) 5 or 6
        • –libXdmcp rpm package
      • •http://ITtra.in/libXdmcp
      • –Compatible SQL or Oracle Database
        • •http://ITtra.in/SQLOracleDB
  5. SQL Database Installation
      • Installation Guide Scripts
        • –Create the database instance
        • –Set transaction isolation level
        • –Create database user account
        • –Assign permissions to the database user account
        • –Use SQL “Mixed Mode” authentication
  6. Create SSL Certificates
    • Keytool Command
    • Create Two SSL Certificates
      • –keytool -keystore certificates.ks -storetype JCEKS -storepass passwd -validity 9999 -genkey -keyalg RSA -alias http
      • –keytool -keystore certificates.ks -storetype JCEKS -storepass passwd -validity 9999 -genkey -keyalg RSA -alias consoleproxy
      • –Use chmod to grant read access universally
  7. vCloud Organizations :
    • The Logical Consumer Object of vCloud
      • –Unique Organization URL
      • –Catalogs for vApps
      • –Email Configuration
      • –Policies: vApp Leases, Templates, Quotas, Limits, and Passwords
    • LDAP Integration
      • –“None” for Local Users
      • –vCD System LDAP for Internal Users
      • –Custom LDAP for 3rd Party Directory Services
    • Organization Roles
      • –Org Admin
      • –Catalog Author
      • –vApp Author
      • –vApp User
      • –Console Access
  8. Create an Organization
    • Create Two Organizations
      • –One for Public Catalogs for Global Access
      • –One for the Development Team
    • Reasons for Choosing Development
      • –Start with the easy workloads first
      • –Learning process for everyone
      • –Adhere to the true development cycle:
        • Development > Test > Quality Control > Stage > Production
  9. Organizational vDCs
    • Virtual Data Centers
      • –Live on top of the Provider vDC (PvDC)
      • –Further logical definition of existing compute and storage resource pools
      • –Multiple OvDCs can live on top of the same PvDC
    • Allocation Models
      • –Defines the quality of service and cost of vCloud resources
      • Allocation Pool
        • Based on Percentages of Guarantee
          • –CPU Allocation in GHz
          • –CPU Resources Guaranteed %
          • –vCPU Speed in GHz
          • –Memory Allocation in GB
          • –Memory Resources Guaranteed %
          • –Maximum number of VMs: Set Value or Unlimited
        • •Uses a vSphere Resource Pool to Enforce
          • –Dynamic allocation of reservations
          • –CPU Resources Guaranteed * vCPUs allocated * vCPU Speed = Resource Pool Reservation
          • •Example: 50% * 2 GHz * 100 vCPUs = 100 GHz Reserved
          • –When Reservation reaches Allocation, limit is imposed
      • Pay as You Go
          • Granular Resources Based on vApps
            • –Resources committed only when a vApp is deployed
            • –CPU Quota: GHz value or Unlimited
            • –CPU Resources Guaranteed %
            • –vCPU Speed in GHz
            • –Memory Quote: GB value or Unlimited
            • –Memory Resources Guaranteed %
            • –Maximum number of VMs: Set Value or Unlimited
          • Notable Information
            • –vCloud Director 5.1 introduced ability to do CPU and Memory quota
            • –Common business jargon = “Pay by the drink”
        • Reservation Pool
          • •Full Reservation of Resources
            • –Simplest model to deploy
            • –CPU Allocation in GHz
            • –Memory Allocation in GB
            • –Maximum number of VMs: Set Value or Unlimited
            • Costly Method
              • –Resources are reserved regardless of use
              • –Cannot go back and overcommit your PvDC
    • Storage Profiles
      • Allocated Storage
        • –Use Storage Profiles to identify back end storage layouts
        • –Storage Profiles are created in the vCenter that owns the vCloud Resource Cluster(s)
    • Networking
      • Network Pool
        • –Choice ultimately determines the amount of available networks
        • –Drives the quota that can be configured
      • Edge Gateway
        • –Provides network services: DHCP, Gateway, DNS, Firewall, 88888
        • –Use High Availability for critical workloads
        • –Avoid Advanced Options unless needed – simple is often best
      • Org vDC Network
        • –A common network pool for vApp to vApp communication
        • –Can be utilized by other Org vDCs if desired

    Comments

    Post a Comment

    Popular posts from this blog

    Designing and Configuring an Enterprise Cloud Solution

    Image
    We have already discussed the architecture of a vRealize Automation environment in previous post. Many topics, including the physical, conceptual and logical design have been covered. These design documents helped us to set up a vRealize Automation environment. However, in order to proceed with the configuration of vRealize Automation, we again need to shift our focus towards the design aspects of implementing a vRealize Automation platform. This chapter will help you to understand these fundamental design concepts. In the following, we will focus on the different components as well as on security aspects. For the most part, this chapter deals with describing the building blocks within a vRealize Automation environment. Afterwards, it will end up with discussing a couple of further design aspects. This chapter will only focus on design issues. The implementation itself will be described in the following chapters. 6.1 vRealize Automation Layers Traditionally, one of the key requ...
    Read more

    "Host IPMI system event log status" alarm in vCenter Server

    To resolve this issue, ensure that the NTP settings are correct on the ESXi host, clear the IPMI System Event log file, and reset the sensors.   To clear the IPMI System Event log file and reset the sensors: Open vCenter Server using the vSphere Client. In the vCenter Server Inventory, select the ESXi/ESX host. Click the  Hardware Status  tab. Click  System Event log  under View. Click  Reset Event   Log . The red alert is removed from the System Event log. Click  Reset Sensors  to reset the host sensors. Starting with ESXi 5.1 U2, 5,5 P01 and later, you can use the  localcli  command line to clear the IPMI SEL logs. To clear the IPMI SEL logs in ESXi 5.1 and later: Connect to the ESXi host through SSH.  Run this command: localcli hardware ipmi sel clear If you find an incorrect date and if you are unable to reset the logs: In ESX - Restart the management agents and  sfcbd...
    Read more

    ESXi : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down

    We had an issue suddenly getting an alert : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected portgroups:"vMotion", "Management Network". So as a troubleshooting Select the ESXi host effected Click on Configuration, Select Networking, Click on vSwitch0 Properties,Click on Network adapters Select on vmnic0, Click on remove, Click on Close Again Select Networking, Click on vSwitch0 Properties,Click on Network adapters, Click on Add, Select the vmnic0, Click on Next, Click on Next, Click on Finish Now Click on Ports tab of vSwitch Properties, Select on vMotion, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select on vmnic0, Click on Move Down to Standby Adapters, Click on OK Now Click on Ports tab of vSwitch Properties, Select on Management Network, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select o...
    Read more