1 / 8

Organizational Notes

Organizational Notes. D. Petravick (FNAL) O. Barring (CERN). What are the Goals? Proposal:. Increased coordination and coherence through mutual awareness and consensus , but not control.

mada
Download Presentation

Organizational Notes

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. Organizational Notes D. Petravick (FNAL) O. Barring (CERN)

  2. What are the Goals? Proposal: • Increased coordination and coherence through mutual awareness and consensus , but not control. • Support world-wide HEP by positioning facility storage systems to interact “directly” with each other will fewer interoperation barriers. • Identification and enumeration of grid and de-facto standards • Touches on technical area already mentioned. • Present component and future component.

  3. Today’s goals State a vision and see it institutions want to participate. Agree on short term organizational work. Show some material about places where any work might be presented/we might gather.

  4. Self-organization. • Electronic:Mailing list • hep-forum-mss@cern.ch • Organizational Meeting (somewhere/some venue) • Ad-hoc? • Next HEPIX • Next GGF

  5. “Collaborative” meetings(1) • Face to face meetings, possibly with video conferencing support. • What seems to be out there: • HEPIX/adjacency • GGF/HEP research group. • Self-sponsored, possibly with opportunistic adjacency. • Adjacency could sometimes happen with above fora.

  6. Collaborative Meeting(2) • Considerations: • Chance to interact within the group. • Chance to be stimulated by others outside the group. • Cost v.s. value tradeoff. • Present v.s. future.

  7. GGF As a Forum HENP application working group, under the Applications Ares: Means: (draft, from Area Director’s Sept Memo) Plan workshops 1-3 times/year Liaison between application and Grid community Represent the mainstream of the application community Feedback deployment experience to respective domains. Work on case studies documents, and application profiles documents Document projects activity is evident “GridForge” Continuous re-chartering every 2 years. Suggest new general area of study Barred: take a parochial activity and call it “grid”

  8. GGF as our primary fora No point if it cannot be well-attended by active members. Need to deliver documents in the GGF framework. Can do other work out-of-bounds. Need consensus that this fora is. attended by hands-on (development) people. Value: More widely attended, more future oriented. More expensive than, say HEPIX. cannot exclude active sites.

More Related