Skip to content

Commit b1217f9

Browse files
authored
Merge pull request #39 from ggabernet/dev
improve deNBI cloud docs
2 parents ddf3763 + b2845a6 commit b1217f9

File tree

5 files changed

+45
-19
lines changed

5 files changed

+45
-19
lines changed

docs/markdown/clusters/denbi_cloud.md

Lines changed: 44 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -2,27 +2,45 @@
22

33
## Access to a project
44

5-
Either request a project to [deNBI cloud](https://cloud.denbi.de) or ask someone at QBiC if they can create an instance for you in one of their projects.
5+
Either request a new project to [deNBI cloud](https://cloud.denbi.de), or ask the RDDS team or team leader if you can create an instance in one of their projects. The info on how to apply for a new project is collected on the [deNBI wiki](https://cloud.denbi.de/wiki/portal/allocation/). We recommend you to apply for an `OpenStack Project` so you can configure your own settings and instances.
66

7-
## Documentation
7+
You should register with your University account to obtain an ELIXIR ID that will allow you to log into deNBI cloud, and once you have an account there, you can be added to an existing project. The instructions on how to register are found [here](https://cloud.denbi.de/wiki/registration/).
8+
9+
> Important! After registering it is necessary to send an email to the Tübingen cloud administrator, so that they activate your account.
10+
11+
## deNBI official documentation
812

913
The documentation on how to create instances and other important things is collected on the [deNBI Tübingen page](https://cloud.denbi.de/wiki/Compute_Center/Tuebingen). This documentation is not perfect, though, and I found it useful to add a few more notes here.
1014

11-
## Create an instance
15+
## Creating an instance
16+
17+
1. Log into `cloud.denbi.de`, select your project, and log into the OpenStack web interface by clicking the green button `Log into Openstack`.
18+
19+
![Login openstack](./denbi_cloud_images/login_openstack.png)
20+
21+
2. You should then see the project overview board. This overview shows how many instances, and total CPUs, memory (GB), and Storage (GB) is still available for this project. If this is not enough for your needs, you can ask for access to another project or create a new project.
22+
23+
![Openstack project overview](./denbi_cloud_images/project_overview_board.png)
24+
25+
3. To create a new instance, go to the left menu: Compute -> Instances -> Launch Instance button. This will prompt a step by step guide:
26+
* Details: add an Instance Name
27+
* Source: select either "Image" for a generic image e.g. CentOS operating system, or "Instance Snapshot" for creating an Instance from a previous snapshot. For running `Nextflow` workflows, you can use the Instance Snapshot `nextflow-singularity` which already has `java-jdk12`, `Nextflow`, `Singularity` and `Docker` installed (check if Nextflow should be updated with `nextflow self-update`).
28+
* Flavour: select the instance flavour (number of CPUs and RAM).
29+
* Networks: select `denbi_uni_tuebingen_external` network.
30+
* Network Ports: leave empty.
31+
* Security Groups: add `default` AND `external_access`.
32+
* Key Pair: add a new key pair or select yours. Only one Key Pair is allowed per instance and if you lose the private key you will not be able to access the instance any more! If you choose to create a new keypair, make sure to copy the private key that is displayed to your computer, and store it under the `~/.ssh/` directory. You will also need to adapt the rights of this file so that only you (the computer main user) can read this file. You can do that in the command line by:
1233

13-
Go to the menu: Compute -> Instances -> Launch Instance button.
34+
```bash
35+
chmod 600 <your_private_ssh_key>
36+
```
1437

15-
* Details: add an Instance Name
16-
* Source: select either "Image" for a generic image e.g. CentOS operating system, or "Instance Snapshot" for creating an Instance from a previous snapshot. For running `Nextflow` workflows, you can use the Instance Snapshot `nextflow-singularity` which already has `java-jdk12`, `Nextflow`, `Singularity` and `Docker` installed (check if Nextflow should be updated with `nextflow self-update`).
17-
* Flavour: select the instance flavour (number of CPUs and RAM).
18-
* Networks: select `denbi_uni_tuebingen_external` network.
19-
* Network Ports: leave empty.
20-
* Security Groups: add `default` AND `external_access`.
21-
* Key Pair: add a new key pair or select yours. Only one Key Pair is allowed per instance and if you lose the private key you will not be able to access the instance any more!
22-
* Rest of fields: leave default.
23-
* Press on `create instance`
38+
* Rest of fields: leave default.
39+
* Press on `create instance`
2440

25-
You should now see your image being Spawn on the Instance dashboard. It might take several minutes to spawn, especially if created from an Instance Snapshot.
41+
You should now see your image being Spawn on the **Instance dashboard**. It might take several minutes to spawn, especially if created from an Instance Snapshot. In this dashboard you will be able to see the instance IP and the operating system, which you will need to log into the instance via `SSH`.
42+
43+
![instance board](./denbi_cloud_images/instance_IP_username.png)
2644

2745
## SSH to an instance
2846

@@ -32,7 +50,7 @@ To ssh to an instance, you need the private key of the Key Pair that was used to
3250
ssh -i /path/to/private/ssh-key <username>@<IP>
3351
```
3452

35-
The username is the name of the operating system that was used in the image. For the `nextflow-singularity` instance snapshot, it is `centos`.
53+
The username is the name of the operating system that was used in the image. For the `nextflow-singularity` instance snapshot, it is `centos`. For an Ubuntu-based instance, that will be `ubuntu`.
3654

3755
```bash
3856
ssh -i /path/to/private/ssh-key centos@<IP>
@@ -65,14 +83,16 @@ In order to use an external cinder volume, you need to first create one on the O
6583
6684
## Setting-up nextflow, singularity, docker
6785
86+
If you haven't created an instance based on an Image that already has java, Nextflow and singularity or docker installed (e.g. the `nextflow-singularity` image), you will need to install this software.
87+
6888
* Installation instructions for [Java](https://phoenixnap.com/kb/install-java-on-centos) on CentOS. For Nextflow you will need Java jdk <= 11.
6989
* Instructions for installing Nextflow can be found [here](https://www.nextflow.io/docs/latest/getstarted.html)
7090
* On CentOS, singularity can be installed with the package manager `yum`. First install the [dependencies](https://sylabs.io/guides/3.0/user-guide/installation.html#before-you-begin) and then head straight to the [CentOS section](https://sylabs.io/guides/3.0/user-guide/installation.html#install-the-centos-rhel-package-using-yum)
7191
* For installing docker, please follow the [instructions](https://docs.docker.com/engine/install/centos/) and the [post-installation steps](https://docs.docker.com/engine/install/linux-postinstall/)
7292
7393
## Running Nextflow pipelines on deNBI
7494
75-
Running Nextflow pipelines on deNBI VMs is like running them locally on your computer. When launching a pipeline, make sure to define the maximum resources available at your instance, either with the appropriate parameters or with a custom config file:
95+
Running Nextflow pipelines on deNBI VMs is like running them locally on your computer. When launching a pipeline, make sure to define the maximum resources available at your instance, either with the appropriate parameters or with a custom config file (e.g. in a file called `custom.config`):
7696
7797
```console
7898
params {
@@ -81,3 +101,11 @@ params {
81101
max_time = 960.h
82102
}
83103
```
104+
105+
Then run the pipeline with the `singularity` or `docker` profile, whatever container system you prefer and have installed in the instance, and by providing this config file. The best is to start the run inside a screen session. For example:
106+
107+
```bash
108+
screen -S newscreen
109+
nextflow pull nf-core/rnaseq -r 3.4
110+
nextflow run nf-core/rnaseq -r 3.4 -profile singularity,test -c custom.config
111+
```
54.1 KB
Loading
55.6 KB
Loading
69.5 KB
Loading

docs/markdown/pipelines/debugging.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -131,9 +131,7 @@ This error occurs because the `scratch` space on the nodes for staging files the
131131
132132
```bash
133133
process {
134-
withName:MarkDuplicates {
135-
scratch = '/sfs/7/workspace/ws/my-ws-name/tmp'
136-
}
134+
scratch = false
137135
}
138136
```
139137

0 commit comments

Comments
 (0)