html5-img
1 / 7

SRM + GLUE

SRM + GLUE. Comments and Observations. Arie Shoshani meeting held at CERN December, 2002. Purpose of GLUE. Provide information on services of SRM Capacity Total by types (permanent, durable, volatile) Type of service Get, put, copy, multi-file requests, status, call_back Policies

zamir
Download Presentation

SRM + GLUE

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SRM + GLUE Comments and Observations Arie Shoshani meeting held at CERN December, 2002

  2. Purpose of GLUE • Provide information on services of SRM • Capacity • Total by types (permanent, durable, volatile) • Type of service • Get, put, copy, multi-file requests, status, call_back • Policies • MaxFileSize, MaxPinDuration, MaxQuotaSize, Lifetime per file type • Directory service • ls, mkdir, etc. • Provide dynamic information for planning • Current space available • Current system load • Current MBs left in my space (by type)

  3. GLUE + SRM terminology • Storage Service • SRM: SRM service • GLUE confuse SRMs and MSSs – call both Storage Service • Storage Space • SRM: Space • Access protocol • SRM: Transfer Protocol • State (dynamic properties) • e.g. CurrentIOLoad, AvailableSpace, MaxIOCapacity • SRM: ??? • SRM: requestStatus, FilesStatus, filesMetadata • Add in SRM: status on space by type

  4. GLUE + SRM terminology (more) • File System • Associated with Storage Space • SRM: not applicable? • Directory • Associated with Storage Space • SRM: per user, per space-type • Policy • Many: MaxFileSize, MinFileSize, ,MaxData, MaxNumFiles, MaxPinDuration, MaxQuotaSize, FileLifetime • SRM: only getProtocols • File • Lots of date info: DateCreated, LastModified, LastAccessed, Latency, LifeTime, Path • SRM: lots of other info: owner, group, fileType, checkSum, …

  5. Conclusions • Some concepts are similar • Storage space, files • File types: V, D, P • Policies • Access Protocol • Some concepts are not • Storage Library ? • Multiple File Systems for each Storage Space • In srm: file system uniform by type, by user • Directory associated with Storage Space • In srm: directory by type, by user

  6. Conclusions (more) • Need to separate • Static properties – goes to Info-service • SRM are active: notify Info-service of static properties when they are initiated, terminated or updated • Dynamic properties – used by planner • SRMs are passive: interrogated on a per-need basis • Open: should SRMs advertise dynamic properties? • Open: Should SRMs accept advisory_requests? • Need to synchronize SRMs and GLUE • Does GLUE need the additional concepts (see previous page)? • GLUE needs a lot more on “type of service” • SRM and GLUE need a lot more on dynamic properties

  7. Conclusions (more) • Any reason SRM and GLUE should not maintain identical information? • Both should keep identical static and dynamic storage properties, policies, access protocols • SRM keeps dynamic properties per request, GLUE needs only dynamic summary information • Setup a one-day meeting to hammer outa common terminology, and what is expected that SRM

More Related