The Anatomy of Grid前部译文(2)

 2005年的老博，转到这个空间来。

2 The Emergence of Virtual Organizations
2．虚拟组织的出现

Consider the following four scenarios:
想象下面的情景：

1. A company needing to reach a decision on the placement of a new factory invokes a sophisticated financial forecasting model from an ASP, providing it with access to appropriate proprietary historical data from a corporate database on storage systems operated by an SSP. During the decision-making meeting, what-if scenarios are run collaboratively and interactively, even though the division heads participating in the decision are located in different cities. The ASP itself contracts with a cycle provider for additional “oomph” during particularly demanding scenarios, requiring of course that cycles meet desired security and performance requirements.
1． 一个公司为了新厂的选址，需要ASP提供复杂的财务预测，同时需要SSP操作存储系统并从数据库中提供相应的历史资料。在决策会议上，处在不同城市的部门 主管正在交互地、合作地进行讨论。ASP在会上与一个设备运行提供商商榷，要求更高的运行性能以及满足相应的安全需求。

2. An industrial consortium formed to develop a feasibility study for a next-generation supersonic aircraft undertakes a highly accurate multidisciplinary simulation of the entire aircraft. This simulation integrates proprietary software components developed by different participants, with each component operating on that participant’s computers and having access to appropriate design databases and other data made available to the consortium by its members.
2．为研究下一代超声波飞机，一个工业团体结合多种学科知识对整个飞行器进行模拟。这个模拟试验将部署在不同参与者处的专用软件整合起来，每个模块都是在参与者的计算机上进行操作的，它们能适当地对数据库进行存取，并让其他数据能够被团体成员获得。

3. A crisis management team responds to a chemical spill by using local weather and soil models to estimate the spread of the spill, determining the impact based on population location as well as geographic features such as rivers and water supplies, creating a short term mitigation plan (perhaps based on chemical reaction models), and tasking emergency response personnel by planning and coordinating evacuation, notifying hospitals, and so forth.
3．有个风险管理小组对一种化学药品负责，他们使用天气和土壤模型来对其扩散性进行评估，研究地区人口和地理特征的影响，比如河流与供水。他们寻求一种短期缓和方案（可能是基于化学反应的），制定个人紧急反应和情况恶化时应对的方法并报告医院，等等。

4. Thousands of physicists at hundreds of laboratories and universities worldwide come together to design, create, operate, and analyze the products of a major detector at CERN, the European high energy physics laboratory. During the analysis phase, they pool their computing, storage, and networking resources to create a “Data Grid” capable of analyzing per bytes of data [22, 44, 53].
4． 在世界各地的数以千计的医生和数以百计的大学研究人员在一起设计、创造、工作，并用CERN（the European high energy physics laboratory）的设备分析检测这种产品。在分析的过程中，他们公用计算、存储、网络资源来建设一个能分析每比特数据的“数据”网格

These four examples differ in many respects: the number and type of participants, the types of activities, the duration and scale of the interaction, and the resources being shared. But they also have much in common, as discussed in the following (see also Figure 1).
上面的4例，反映了不同的参与者数量、不同的活动形式、不同的共享资源的持续时间和交互范围。但是他们也有着很多共同点，下面将进行探讨。

In each case, a number of mutually distrustful participants with varying degrees of prior relationship (perhaps none at all) want to share resources in order to perform some task. Furthermore, sharing is about more than simply document exchange (as in “virtual enterprises” [18]): it can involve direct access to remote software, computers, data, sensors, and other resources. For example, members of a consortium may provide access to specialized software and data and/or pool their computational resources.
每种情况下，每个参与者 都想通过共享资源来完成任务，而他们之间的信任关系是各不相同的（或许根本就没有）。另外，共享不仅仅包括简单的文件交换（像在“虚拟企业”里那样 [18]），通过它能直接访问软件、计算机、数据、传感器以及其他资源。例如，某个团体的成员能够将特定的软件和数据共享，让别人可以访问他们的计算资 源。

