Home > Articles > Certification

  • Print
  • + Share This
This chapter is from the book

Distributed Resource Scheduler

  • Distributed Resource Scheduler (DRS) Cluster
  • Affinity Rules
  • VMware EVC

Cram Saver

If you can correctly answer these questions before going through this section, save time by skimming the Exam Alerts in this section and then completing the Cram Quiz at the end of the section.

  1. What color is assigned to a DRS cluster that is overcommitted?

    bullet.jpg

    A.

    Red

    bullet.jpg

    B.

    Orange

    bullet.jpg

    C.

    Blue

    bullet.jpg

    D.

    Yellow

  2. How do you configure two VMs so that they are never present on the same host at the same time?

    bullet.jpg

    A.

    Affinity

    bullet.jpg

    B.

    Policy

    bullet.jpg

    C.

    Permissions

    bullet.jpg

    D.

    Anti-Affinity

Answers

  1. D is correct. A DRS cluster that is overcommitted is assigned the color yellow; therefore, answers A, B, and C are incorrect.

  2. D is correct. Configuring an Anti-Affinity rule would be the correct course of action and the correct answer to the question. Affinity rules force VMs to stay together on the same host. Choices B and C are incorrect.

VMware DRS is an enterprise-level feature that uses vMotion to load balance the CPU and memory resources of all ESX/ESXi hosts within a given DRS cluster. DRS is also used to enforce resource policies and respect placement constraints.

DRS functions efficiently using clusters. A cluster is the implicit collection of CPU and memory resources across ESX/ESXi hosts that are members of this cluster to allow for the creation of VMware DRS clusters and VMware High Availability (HA) clusters. A cluster is an object that appears in the vCenter inventory and, like all other objects, can be assigned permissions. It can have a maximum of 32 nodes, or 320 VMs per host, or 3000 VMs per cluster, whichever maximum is reached first.

In other words, you can have 32 hosts in the cluster, but you are then limited to only 93 VMs per host, or you can have 300 VMs on 10 hosts, or 20 hosts with 150 VMs, and so on.

After you add ESX/ESXi hosts as nodes in a DRS cluster, DRS then monitors these ESX/ESXi hosts. If DRS detects high CPU utilization or high memory utilization on a particular host, it uses vMotion to migrate some VMs off the host with resource constraints to a host that is not experiencing resource constraints. DRS constantly plays this role to ensure that all ESX/ESXi hosts never have resource constraints.

DRS Automation Process

The DRS automation process involves initial placement of the virtual machines when they are first powered on and later on dynamically load balancing VMs on the best-suited host that will render the best performance. As shown in Figure 8.9, the automation process options are as follows:

  • Manual: If you select this option, vCenter suggests which VM needs to be initially placed on which host at power on and later suggests which VM should be migrated to a different host; however, vCenter does not perform either task automatically.
  • Partially Automated: If you select this option, VMs are automatically placed at power on; however, for future load balancing, vCenter only suggests the migration but does not perform it.
  • Fully Automated: If you select this option, vCenter suggests and performs the initial placement of VMs at power on and automatically migrates them to maintain the most adequate load balancing.
Figure 8.9

Figure 8.9 DRS cluster automation.

When set to Manual or Partially Automated, DRS recommends VMs that need to be migrated to improve performance and maintain proper load balancing in the cluster. To view these recommendations, you can select the DRS cluster in the vCenter inventory and click the DRS Recommendations tab, as shown in Figure 8.10.

Figure 8.10

Figure 8.10 DRS recommendations.

If you choose a fully automated load-balancing schedule, you can also control the frequency at which migrations occur. DRS analyzes the VMs and rates them on a five-star basis, with five stars meaning the VM must move from one host to another and one star meaning the VM does not necessarily need to move or, if moved, the change is not significant. Your options are as follows:

  • Most Conservative: This option means DRS migrates VMs very infrequently and only when it must (that is, when VMs have five stars).
  • Moderately Conservative: This option means that DRS migrates VMs with four stars or more. This option promises significant improvement.
  • Default: This option moves VMs with three stars or more and promises good improvement.
  • Moderately Aggressive: This option moves VMs with two stars or more and promises moderate improvement.
  • Aggressive: This option migrates VMs with one star or more and promises slight improvement.

DRS automation levels can also be managed on the virtual machine level, where you manually assign the automation level for each VM in the cluster. To configure the automation level based on the VM, right-click the cluster where the VM is a member and go to Edit Settings. On the left pane, select Virtual Machine Options. You then are presented with a list of VMs that are members of this cluster on the right. You can change the automation level manually. Figure 8.11 shows an example.

Figure 8.11

Figure 8.11 VM level automation.

DRS Cluster Validity

