Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • impd-openVRE impd-openVRE
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IMPaCT-DataIMPaCT-Data
  • impd-openVREimpd-openVRE
  • Wiki
  • Home

Home · Changes

Page history
Updated Home (markdown) authored Oct 27, 2022 by lcodo's avatar lcodo
Hide whitespace changes
Inline Side-by-side
Home.md
View page @ 2d985391
......@@ -14,8 +14,17 @@
### What is openVRE
### Architecture
This figure shows an overview of the layout of the final computational infrastructure and how openVRE interacts with the different components:
The [main repository](https://github.com/inab/openVRE) contains the source code of openVRE, including the web front-end, which can be easily customizable to your project, and the core code, responsible of managing data, metadata, processing units (analyses and visualizers) and computational resources. This figure shows an overview of one of the possible layouts for a computational infrastructure based on openVRE:
![arch_1](https://github.com/inab/openVRE/raw/master/public/assets/layouts/layout/img/architecture%20openvre%20(1).png)
![arch_1](https://github.com/inab/openVRE/raw/master/public/assets/layouts/layout/img/wiki/architecture_overview.png)
The different components makes possible to provide the computational environment for an analysis or visualization tool initiated by a user at the VRE web interface. The petition is processed by one of the two schedulers available, PMES or SGE-oneflow. They both end up triggering the tool in the particular virtual machine where the selected tool is encapsulated (see bellow the differences between both enactors). In any case, resources are dynamically assigned based on user demands as the number of dedicated VMs is proportional to the number of job petitions, as long as cloud computational resources allow it. Those VMs have access to a number of data volume where input files are accessible, either private (coming from user's workspace) or public datasets are available, and where output files will be written.
Once job's petition reaches the VM, tool execution starts. In any case. tools are generally wrapped by the mg-tool API, that acts as intermediary agent between the MuGVRE and the tool code itself to uniformelly communicate with it. Thought the API, the application or pipelines is eventually executed.
![arch_2](https://github.com/inab/openVRE/raw/master/public/assets/layouts/layout/img/wiki/architecture_docker.png)
### Components
### Puggable resources
......
Clone repository

On this page

  • Home
  • Bring your own tool

  • Sidebar