Figure 1: An actual organization can participate in one or more VOs by sharing some or all of its resources. We show three actual organizations (the ovals), and two VOs: P, which links participants in an aerospace design consortium, and Q, which links colleagues who have agreed to share spare computing cycles, for example to run ray tracing computations. The organization on the left participates in P, the one to the right participates in Q, and the third is a member of both P and Q. The policies governing access to resources (summarized in “quotes”) vary according to the actual organizations, resources, and VOs involved.
图 1：一个实际的组织可以通过共享资源来加入一个或多个VO。我们展示了三个实际组织（椭圆）和两个VO：P和一个航空设计团体相关，Q中的成员共享空闲的 计算机指令周期，做诸如光线追踪的计算。左边的组织加入了P，右边的组织加入了Q，中间的同时加入了P和Q。在不同的实际组织、资源、和VO中，资源的访 问管理策略（通过摘要“引用”）是各不相同的。

Resource sharing is conditional: each resource owner makes resources available, subject to constraints on when, where, and what can be done. For example, a participant in VO P of Figure 1 might allow VO partners to invoke their simulation service only for “simple” problems. Resource consumers may also place constraints on properties of the resources they are prepared to work with. For example, a participant in VO Q might accept only pooled computational resources certified as “secure.” The implementation of such constraints requires mechanisms for expressing policies, for establishing the identity of a consumer or resource (authentication), and for determining whether an operation is consistent with applicable sharing relationships (authorization).
资 源共享是有条件的：每个资源所有者让资源变为可用时要取决于时间、地点、事情。例如，图中P这个VO的某个参与者向它的合作者提供的服务可能仅仅能够解决 简单问题。资源消费者很可能仍不能获得他们工作时想要的资源。例如，图中Q这个VO的某个参与者仅仅能获得被认可为“安全”的资源。为应用这些约束条件， 要有表达解释策略、认证消费者和资源的机制（认证）、以及有机制判断对于资源来说某个操作是否可执行（授权）。

Sharing relationships can vary dynamically over time, in terms of the resources involved, the nature of the access permitted, and the participants to whom access is permitted. And these relationships do not necessarily involve an explicitly named set of individuals, but rather may be defined implicitly by the policies that govern access to resources. For example, an organization might enable access by anyone who can demonstrate that they are a “customer” or a “student.” The dynamic nature of sharing relationships means that we require mechanisms for discovering and characterizing the nature of the relationships that exist at a particular point in time. For example, a new participant joining VO Q must be able to determine what resources it is able to access, the “quality” of these resources, and the policies that govern access.
共享活动涉及到资源、基本存取权限 和用户访问权限。随时间的变化，他们间的关系也各不相同。这些关系中的用户组可能并不清楚明白，而是通过资源访问管理策略进行了模糊的定义。譬如，一个组 织让任何证明自己为“消费者”或“学生”的人进行访问。这个动态的共享关系意味着，我们需要一种能在特定时间点发现和记录关系状态的机制。比如，加入Q这 个VO的新成员必须判断哪些资源它可以访问，搞清楚这些资源的“质量”，以及管理访问的策略。

Sharing relationships are often not simply client-server, but peer to peer: providers can be consumers, and sharing relationships can exist among any subset of participants. Sharing relationships may be combined to coordinate use across many resources, each owned by different organizations. For example, in VO Q, a computation started on one pooled computational resource may subsequently access data or initiate subcomputations elsewhere. The ability to delegate authority in controlled ways becomes important in such situations, as do mechanisms for coordinating operations across multiple resources (e.g., coscheduling).
共享关系不是简单的C/S，其中的P2P提供者可以是消费者，而且共 享关系存在于其中的任何参与者。共享关系可以用来调整对许多不同组织拥有的资源的访问。举个例子，在Q这个VO中，在集中的计算资源中开始执行一组计算， 它可能会随后访问其他地方的数据或进行子计算。在这种情况下，授权的能力变得很重要。协调多个资源间访问的机制也很重要。

The same resource may be used in different ways, depending on the restrictions placed on the sharing and the goal of the sharing. For example, a computer may be used only to run a specific piece of software in one sharing arrangement, while it may provide generic compute cycles in another. Because of the lack of a priori knowledge about how a resource may be used, performance metrics, expectations, and limitations (i.e., quality of service) may be part of the conditions placed on resource sharing or usage.
由 于不用的共享规则和共享目标，相同的资源可能会用在不同的地方。例如，某个计算机在一次任务中可能仅仅用来运行一个特定的程序片断，而与此同时它可能在向 其他任务同步提供CPU。由于无从知道资源的优先级分配、运行质量、期望值，一些限制（如，服务质量）可能也是资源共享和利用时的一部分条件。

These characteristics and requirements define what we term a virtual organization, a concept that we believe is becoming fundamental to much of modern computing. VOs enable disparate groups of organizations and/or individuals to share resources in a controlled fashion, so that members may collaborate to achieve a shared goal.
通过这些特性和需求我们定义了虚拟企业（VO），一个我们认为正成为当前计算的基础的概念。VO使得分散的组织和个人之间的资源共享成为可能，因此成员们能通过合作来实现一个共享目标。

3 The Nature of Grid Architecture
3 网格体系结构的本质

The establishment, management, and exploitation of dynamic, cross-organizational VO sharing relationships require new technology. We structure our discussion of this technology in terms of a Grid architecture that identifies fundamental system components, specifies the purpose and function of these components, and indicates how these components interact with one another.
建立、管理和开发动态、组织交叉的VO是需要新技术的工作。我们对此技术进行论述时依靠的是“网格体系结构”，以此来识别基本的系统组件，指明这些组件的目的和功能，并阐述这些组件是如何互相作用的。

In defining a Grid architecture, we start from the perspective that effective VO operation requires that we be able to establish sharing relationships among any potential participants. Interoperability is thus the central issue to be addressed. In a networked environment, interoperability means common protocols. Hence, our Grid architecture is first and foremost protocol architecture, with protocols defining the basic mechanisms by which VO users and resources negotiate, establish, manage, and exploit sharing relationships. A standards-based open architecture facilitates extensibility, interoperability, portability, and code sharing; standard protocols make it easy to define standard services that provide enhanced capabilities. We can also construct Application Programming Interfaces and Software Development Kits (see Appendix for definitions) to provide the programming abstractions required to create a usable Grid. Together, this technology and architecture constitute what is often termed middleware (“the services needed to support a common set of applications in a distributed network environment” [3]), although we avoid that term here due to its vagueness. We discuss each of these points in the following.
在定义一个网格体系结构的时候，高效的VO操作 需要我们能够在任何参与者之间建立共享关系。因此互操作性是要解决的中心问题。在网络环境中，互操作性需要通用协议。因而，我们的网格体系结构首先是协议 体系结构，通过协议来定义基本机制，以此来使VO的用户能够协商、建立、管理和开发共享关系。一个基于标准的开放的体系结构能够促进扩展性、互操作性、可 移植性、和代码共享。标准协议使得定义提供高性能的服务的过程变得容易。我们也规划了API和SDK（在附录中有定义）来提供创建一个网格所需的抽象化程 序。这种技术和体系结构组合在一起常常被称为中间件（“这种服务要为一个分布式网络环境中的一组通用应用提供支持”[3]），不过我们为避免表达含糊在这 里不用这个术语。我们在下面论述了这些要点。

Why is interoperability such a fundamental concern? At issue is our need to ensure that sharing relationships can be initiated among arbitrary parties, accommodating new participants dynamically, across different platforms, languages, and programming environments. In this context, mechanisms serve little purpose if they are not defined and implemented so as to be interoperable across organizational boundaries, operational policies, and resource types. Without interoperability, VO applications and participants are forced to enter into bilateral sharing arrangements, as there is no assurance that the mechanisms used between any two parties will extend to any other parties. Without such assurance, dynamic VO formation is all but impossible, and the types of VOs that can be formed are severely limited. Just as theWeb revolutionized information sharing by providing a universal protocol and syntax (HTTP and HTML) for information exchange, so we require standard protocols and syntaxes for general resource sharing.

