Learn more about Platform products at http://www.platform.com



EGO concepts and terms



EGO master

The bulk of the intelligence in Platform EGO resides on the EGO master, which receives requests from clients and interacts with the underlying nodes to gather resource information.

EGO hosts contain the local information collection and execution agents taking instructions from the EGO master.


Resources

Resources are physical and logical entities that are used by applications in order to run. A resource of a particular type is associated with attributes. For example, a host has attributes of memory, CPU utilization, operating system type, etc. Platform EGO deals with resource allocation at the granularity of physical hosts, logical sub-divisions of the physical host known as cpu slots, software license features, and includes an extensible resource model to cover storage space, network bandwidth, or data sets as resources whose use is controlled under policies


Consumers

A consumer is a generalized notion of something that uses a resource. A consumer may be an individual user, user group, application, project, department, or an entire company. Consumers are organized hierarchically to model the nature of an organization that wants to access compute resources.


Resource allocation requests

An allocation request is a request for a set of resources made by a client to Platform EGO. The client must identify the originating consumer that this request is for in order for Platform EGO to apply its policies on resource allocation.

A client for each unique consumer wanting to run work should issue a resource allocation request; this allows Platform EGO to coordinate the sharing of resources amongst multiple consumers across different applications. Separate allocation requests should be made for each application or set of services that needs resources, since the allocation resource requirements will likely be different between different applications or sets of services.


Services

Platform EGO is an operating environment for hosting distributed services. Platform EGO provides a facility to define services that must be running and manages the lifecycle of their execution. Putting services under EGO management provides centralized control, virtualization of service placement, and failover.

Platform EGO comes with a set of standard services that would be commonly used within any environment. These include Service Controller, Service Director, web portal service, calendar service, and logging service. These services can be used together with application specific services to manage different workloads and environments.


Containers (Activities)

Services, in general, require some sort of execution context to be established; this may include a virtual machine (VM) or a J2EE application server, or some OS-level construct. To abstract this concept we introduce the notion of an activity or container as a hosting environment for services. The container is the main "unit of execution" from the point of view of the EGO kernel. Within the context of Platform EGO, container and activity have the same meaning. The container term is a legacy of Platform EGO's native C APIs whereas activity is a term that is favored within the context of Web Services. This guide uses both terms in keeping with this philosophy.

The relationship between services and containers is, in general, many to one, i.e., multiple services will run in the same container.

[ Top ]


[ Platform Documentation ]


      Date Modified: July 12, 2006
Platform Computing: www.platform.com

Platform Support: support@platform.com
Platform Information Development: doc@platform.com

Copyright © 1994-2006 Platform Computing Corporation. All rights reserved.