Skip to content

ESGFCmip5Meetings|20111018

Jump to bottom Edit New page
Stephen Pascoe edited this page Apr 9, 2014 · 6 revisions
Wiki Reorganisation
This page has been classified for reorganisation. It has been given the category MOVE.
The content of this page will be revised and moved to one or more other pages in the new wiki structure.

October 18th, 2011

This meeting was a presentation of the P2P Node: Summary, architecture and future directions.

Dean - Introduce the ESGF P2P Node and recap the above agenda.

- Give a system overview:

* [ http://esgf.org/wiki/ESGF_Overview ](http://esgf.org/wiki/ESGF_Overview)

- Discuss the vision and how the project works.

* [ http://esgf.org/wiki/ESGF_Manifesto ](http://esgf.org/wiki/ESGF_Manifesto)

Luca - Functionality

- Interface groups (how we work)

* [ http://esgf.org/wiki/ESGFInterfaceGroups ](http://esgf.org/wiki/ESGFInterfaceGroups)

John - ESGF User Interface (administration, search & download)

Gavin - Releases & Components (the stack)

  • http://esgf.org/releases/

  • - Installation

    • http://esgf.org/wiki/Cmip5DataNode/InstallationProcedure http://rainbow.llnl.gov/dist/ http://esgf.org/esgf-installer-site/ - Roadmap http://esgf.org/wiki/RoadMap - Timelines

      • Sort term monthly release cycles, elongated after full standard functionality established) - Quick governance (more details deferred for another discussion)

      • Every project has a project leader with one or more work group initiatives

        • (Luca, John & Feiyi, Rachana & Neill, Bob, Estani, Stephen, Gavin, Sandro)

      • There is an ESGF Node coordinator that puts together the releases and helps coordinate overall testing (Gavin)

      • Project Leaders manager all project related activities and meet together with coordinator to create a release.

      • There is a director that expresses the overall direction and initiatives for the project a whole (Dean [et. al.]) - Repos are administered by the Project Leaders who may delegate to lieutenants as they choose... et. al. - It is encouraged that Repo forks should live at esgf.org, email coordinator for forks.

      • (overall flat org structure)

Key concepts: Collaboration with broad developer community. Merit based system of contribution. Delegated hierarchy. Ability to provide agile response to user community needs. Customizable "scale-out" architecture. Open standards where possible, community (working group) standards where needed.

Ex: Sandro and Gavin - visiting, working on Dashboard Zed and Estani work on installer Estani - visiting to work on deep storage "stager" project and download / replication. Stephen, Luca, Phil, Neill, Rachana - work on interoperable standards based security interface and infrastructure. Bob & Feiyi publisher collaboration and integration. etc....

Add a custom footer
Add a custom sidebar
Clone this wiki locally