互操作性为什么占有如此重要的位置？因为我们需要在任意不同的单位之间建立共享关系，动态的调和新参 与者――通过不同的平台、语言和编程环境。在此状态下，如果他们没被定义和实现，就实现不了跨组织边界、执行策略、资源类型的互操作，这些机制也就不起作 用。没有互操作性，在参与和应用VO时就必须进行双边的共享分配，因为此时不能保证双边使用的机制能扩展到其他的地方去。没有这样的保证，动态VO结构几 乎是不可能实现的，而VO能够存在的类型也极为有限。就像WEB通过提供通用语法和协议（HTTP和HTML）使信息共享产生了革命，我们在资源共享方面 也需要标准的语法和协议。
Why are protocols critical to interoperability? A protocol definition specifies how distributed system elements interact with one another in order to achieve a specified behavior, and the structure of the information exchanged during this interaction. This focus on externals (interactions) rather than internals (software, resource characteristics) has important pragmatic benefits. VOs tend to be fluid; hence, the mechanisms used to discover resources, establish identity, determine authorization, and initiate sharing must be flexible and lightweight, so that resource-sharing arrangements can be established and changed quickly. Because VOs complement rather than replace existing institutions, sharing mechanisms cannot require substantial changes to local policies and must allow individual institutions to maintain ultimate control over their own resources. Since protocols govern the interaction between components, and not the implementation of the components, local control is preserved.
为 何协议对互操作性来说很关键？一个协议不仅定义特定了分布的系统元件之间为某目的而进行的交互，也包括这些交互之间的信息交换。这样对外部（交互）的关注 比对内部（软件、资源特性）的关注更有实际价值。VO要是明晰的，于是它的机制在发现资源、建立证书、进行认证和开始共享时必须是可扩展的和轻量级的，这 样的资源共享的分配才可能快速的建立和改变。因为VO是补充而不是对现有机构和共享机制的替换，它不能要求本地策略因此而进行底层的改变，同时要让单个机 构能够继续对自己资源进行终端控制。协议管理了组件之间的交互而不是它们的执行。本地协议是被保留的。

Why are services important? A service (see Appendix) is defined solely by the protocol that it speaks and the behaviors that it implements. The definition of standard services—for access to computation, access to data, resource discovery, coscheduling, data replication, and so forth— allows us to enhance the services offered to VO participants and also to abstract away resource-specific details that would otherwise hinder the development of VO applications.
Why do we also consider Application Programming Interfaces (APIs) and Software Development Kits (SDKs)? There is, of course, more to VOs than interoperability, protocols, and services. Developers must be able to develop sophisticated applications in complex and dynamic execution environments. Users must be able to operate these applications. Application robustness, correctness, development costs, and maintenance costs are all important concerns. Standard abstractions, APIs, and SDKs can accelerate code development, enable code sharing, and enhance application portability. APIs and SDKs are an adjunct to, not an alternative to, protocols. Without standard protocols, interoperability can be achieved at the API level only by using a single implementation everywhere—infeasible in many interesting VOs—or by having every implementation know the details of every other implementation. (The Jini approach [6] of downloading protocol code to a remote site does not circumvent this requirement.)
为什么服务重要？一个服务 （见附录）通过一种协议来表达和工作。标准服务――对于获得计算，获得数据，资源发现，同步安排，数据复制，等等――让我们能增进对VO成员提供的服务， 对于那些可能妨碍VO应用发展的抽象的特定资源细节亦如此。为什么我们也关注API和SDK？因为互操作性、协议、服务的需要。开发者必须能在多变的执行 环境中开发出的复杂的系统。用户要能操作这些应用程序。应用程序的健壮性，正确性，开发成本和维护成本都是要考虑的重要因素。标准的抽象接口，API和 SDK能加速代码开发，有利代码共享，并增强程序的可移植性。API和SDK是协议的附加和不是与其无关。没有标准协议的话，若要达到API层面的互操 作，在到处就只能用相同的执行方式――在许多有意思的VO中是不可行的――或者每种执行方式都知道其他每种执行方式的细节。（JINI中下载远程站点的协 议代码没能绕过这个需求）

In summary, our approach to Grid architecture emphasizes the identification and definition of
protocols and services, first; and APIs and SDKs, second.
总的来说，我们着重论述了网格体系结构的认证，对协议、服务和API、SDK的定义