...
Independent Python/Kepler actor installations
In this scenario I assume complete separation of Kepler and Python. FC2K should allow choosing whether we want to generate actor for given workflow platform: Python, Kepler, something else in the future. Once platform is selected, FC2K generates source code and "Weighted Companion Cube" - one that contains all the native codes, libraries, etc. - for given platform.
Kepler
TODO: we have to decide whether we want to update the way of generation for Kepler or not
Python
I suggest moving towards Python packages that are self contained packages consisting of:
- python wrapper
- shared libraries
- standalone binary (MPI based execution)
- default parameters
Each package should be installed inside user's virtual environment - this way, it will be possible to provide users with any version of actor and Python workflow will be composed of loosely coupled actors.TBD (MICHAL)
One common installation of actor resources
...