VCP-IaaS Study Notes: Section 5.1

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

Identify the URL name of a newly created Organization

Create/Modify/Delete vCloud Organizations

  • Create
    • Open the New Organization Wizard
      • Open the New Organization wizard to start the process of creating an organization.
      • Procedure
        • Click the Manage & Monitor tab and then click Organizations in the left pane.
        • Click the New Organization button.
        • The New Organization wizard starts.
      • Name the Organization
        • Provide a descriptive name and an optional description for your new organization.
        • Procedure
          • Type an organization name.
            • This name provides a unique identifier that appears as part of the URL that members of the organization use to log in to the organization.
          • Type a display name for the organization.
            • This name appears in the browser header when an organization member uses the unique URL to log in to vCloud Director. An administrator or organization administrator can change this name later.
          • (Optional) Type a description of the organization.
          • Click Next.
      • Specify the Organization LDAP Options
        • You can use an LDAP service to provide a directory of users and groups for the organization. If you do not specify an LDAP service, you must create a user account for each user in the organization. LDAP options can only be set by a system administrator and cannot be modified by an organization administrator.
        • Procedure
          • Select the source for organization users.

          • Provide any additional information that your selection requires.

      • Add Local Users to the Organization
        • Every organization should have at least one local, non-LDAP, organization administrator account, so that users can log in even if the LDAP service is unavailable.
        • Procedure
          • Click Add.
          • Type a user name and password.
          • Assign a role to the user.
          • (Optional) Type the contact information for the user.
          • Select Unlimited or type a user quota for stored and running virtual machines and click OK.
            • These quotas limit the user’s ability to consume storage and compute resources in the organization.
          • Click Next.
      • Set the Organization Catalog Publishing Policy
        • A catalog provides organization users with a library of vApp templates and media that they can use to create vApps and install applications on virtual machines.
        • Generally, catalogs should only be available to users in a single organization, but a system administrator can allow the organization administrator to publish their catalogs to all organizations in the vCloud Director installation.
        • Procedure
          • Select a catalog publishing option.
            • Cannot publish catalogs – Org administrator cannot publish catalogs to users outside of the organization.
            • Allow publishing catalogs to all organizations – Can publish catalogs to all users in all organizations.
      • Configure Email Preferences
        • vCloud Director requires an SMTP server to send user notification and system alert emails. An organization can use the system email settings or use its own email settings.
        • Procedure
          • Select an SMTP server option.
            • Use system default SMTP server –  The organization uses the system SMTP server.
            • Set organization SMTP server The organization uses its own SMTP server. Type the DNS host name or IP address and port number of the SMTP server.
          • Select a notification settings option.
            • Use system default notification settings – The organization uses the system notification settings.
            • Set organization notification settings – The organization uses its own notification settings. Type an email address that appears as the sender for organization emails, type text to use as the subject prefix for organization emails, and select the recipients for organization emails.
      • Configure Organization Lease, Quota, and Limit Settings
        • Leases, quotas, and limits constrain the ability of organization users to consume storage and processing resources. Use these settings to prevent users from depleting or monopolizing an organization’s resources.
        • Procedure
          • Select the lease options for vApps and vApp templates.
            • Leases provide a level of control over an organization’s storage and compute resources by specifying the maximum amount of time that vApps can run and that vApps and vApp templates can be stored. You can also specify what happens to vApps and vApp templates when their storage lease expires.
          • Select the quotas for running and stored virtual machines.
            • Quotas determine how many virtual machines each user in the organization can store and power on in the organization’s virtual datacenters. The quotas that you specify act as the default for all new users added to the organization.
          • Select the limits for resource intensive operations.
            • Certain vCloud Director operations, for example copy and move, are more resource intensive than others. Limits prevent resource intensive operations from affecting all the users in an organization and also provide a defense against denial-of-service attacks.
          • Select the number of simultaneous VMware Remote Console connections for each virtual machine.
            • You might want to limit the number of simultaneous connections for performance or security reasons.
          • NOTE This setting does not affect Virtual Network Computing (VNC) or Remote Desktop Protocol (RDP)connections.
          • (Optional) Select the Account lockout enabled check box, select the number of invalid logins to accept before locking a user account, and select the lockout interval.
          • Click Next.
      • Confirm Settings and Create the Organization
        • Before you create the organization, review the settings you entered.
        • Procedure
          • Review the settings for the organization.
          • (Optional) Click Back to modify the settings.
          • Click Finish to accept the settings and create the organization.
    • Modify
      • NOTE: In almost every case you can change the same thing as when creating a new organization so I will just post where you need to click to modify the setting.
      • Name
        • You must disable the organization before you can rename it.
        • Procedure
          • Click the Manage & Monitor tab and click Organizations in the left pane.
          • Right-click the organization name and select Properties
          • On the General tab, type a new organization name and click OK
        • The internal organization URL changes to reflect the new name
      • Full Name and Description
        •  Click the Manage & Monitor tab and click Organizations in the left pane.
        • Right-click the organization name and select Properties
        • On the General tab, type a new full name or description and click OK.
      • LDAP Options
        • Click the Manage & Monitor tab and click Organizations in the left pane.
        • Right-click the organization name and select Properties
        • Click the LDAP options tab.
        • System administrators and organization administrators who are currently logged in cannot import users and groups using the modified LDAP options until the cache for their current session expires or they log out and log in again.
      • Catalog Publishing Policy
        • Click the Manage & Monitor tab and click Organizations in the left pane.
        • Right- click the organization name and select Properties
        • Click the Catalog Publishing tab.
        • For users who are currently logged in to the organization, changes to the catalog publishing
          policy do not take effect until the cache for their current session expires or
          they log out and log in again.
      • Email Preferences
        • Click the Manage & Monitor tab and click Organizations in the left pane.
        •  Right-click the organization name and select Properties
        • Click the Email Preferences tab.
        • You can Test the email setting with Test Email Settings button.
      • Lease, Quota and Limit Settings
        • Click the Manage & Monitor tab and click Organizations in the left pane.
        • Right-click the organization name and select Properties
        • Click the Policies tab.
    • Delete
      • Prerequisites
        • Before you can delete an organization, you must disable it and delete or change ownership of
          all objects that the organization users own.
      • Procedure
        • Click the Manage & Monitor tab and click Organizations in the left pane
        • Right-click the organization name and select Delete
        • Click Yes.

