Skip to content

Roadmap: Development

Jump to bottom Edit New page
oweidner edited this page Jul 30, 2012 · 7 revisions

Overview

This is a rough outline of the envisioned roadmap for SAGA-Bliss development. Since SAGA-Bliss aims to be a community project, we would like to encourage anyone who's interested in SAGA-Bliss to comment on and contribute to this roadmap. This is probably best done via the developers mailing list: https://groups.google.com/forum/?fromgroups#!forum/bliss-dev.

We have roughly organized the roadmap into three milestones called tiers. Except for Tier 1 which is due September 2012, there are no dates associated with the milestones.

Tier 1 (Due: September 2012)

  • Implement Job API Package (Done)
  • Implement Resource API Package (Done)
  • Implement File API Package (Done)
  • Implement SSH Plug-In (Done)
  • Implement PBS Plug-In (Done)
  • Implement SGE Plug-In (Done)
  • Implement GSISSH Plug-In

Tier 2 (Due: TBD)

  • Production Feature: Implementation of the SAGA Advert Package along with a plug-in (probably based on Redis). Advert represents the coordination aspects of the SAGA API and is important for the development of SAGA-based distributed frameworks and application. Advert was one of the popular packages in SAGA C++, we expect it to be just as usable in our Python implementation.

  • Production Feature: Implementation of a Condor Plug-In. This is required for people who want to use SAGA-Bliss on Open Science Grid and other Condor-based grids. Condor doesn't allow remote job submission without having parts of the Condor-stack installed on the client machine -- we would like to circumvent that by implementing a 'remote submission mechanism' that tunnels Condor commands via SSH and GSISSH -- similar to the ssh+pbs:// and ssh+sge:// mechanism in the PBS and SGE plug-ins.

  • Experimental Feature: Implementation of the SAGA Monitoring API and see how feasible it is to integrate it with existing job plug-ins. To our knowledge, the monitoring API has never been implemented -- it would be interesting to explore how practical / difficult to implement it is.

  • Experimental Feature: Implementation of the SAGA Async API and see how feasible it is to integrate it with existing job / file plug-ins.

Tier 3 (Due: TBD)

  • Implement SAGA Messaging API
  • Globus GRAM / GridFTP / Globus online plug-ins
  • OCCI plug-in
  • BES plug-in
Add a custom footer
Add a custom sidebar
Clone this wiki locally