cloud-pipeline
cloud-pipeline copied to clipboard
epam
Cloud agnostic genomics analysis, scientific computation and storage platform
**Background** It possible situation, when some processes can become `< defunct >` in docker container of the run. That means, that when `launch.sh` will finish and exit such container will...
**Background** At the moment when a user is allowed to use `run as` feature with some service account, the user can use it for any available pipeline or tool. This...
**Background** Let's introduce mechanism of the monitoring, notification and (if possible) regulation of usage of network by pods. This mechanism should be similar to the one we have for `IDLE...
**Approach** Based on #3588 results let's implement a way to specify such directory as an input for `pipectl install` command. - If such option (-pc/--point-in-time-configuration) was provided, `install` command should...
**Background** Event sourcing is a really great mechanism for asynchronous communication between services. In Cloud-Pipeline we have at least one (but, certainly, it would be much more in a future)...
**Background** Let's implement optimization of the `git-sync` daemon. Currently it makes a lot of `/metadata/load` calls to check if we need to refresh user ssh keys. Most of the time...
**Background** Sometimes its can be very beneficial to be able to persist setup and all internal configuration (Application version, cp-global-config map, API system preferences, docker images) from existing environment. Later...