Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
gga_load_data
Manage
Activity
Members
Labels
Plan
Issues
12
Issue boards
Milestones
Wiki
Code
Merge requests
5
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
abims
e-infra
gga_load_data
Commits
48f5e18a
Commit
48f5e18a
authored
3 years ago
by
Loraine Gueguen
Browse files
Options
Downloads
Patches
Plain Diff
Move requirements to the top
parent
6528055a
No related branches found
No related tags found
1 merge request
!1
Release 1.0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+19
-17
19 additions, 17 deletions
README.md
with
19 additions
and
17 deletions
README.md
+
19
−
17
View file @
48f5e18a
...
@@ -8,6 +8,14 @@ See `examples/example.yml` for an example of what information can be described a
...
@@ -8,6 +8,14 @@ See `examples/example.yml` for an example of what information can be described a
Each GGA environment is deployed at
[
https://hostname/sp/genus_species/
](
https://hostname/sp/genus_species/
)
.
Each GGA environment is deployed at
[
https://hostname/sp/genus_species/
](
https://hostname/sp/genus_species/
)
.
## Requirements
To run the gga_load_data tools, Python 3.6 and the packages listed in
[
requirements.txt
](
./requirements.txt
)
are required.
To deploy the GGA Docker services, one or multiple hosts machines are required with
[
Docker
](
https://docs.docker.com/engine/install/
)
installed,
and a
[
swarm
](
https://docs.docker.com/engine/swarm/swarm-tutorial
)
(
for
cluster management and orchestration).
## Reverse proxy and authentication
## Reverse proxy and authentication
Traefik is a reverse proxy which allows to direct HTTP traffic to various Docker Swarm services.
Traefik is a reverse proxy which allows to direct HTTP traffic to various Docker Swarm services.
...
@@ -71,6 +79,17 @@ $ python3 /path/to/repo/gga_load_data.py input_file.yml -c/--config config_file
...
@@ -71,6 +79,17 @@ $ python3 /path/to/repo/gga_load_data.py input_file.yml -c/--config config_file
--main-directory
$PATH
(
Path where to access stacks
;
default
=
current directory
)
--main-directory
$PATH
(
Path where to access stacks
;
default
=
current directory
)
```
```
## Limitations
The stacks deployment and the data loading into Galaxy should be run separately and only once the Galaxy service is ready.
The
`gga_load_data.py`
script check that the Galaxy service is ready before loading the data and exit with a notification if it is not.
The status of the Galaxy service can be checked manually with
`$ docker service logs -f genus_species_galaxy`
or
`./serexec genus_species_galaxy supervisorctl status`
.
When deploying the stack of services, the Galaxy service can take a long time to be ready, because of the data persistence.
In development mode only, this can be disabled by setting the variable
`persist_galaxy_data`
to
`False`
in the config file.
## Directory tree:
## Directory tree:
For every input organism, a dedicated directory is created with
`gga_get_data.py`
. The script creates this directory and all subdirectories required.
For every input organism, a dedicated directory is created with
`gga_get_data.py`
. The script creates this directory and all subdirectories required.
...
@@ -126,23 +145,6 @@ Directory tree structure:
...
@@ -126,23 +145,6 @@ Directory tree structure:
```
```
## Current limitations
The stacks deployment and the data loading into Galaxy should be run separately and only once the Galaxy service is ready.
The
`gga_load_data.py`
script check that the Galaxy service is ready before loading the data and exit with a notification if it is not.
The status of the Galaxy service can be checked manually with
`$ docker service logs -f genus_species_galaxy`
or
`./serexec genus_species_galaxy supervisorctl status`
.
When deploying the stack of services, the Galaxy service can take a long time to be ready, because of the data persistence.
In development mode only, this can be disabled by setting the variable
`persist_galaxy_data`
to
`False`
in the config file.
## Requirements
Requires Python 3.6
[
requirements.txt
](
./requirements.txt
)
## License
## License
[
BSD 3-Clause
](
./LICENSE
)
[
BSD 3-Clause
](
./LICENSE
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment