Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Cluster Grid Example Implementations

In this section, a sample Sun Cluster Grid implementation is outlined, demonstrating how to perform the following tasks:

  • Translate site gathered information into grid architectural features.

  • Take advantage of features that enable the management of heterogeneous environments in terms of the compute tier.

  • Configure the MPI environment, OpenMP, serial, and interactive queues to maximize utilization.

  • Take advantage of the inherent scalability of the architecture, and the flexibility with respect to changing user demands.

  • Consider various network architectures to enhance the grid environment.

Scenario 1—General HPC Environment

This example represents a multi-departmental academic site that caters to 200 users with differing computational requirements. The information gathering stage is outlined below in terms of service provision and the three tiers.

Service Provision

In this example, a highly available service is not required, but system health monitoring is considered advantageous. The authentication scheme for the new cluster grid should integrate with the existing University scheme so that users can use their existing user names and passwords.

It is expected that the cluster grid will be configured to allow the compute tier to scale four-fold in terms of CPU count without further enhancement of the management tier.

A new storage facility will be associated with the cluster grid giving users significant disk space (at least 2 Gbytes per user) on high performance storage arrays. The total storage capacity can be increased within the year.

The DRM service is not currently required to implement a fair-share scheme across the departments, but this might be a future requirement.

Access Tier

Users are competent with UNIX and expect to have telnet, rlogin, and ftp access to the cluster grid storage system to configure jobs. Because the authentication scheme is to be integrated with the university's existing authentication scheme, the access nodes will be added to that scheme. A maximum of 50 users are expected to be simultaneously accessing cluster grid services.

A desktop machine with a monitor is required by the administrator for accessing the cluster grid management software.

The HPC resource must cater to mixed workloads including throughput jobs, highly parallel jobs as well as large memory and medium-scaling threaded or OpenMP jobs.

Management Tier

Besides the DRM, there is a requirement for the file storage to be served out to the compute tier using NFS. This storage should be fully backed up. Some health monitoring service should also be installed.

Compute Tier

The HPC resource must cater to mixed workloads including throughput jobs, highly parallel jobs as well as large memory and medium-scaling threaded or OpenMP jobs. The applications are roughly characterized in FIGURE 4. There are large numbers of serial jobs and a number of shared-memory parallel applications (OpenMP and threaded). A few OpenMP applications scale to 20 processors, while the high scaling jobs of 20 and above processors are MPI.

Data access patterns are highly varied but in this case, one key serial application is typified by very high read intensive I/O. Application runtimes for serial applications are typically 2–4 hours. The parallel application users have requested the ability to run for 24 hours on occasion, but day-to-day usage will include runtimes about 2–12 hours.

Design Implementation

In this section, the information gathering results are translated into hardware and software implementation decisions (FIGURE 3).

Figure 3FIGURE 3 Grid Hardware and Network Infrastructure for Scenario 1

Access Tier

Users will be allowed login access to one dual-CPU node (a Sun Blade™ 1000 workstation) in order to access the cluster grid file system and submit jobs. These machines must cater for file transfers to and from the storage system. A maximum of 50 users are expected to be simultaneously accessing cluster grid services.

A Sun Blade 100 is supplied for the administrator's use.

Management Tier

A four-way Sun Fire V480 server is used for the SGE and SunMC server. The internal disks are mirrored for added resilience. this configuration should allow for substantial future scaling of the compute tier. The NFS service is provided by the Sun Fire 6800 server which is to be used also in the compute tier. The Sun Fire 6800 server will also provide full backup service through the use of a Sun StorEdge L25 tape library.

Compute Tier

The applications are characterized in FIGURE 4. There are large numbers of serial jobs and a number of shared-memory based parallel applications (OpenMP and threaded), as well as MPI applications beyond 40 processors.

Figure 4FIGURE 4 Approximate Workload for Example Site

A single Sun fire 6800 server is provided primarily to supply compute power for those OpenMP jobs that scale beyond 8 threads. It may also provide a platform for those MPI jobs that benefit from the SMP architecture. Smaller threaded jobs and serial jobs requiring greater than 1 Gbyte memory will be catered to by three Sun Fire V880 servers.

Price and performance considerations usually tend towards distributed memory systems for those appropriate applications. In this example, while applications scaling up to 24 processors must be catered to using a shared memory system, the high scaling MPI applications can take advantage of a distributed memory system such as a network of workstations (NOW). A Linux-based cluster, comprising x86 architecture processors packaged in a large number of dual-processor enclosures caters to those MPI jobs scaling beyond 24 processors. The Linux cluster is interconnected with Myrinet, Gigabit Ethernet, and serial network.

Shared storage across the cluster grid is hosted by a Sun Fire 6800 server on two Sun StorEdge™ T3 disk arrays implementing hardware RAID 5. The choice to host the shared storage here was by the desire to host storage direct attached (and therefore lowest access latency) on the largest SMP server, which is likely to be the host which accesses the storage most frequently.

