...
Rather than a single repository view, this will probably be multiple views that are configured to show a particular type of data bean(s) coming from a content provider. The content provider would get the data required from the configured tupelo context(s). For example, we will need a "Data Dataset Repository View" that shows all datasets (e.g. input/output datasets) and a way to manipulate them (e.g. add tags, annotations, etc), "Workflow Repository View" that shows all imported workflows, "Scenario Repository View" that shows all saved scenarios, "Service Repository View" that shows defined RMI service endpoints for launching jobs, and a "Known Hosts View" for showing known hosts that can accept jobs. This seems like too much disparate information to display in a single view. In SAGE and all derived products, a repository is going to be used for storing information that must be persisted and includes input data, output data, saved scenarios, workflows, etcAll Repository views will descend from BardFrameView since the BardFrame will be required to get the data required for each view.
Functional Requirements
- Import datasets that will be used as input to HPC workflows such as Mesh files, input files (e.g. mach number, poisson ratio, etc)
- Store output datasets from workflow runs, some workflows will be parameterized and have multiple outputs
- Store scenarios
- Store defined RMI services
- Store known-hosts
- Store workflow xml files (Ogrescript)
- Other functionality?
Repositories A critical requirement is that repositories can be both remote and local and users might use more than one simultaneously. Input data for workflows that is managed by Tupelo will need to move from the users machine to a location that the HPC machine can access. Datasets should also be returned to the users scenario or made available to it.
Known Host View
This view lists information about the HPC hosts such as environment settings, user information for the host (username, user home, etc), host operating system, node properties, etc.
...