Monitoring a DRS cluster to ensure that there are no errors is critical. A resource pool can be in one of three states: valid, overcommitted, or invalid. A DRS cluster is considered to be valid, functioning, and healthy when the resource availability satisfies all the reservations and supports all running VMs. In the event that a DRS cluster is not considered valid, resource pools notify you that there is a problem by changing the color of the resource pool in the vSphere client as follows:

  • Yellow means that the resource pool is overcommitted in terms of resources.
  • Red means that the resource pool has violated the DRS cluster rules or high-availability rules and is thereby considered invalid.

DRS Rules

DRS enables you to set rules that govern whether VMs can exist on the same ESX/ESXi host at the same time or if they should always be separated and never exist on the same host at the same time. This capability can be useful if you are trying to avoid a single point of failure for a particular VM and want to make sure that the DRS algorithm never places VMs assigned in the rules on the same host. That being said, you can choose to have the VMs on the same host at all times, so if one VM is migrated, the other follows as well. These rules are known as VM-VM Affinity rules and have two options:

  • Affinity: This rule implies that VMs should be on the same ESX/ESXi host at all times.
  • Anti-Affinity: This rule implies that VMs cannot exist on the same ESX/ESXi host at the same time.

The release of vSphere 4.1 introduced a new Affinity rule known as VM-Host Affinity Rules. These rules determine whether groups of VMs can or cannot exist on groups of ESX/ESXi hosts. With these rules, you can build groups of specific VMs and groups of specific ESX/ESXi hosts and then implement Affinity or Anti-Affinity rules. VM-Host affinity rules have the following options:

  • Must run on hosts in group: This rule implies it is a requirement that the VM group be on the same ESX/ESXi host group at all times.
  • Should run on hosts in group: This rule implies it is preferred that the VM group be on the same ESX/ESXi host group at all times.
  • Must not run on hosts in group: This rule implies it is a requirement that the VM group NOT be on the same ESX/ESXi host group at all times.
  • Should not run on hosts in group: This rule implies it is preferred that the VM group NOT be on the same ESX/ESXi host group at all times.

You can access these rules by right-clicking your cluster and pointing to Edit Settings. You then see the Rules section on the left. Select it and click Add. Figure 8.12 shows an example of how you can set a rule to never allow two VMs to be on the same host at the same time.

Figure 8.12

Figure 8.12 DRS rules.

VMware EVC

As we have been discussing in this chapter, vMotion has certain CPU requirements that need to be met before a successful live migration of VMs can take place between hosts. Considering OEM server manufacturers constantly upgrade the CPUs that ship with their server models, it can become challenging when you purchase servers at different intervals. At some point, you are bound to have hardware of different CPU families.

VMware Enhanced vMotion Compatibility is similar in function to the NX/XD feature, except it is configured on a cluster basis and affects the hosts in the cluster while the NX/XD feature is implemented on a VM level. When creating an EVC cluster, you are instructing vSphere to find the lowest common denominator between all the hosts' CPUs thereby allowing the highest level of vMotion compatibility.

As you can see in Figure 8.13, creating a VMware EVC cluster is easy. Choose Edit Settings on your existing DRS cluster and select VMware EVC from the left pane. You can then configure the options appropriately.

Figure 8.13

Figure 8.13 VMware EVC enabled cluster.

Cram Quiz

Answer these questions. The answers follow the last question. If you cannot answer these questions correctly, consider reading the section again.

  1. Which setting is an invalid level when Fully Automated DRS cluster load balancing is selected?

    bullet.jpg

    A.

    Conservative

    bullet.jpg

    B.

    Aggressive

    bullet.jpg

    C.

    Default

    bullet.jpg

    D.

    Low

  2. Which of the following is not a DRS cluster automation level? (Select all that apply.)

    bullet.jpg

    A.

    Manual

    bullet.jpg

    B.

    Semi Manual

    bullet.jpg

    C.

    Fully Automated

    bullet.jpg

    D.

    Semi Automated

  3. How many cluster nodes are supported for each DRS cluster?

    bullet.jpg

    A.

    16

    bullet.jpg

    B.

    24

    bullet.jpg

    C.

    32

    bullet.jpg

    D.

    36

Cram Quiz Answers

  1. D is correct. Low is not a valid frequency level when Fully Automated is selected; therefore, answers A, B, and C are incorrect.

  2. B and D are correct. Semi Manual and Semi Automated are invalid and do not exist. The three levels of automation are Manual, Partially Automated, and Fully Automated; therefore, answers A and C are incorrect.

  3. C is correct. VMware DRS clusters support up to 32 ESX/ESXi hosts or nodes per cluster; therefore, answers A, B, and D are incorrect.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020