...
- How to assure compatibility with current version of IMAS?
- Binaries are build for particular IMAS version
- If user switch IMAS version, version of resources should be also changed
- How to assure compatibility of Kepler or Python workflow with given set of actors
- Actor A could have different ports (API) in workflow version X and Y
- This is currently achieved by actor release procedure and maintenance of ETS workflow (release of ETS workflow)
- ETS workflow + visualisation scripts + Kepler release + actor release + autoGUI release make a package that works.
- Actor A could have different ports (API) in workflow version X and Y
- How to make libraries "discoverable" by both actors?
LD_LIBRARY_PATH?- absolute path to
libActor.so? - Any other mechanism?
- How to design layout of directories to address before-mentioned points?
Implementation - TBD
Layout of folders - TBD
...
Proposed solutions
Independent Python/Kepler actor installations
TBD (MICHAL)
One common installation of actor resources
Idea
- To keep all (common) actor resources for both: Python and Kepler actors in one place (directory)
- To allow switching between "workspaces" (user defined sets of actors)
- To load actor libraries only for current version of IMAS (if actor is IMAS dependent)
Layout of actor directory
TBD (the same as previously?)
IMAS Workspace
switching workspace
Kepler: rm target/* ? ant compile?