Skip to content
Snippets Groups Projects
Unverified Commit 5a8052cc authored by AJRubio-Montero's avatar AJRubio-Montero Committed by GitHub
Browse files

Update README.md

parent 47b8d76a
No related branches found
No related tags found
No related merge requests found
...@@ -57,7 +57,7 @@ established. For this purpose, onedataSim includes two main programs: ...@@ -57,7 +57,7 @@ established. For this purpose, onedataSim includes two main programs:
[OneData](https://github.com/onedata); [OneData](https://github.com/onedata);
- makes standardised metadata for every inputs and results and includes them - makes standardised metadata for every inputs and results and includes them
as extended attributes in OneData filesystem. as extended attributes in OneData filesystem.
**``do_showers_onedata.py``** that: 2. **``do_showers_onedata.py``** that:
- executes analysis as ``do_showers.sh`` does. - executes analysis as ``do_showers.sh`` does.
- caches the selected simulation to be analisyed in local from the official - caches the selected simulation to be analisyed in local from the official
[LAGO repository](https://datahub.egi.eu) and then stores again the results [LAGO repository](https://datahub.egi.eu) and then stores again the results
...@@ -84,7 +84,6 @@ simulations. ...@@ -84,7 +84,6 @@ simulations.
[LAGO Virtual Organisation](https://lagoproject.github.io/DMP/docs/howtos/how_to_join_LAGO_VO/) [LAGO Virtual Organisation](https://lagoproject.github.io/DMP/docs/howtos/how_to_join_LAGO_VO/)
to obtain a OneData personal to obtain a OneData personal
[token.](https://lagoproject.github.io/DMP/docs/howtos/how_to_login_into_OneData/). [token.](https://lagoproject.github.io/DMP/docs/howtos/how_to_login_into_OneData/).
2. Had [Docker](https://www.docker.com/) 2. Had [Docker](https://www.docker.com/)
(or [Singularity](https://singularity.lbl.gov/) (or [Singularity](https://singularity.lbl.gov/)
or [udocker](https://pypi.org/project/udocker/)) or [udocker](https://pypi.org/project/udocker/))
...@@ -99,6 +98,7 @@ On linux, the recommended way is to remove all docker packages included by ...@@ -99,6 +98,7 @@ On linux, the recommended way is to remove all docker packages included by
default in your distro and to make use of Docker repositories. default in your distro and to make use of Docker repositories.
For example, for a old Debian based distribution such as Ubuntu: For example, for a old Debian based distribution such as Ubuntu:
```sh ```sh
sudo apt-get remove docker wmdocker docker-registry [...etc...] sudo apt-get remove docker wmdocker docker-registry [...etc...]
curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add - curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
...@@ -182,14 +182,11 @@ sudo docker run --privileged -e ONECLIENT_ACCESS_TOKEN=$TOKEN \ ...@@ -182,14 +182,11 @@ sudo docker run --privileged -e ONECLIENT_ACCESS_TOKEN=$TOKEN \
### Running simulations (generating S0 data) ### Running simulations (generating S0 data)
1. Export credentials: 1. Export credentials:
```sh ```sh
export TOKEN="MDAxY...LAo" export TOKEN="MDAxY...LAo"
export ONEPROVIDER="ceta-ciemat-01.datahub.egi.eu" export ONEPROVIDER="ceta-ciemat-01.datahub.egi.eu"
``` ```
2. Showing parameters: 2. Showing parameters:
```sh ```sh
sudo docker run --privileged -e ONECLIENT_ACCESS_TOKEN=$TOKEN \ sudo docker run --privileged -e ONECLIENT_ACCESS_TOKEN=$TOKEN \
-e ONECLIENT_PROVIDER_HOST=$ONEPROVIDER \ -e ONECLIENT_PROVIDER_HOST=$ONEPROVIDER \
...@@ -286,7 +283,6 @@ You can access to head node through SSH, using ``cloudadm`` account, but then ...@@ -286,7 +283,6 @@ You can access to head node through SSH, using ``cloudadm`` account, but then
you can gain root privileges with ``sudo``. Slurm and a directory shared by NFS you can gain root privileges with ``sudo``. Slurm and a directory shared by NFS
are already configured (/home), but some configruation has to be done: to share are already configured (/home), but some configruation has to be done: to share
the users' directories and to install spackages needed for Docker: the users' directories and to install spackages needed for Docker:
```sh ```sh
sudo mkdir /home/cloudadm sudo mkdir /home/cloudadm
sudo chown cloudadm /home/cloudadm sudo chown cloudadm /home/cloudadm
...@@ -344,16 +340,18 @@ You must indicate the BASE_OS parameter if you want creating S0 or S2 images: ...@@ -344,16 +340,18 @@ You must indicate the BASE_OS parameter if you want creating S0 or S2 images:
sudo docker build --build-arg BASE_OS="lagocollaboration/lago-corsika:77402" \ sudo docker build --build-arg BASE_OS="lagocollaboration/lago-corsika:77402" \
-t onedatasim-s1:local-test https://github.com/lagoproject/onedatasim.git -t onedatasim-s1:local-test https://github.com/lagoproject/onedatasim.git
``` ```
```sh ```sh
sudo docker build -t onedatasim-s1:local-test https://github.com/lagoproject/onedatasim.git sudo docker build -t onedatasim-s1:local-test https://github.com/lagoproject/onedatasim.git
``` ```
```sh ```sh
sudo docker build --build-arg BASE_OS="lagocollaboration/geant4:TBD" \ sudo docker build --build-arg BASE_OS="lagocollaboration/geant4:TBD" \
-t onedatasim-s2:local-test https://github.com/lagoproject/onedatasim.git -t onedatasim-s2:local-test https://github.com/lagoproject/onedatasim.git
``` ```
#### Example: building ``onedatasim-s0`` from featured branches #### Example: building ``onedatasim-s0`` from featured branches
If you have the newer releases of *git* installed in your machine, you can build If you have the newer releases of *git* installed in your machine, you can build
the container with one command. Note that afther the *.git* link, the container with one command. Note that afther the *.git* link,
there hare an '#' followed of again the ONEDATASIM_BRANCH name. there hare an '#' followed of again the ONEDATASIM_BRANCH name.
...@@ -383,7 +381,7 @@ a local directory inside the container the with the parameter ...@@ -383,7 +381,7 @@ a local directory inside the container the with the parameter
onedataSim samples geant4-dev onedataSim samples geant4-dev
``` ```
2. Explore OneData repository within the container. 2. Explore OneData repository within the container.
Firstly test if the repository is already mounted and force mount if necessary: Firstly test if the repository is already mounted and force mount if necessary:
```sh ```sh
[root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu [root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu
[root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu/LAGOsim [root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu/LAGOsim
...@@ -396,7 +394,7 @@ Getting configuration... ...@@ -396,7 +394,7 @@ Getting configuration...
Oneclient has been successfully mounted in '/mnt/datahub.egi.eu'. Oneclient has been successfully mounted in '/mnt/datahub.egi.eu'.
``` ```
Then, you can explore the repository: Then, you can explore the repository:
```sh ```sh
[root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu [root@c42dc622f7eb run]# ls -alh /mnt/datahub.egi.eu
total 0 total 0
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment