Current solution
It looks like (from user's perspective) we miss simplified way of choosing "dressed" Kepler and workflow that will be used to launch ETS. In fact, the same sort of issues will affect Python based workflows.
...
all these components make user based environment.In order to use it, user will.
Main goal
To provide to the user a mechanism that:
- allows to run ETS workflow via ETS GUI
- automatically and transparently updates all ETS components
Assumptions
- User sets up and runs ETS via ETS GUI only
Module ets
Module ets configures user working environment by loading consistent set of libraries that were used to build particular version of ETS.
It internally
- loads module itmenv
- sets particular release of ETS actors
- sets particular release of ETS workflow (ETS.xml)
Script launch_ets.sh
This script
- checks if new versions of ETS environment are available
- in case a new version was released, allows the user to decide is local installation should be updated
- if YES - automatically updates local user installation of ETS environment
Use cases:
Use-case 1 -
...
Running existing installation of ETS
1) Precondition - first run or no ETS versions released since last run
2) Setting ETS environment and launching ETS
| Code Block |
|---|
# 1. log in to machine
# 2. initialise environment
> module load ets_workflow
# 3. run the autoGui
> launch_ets.sh |
autoGui is started, user can use his version of ETS with the default workflow loaded by environment.
Use-case 2 -
...
Running already installed version of ETS
...
(even if new version was released)
1) Precondition - ETS environment updated
In this scenario, system was upgraded and new release of tools was installed
...
| Info |
|---|
With current layout of
|
2) Setting ETS environment and launching ETS
| Code Block |
|---|
# 1. log in to machine
# 2. initialise environment
> module load ets_workflow
# 3. run the autoGui
> launch_ets.sh
There is a new release of Kepler. Do you want to upgrade [Y/N]?: N |
User presses N and currently installed version of autoGui and current version of Kepler are environment (Kepler, set of ETS actors, and workflow file) is used. No changes inside user's settings are done.
Use-case 3 -
...
Running ETS (automatic update of
...
ETS installation)
1) Precondition - ETS environment updated
In this scenario, system was upgraded and new release of tools was installed
...
| Info |
|---|
With current layout of
|
2) Setting ETS environment and launching ETS
| Code Block |
|---|
# 1. log in to machine
# 2. initialise environment
> module load ets_workflow
# 3. run the autoGui
> launch_ets.sh
There is a new release of Kepler. Do you want to upgrade [Y/N]?: Y |
...