Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 631560

Summary: Overview comments
Product: Red Hat Enterprise MRG Reporter: Robert Rati <rrati>
Component: Grid_User_GuideAssignee: Lana Brindley <lbrindle>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Needle <jneedle>
Severity: medium Docs Contact:
Priority: medium    
Version: DevelopmentCC: mhideo
Target Milestone: 1.3   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-14 20:27:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Robert Rati 2010-09-07 21:19:44 UTC 
Description of problem:
- Strike paragraph two, it is describing a feature we do not support
- MRG Grid doesn't "implement" ClassAds - implement -> uses
- Describing Grid as a Broker is applyng messaging context where it is only confusing
- We hope...?

Section needs to be rewritten, it mixes details with overview

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Lana Brindley 2010-09-13 03:48:44 UTC 
<chapter id="chap-Grid_User_Guide-Overview">
	<title>Overview</title>
	 <para>
		&GRID; uses the computational ability of many computers connected over a network to complete large or resource-intensive operations. &GRID; harnesses existing resources by detecting when a workstation becomes idle, and then relinquishing that resource when it is required by another user. When a job is submitted to &GRID;, it finds an idle machine on the network and begins running the job on that machine. <!--                                                                                                                                                                                                             When the machine is no longer available to &GRID; - that is, when it is brought back out of the idle status - &GRID; will automatically checkpoint the job, and find a new idle machine to continue running. &GRID; will continue the job on the new machine from precisely where it left off.                                                                                                                                                                                                            -->There is no requirement for machines to share file systems, so machines across an entire enterprise can run a job, including machines in different administrative domains.
	</para>
	 <para>
		&GRID; uses ClassAds to simplify job matching and submission. All machines in the &GRID; pool advertise their resources, such as available RAM memory, CPU speed, and virtual memory size in a resource offer ClassAd. When a job is submitted, the submitter specifies a required and a desired set of properties, in a resource request ClassAd. &GRID; matches and ranks resource offer ads with resource request ads, making certain that all requirements in both ads are satisfied. During this match-making process, &GRID; also considers several layers of priority values: the priority the user assigned to the resource request ad, the priority of the user which submitted the ad, and desire of machines in the pool to accept certain types of ClassAds over others.
	</para>
	 <para>
		Groups of researchers, engineers, and scientists have used &GRID; to establish pools ranging in size from a handful to tens of thousands of workstations.
	</para>
</chapter>


LKB