Networks

Serial, gigabit Ethernet and Myrinet interconnects all feature in the example solution as shown in FIGURE 3. Gigabit Ethernet interconnects the management server with all compute hosts. A dedicated Myrinet interconnect provided a low-latency connection between the nodes of the Linux cluster.

Software

This section describes the software as it is applied to the example implementation.

Sun Grid Engine

In this example, the SGE is sufficient (rather than SGEEE) because fair-share scheduling across multiple departments is not required. If resource allocation based on departments or projects becomes a future requirement, the upgrade to the Enterprise Edition is a straightforward implementation.

The SGE queue structure must cater to serial, OpenMP and MPI jobs.

Queues are implemented on a calendar basis across the cluster grid. In the daytime, short 2- or 4-hour queues are enabled on all machines covering parallel environments and serial queues. Each evening, a 12-hour queue is enabled in place of the daytime queues. On weekends, 24-hour queues are enabled for jobs with long runtimes.

Three parallel queues for OpenMP jobs exist:

  • 20-slot PE on Sun Fire 6800 server

  • 8-slot PE on Sun Fire V880(a) server

  • 4-slot PE on Sun Fire V880(b) server

A total of 12 slots are available for serial jobs on the Sun Fire V880 servers (four slots on the Sun Fire V880(b) and 8 slots on the Sun Fire V880(c)).

CacheFS software is implemented on one of the Sun Fire V880 servers. The CacheFS file system encompasses the subdirectory, which holds the data that is prone to high read-intensive activity by one key serial application. A Sun Grid Engine queue is configured on this machine to run jobs requesting this application.

On the management host, four slots are allocated for users to run interactive jobs (leaving approximately four processors continuously available for system processes, DRM and SunMC.)

MPI Environments

MPICH is installed across the Linux cluster to provide the runtime environment for MPI applications. MPICH can be tightly integrated with Sun Grid Engine.

Scenario 2– Minimal Cluster Grid Implementation

This scenario (FIGURE 5) demonstrates a minimal cluster grid implementation that uses the Sun Grid Engine resource manager to control a number of single processor machines. The following information pertains to the requirements placed upon the cluster grid.

Figure 5FIGURE 5 Grid Hardware and Network Infrastructure for Scenario 2

Service Provision

The service provision requirement calls for a queueing system to optimize the utilization of a new compute farm. The new service should impose minimal disruption to users, and take into account moderate scaling of the compute layer for future growth. Storage should be integrated within the new system.

Access Tier

Users currently work using desktop workstations and these should be integrated into the access tier to allow access to file storage, job submissions, and so on. A maximum of 30 users are expected to simultaneously access the cluster grid.

Minimal health monitoring of the system and administrative access is needed from an existing administration workstation.

Management Tier

DRM and NFS services must be provided. An existing SunMC server will be used to monitor any servers which are critical to the grid service.

Compute Tier

The HPC resource must cater to serial jobs only. A small number of floating point intensive applications are used. Jobs have memory requirements of approximately 500 Mbytes, with approximately ten percent of the jobs requiring up to 2 Gbytes. Average runtimes are around 30 minutes with little variation.

Design Implementation

In this section, the information gathering results are translated into hardware and software implementation decisions.

Access Tier

The user's existing desktop workstations will be registered with SGE as submit hosts, allowing users to submit applications without using telnet, and rlogin type commands. Access to the cluster grid file system where users have file space will be enabled using NFS.

Administrative access will be provided by registering the existing administration workstation as an admin host with SGE.

Management Tier

The management tier service is provided by a single 2-way Sun Fire 280R with a Sun StorEdge D1000 array directly attached. A SunMC agent will be installed on the 280R server so it can be monitored by the existing SunMC server. The file space will be NFS shared across both the Compute Layer and the users desktops. The network for the cluster grid (between compute and management layer) will be isolated from the office traffic through the use of an additional gigabit Ethernet interface which will connect the 280R to the compute layer only using a switch.

Serial connections to the compute tier will be installed along with a terminal concentrator to allow console access by the administrator.

Compute Tier

The compute tier is composed of 20 Sun Fire V100 servers, each configured with 1 Gbyte of RAM. An additional four Sun Fire V100 systems will be configured with 2 Gbyte of RAM.

Software

The SGE queue structure will be simple. This simplicity will be reflected in a fast scheduling loop which will improve throughput if very large numbers of jobs are submitted over a short time span. By default, the SGE installation results in single slot queues on single processor machines. Those jobs requesting greater than 1 Gbyte of RAM will be automatically scheduled to use the 2 Gbyte compute nodes. Further adjustments to time limits on these queues or tuning of the scheduler should be considered during the early stages of implementation.

  • + 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