Configure VM lease times

  • The goal of a runtime lease is to prevent inactive vApps from consuming compute resources. For example, if a user starts a vApp and goes on vacation without stopping it, the vApp continues to consume resources.
  • A runtime lease begins when a user starts a vApp. When a runtime lease expires, vCloud Director stops the vApp.
  • How to configure see button 2:  Configure Organization Lease, Quota, and Limit Settings

Configure Storage lease times

  • The goal of a storage lease is to prevent unused vApps and vApp templates from consuming storage resources.
  • A vApp storage lease begins when a user stops the vApp. Storage leases do not affect running vApps. A vApp template storage lease begins when a user adds the vApp template to a vApp, adds the vApp template to a workspace, downloads, copies, or moves the vApp template.
  • When a storage lease expires, vCloud Director marks the vApp or vApp template as expired, or deletes the vApp or vApp template, depending on the organization policy you set.
  • How to configure see button 2:  Configure Organization Lease, Quota, and Limit Settings

Configure SMTP server information

  • vCloud Director requires an SMTP server to send user notification and system alert emails. You can modify the settings you specified when you created the organization.
  • Procedure
    • Click the Manage & Monitor tab and click Organizations in the left pane.
    • Right-click the organization name and select Properties.
    • Click the Email Preferences tab.
    • Select an SMTP server option.

    • Select a notification settings option.

    • (Optional) Type a destination email address and click Test Email Settings to verify that all SMTP serve settings are configured as expected.
  • Click OK.

Configure notification settings

  • vCloud Director sends system alert emails when it has important information to report. For example, vCloud Director sends an alert when a datastore is running out of space. You can configure vCloud Director to send email alerts to all system administrators or to a specified list of email addresses.
  • Organizations can use the system notification settings, or use custom notification settings.
  • Prerequisites
    • A valid connection to an SMTP server.
  • Procedure
    • Click the Administration tab and click Email in the left pane.
    • Select the recipients of system alert emails and click Apply.

Apply policies to a vCloud Organization

  • Password policy – Account lockout policy: When creating a Org.
  • Catalog publishing policy: Creating and modifying a Org.
  • Storage lease policy: Creating and modifying a Org.
  • These policies are mentioned in the notes above.

Leave a Reply

Your email address will not be published. Required fields are marked *