Comments on ogsa platform document draft 2
This presentation is the property of its rightful owner.
Sponsored Links
1 / 10

Comments on OGSA platform document draft-2 PowerPoint PPT Presentation


  • 96 Views
  • Uploaded on
  • Presentation posted in: General

GGF7 OGSA-WG. Comments on OGSA platform document draft-2. 03/06/2003 Andreas Savva, Ph.D. Hiro Kishimoto, Ph.D. Fujitsu. Major comments. Services not Interfaces “OGSA Platform interface” -> “OGSA platform service” Profile Need a concrete definition Missing functionalities

Download Presentation

Comments on OGSA platform document draft-2

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Comments on ogsa platform document draft 2

GGF7 OGSA-WG

Comments onOGSA platform document draft-2

03/06/2003

Andreas Savva, Ph.D.

Hiro Kishimoto, Ph.D.

Fujitsu


Major comments

Major comments

  • Services not Interfaces

    • “OGSA Platform interface” -> “OGSA platform service”

  • Profile

    • Need a concrete definition

  • Missing functionalities

  • Service Domain, Service Collection, Service Group

    • “Service domain” -> “service collection”

  • CRM

    • Real & logical are asymmetrical

    • granularity

  • Missing services

  • Message, events, log, and trace

    • Need re-organization w.r.t. user’s point of view

    • Job and task queueing is supported by message?


Services not interfaces

Services not Interfaces

  • Title of “§4.2” on page 12

  • OGSA Platform focus on services

  • Interfaces defined by subgroups

  • “OGSA platform service” or “OGSA core service”


Profile

Profile

  • Profiles are good idea, but

  • Need a concrete definition since it is used inconsistent way

  • Add “common service profile” dashed line in Figure 1 on page 9

  • The first sentence says profile and binding are part of OGSA platform. But the last sentence says not (page 4)

  • “Protocol binding”, “hosting environment”, and “domain-specific service” are NOT profile. Instead, they may be involved in some profile (page 10)


Platform shaded and profiles dashed lines

Platform (shaded) and profiles (dashed lines)


Missing functionalities 3 2

Missing functionalities (§3.2)

  • Scheduling of service tasks

  • Long recognized as an important capability for any information processing system, scheduling becomes extremely important and difficult for distributed Grid systems.

  • Load Balancing

  • In many applications it is necessary to make sure make sure deadlines are met, or resources are used uniformly. These are both forms of load balancing that must be made possible by the underlying infrastructure.

  • Pricing


Service domain collection group

Service Domain, Collection, Group

  • “Service domain” -> “service collection” (§4.2, §5.2)

    • At November F2F meeting, OGSA-WG had a long discussion on “service domain” and conclusion was “since it is syntactic collection not semantics, it should be called “service collection”

  • Service Group defined in OGSI (syntax)

  • Is Service Collection definition syntactic or semantic?


Comments on ogsa platform document draft 2

CRM

  • Real and logical

    • What is real and logical.

    • Strictly speaking, they are not symmetrical.

  • Granularity

    • Node is CRM. But interface adaptor, disk, and IP address is not CRM instance.

    • They are elements or SDEs of the CRM.


Missing services 3 2

Missing services (§3.2)

  • Resource Services

    • Provide an interface to a resource, such as a cpu, disk, network, management tools, etc.

    • This is not a service but The Common Resource Model (CRM) ?

  • Reservation and scheduling services

    • Reservation Services provide the mechanism to make resources reservation at a particular time duration

    • Scheduling Services provide the mechanism to scheduling tasks according to their priorities

  • Deployment services

    • Deploy necessary software (OS, middleware, application) and data into hosting environment


Message events log and trace

Message, events, log, and trace

  • Page 12 is poor structure

    • Should be separate two.

      • Production use messages used by applications and middleware

      • Monitoring and problem diagnostic

  • Job and task queueing is supported by message

    • It is true but “implementation level” or “building block”


  • Login