Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
OnedataSim
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
LAGO
Software
OnedataSim
Commits
47b8d76a
Unverified
Commit
47b8d76a
authored
3 years ago
by
AJRubio-Montero
Committed by
GitHub
3 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
b7923006
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+10
-10
10 additions, 10 deletions
README.md
with
10 additions
and
10 deletions
README.md
+
10
−
10
View file @
47b8d76a
...
...
@@ -57,7 +57,7 @@ established. For this purpose, onedataSim includes two main programs:
[
OneData
](
https://github.com/onedata
)
;
-
makes standardised metadata for every inputs and results and includes them
as extended attributes in OneData filesystem.
2.
**``do_showers_onedata.py``**
that:
**``do_showers_onedata.py``**
that:
-
executes analysis as
``do_showers.sh``
does.
-
caches the selected simulation to be analisyed in local from the official
[
LAGO repository
](
https://datahub.egi.eu
)
and then stores again the results
...
...
@@ -275,12 +275,12 @@ sudo docker run --privileged -e ONECLIENT_ACCESS_TOKEN=$TOKEN \
### Executing on clusters instantiated by oneself in IaaS cloud providers
1.
First you has to create and configure a cluster in the cloud:
-
Using the EOSC public cloud, that enables the pre-configuration of Slurm
and other schedulers (Kubernetes).
[
See EOSC-Synergy training for LAGO
](
https://moodle.learn.eosc-synergy.eu/course/view.php?id=16
)
-
Using commercial public clouds (Amazon, Azure, Google, etc).
-
Using private clouds (institutional orchestators as OpenStack,
OpenNebula, XenServer, VMware, etc).
-
Using the EOSC public cloud, that enables the pre-configuration of Slurm
and other schedulers (Kubernetes).
[
See EOSC-Synergy training for LAGO
](
https://moodle.learn.eosc-synergy.eu/course/view.php?id=16
)
-
Using commercial public clouds (Amazon, Azure, Google, etc).
-
Using private clouds (institutional orchestators as OpenStack,
OpenNebula, XenServer, VMware, etc).
2.
Example for an Slurm instantiated on EOSC resources (pre-configured by IM):
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
...
...
@@ -353,10 +353,10 @@ sudo docker build --build-arg BASE_OS="lagocollaboration/geant4:TBD" \
```
#### Example: building ``onedatasim-s0`` from featured branches
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,
there hare an
'#' followed of again the ONEDATASIM_BRANCH name.
the container with one command. Note that afther the
*.git*
link,
there hare an
'#' followed of again the ONEDATASIM_BRANCH name.
```
sh
sudo
docker build
--build-arg
ONEDATASIM_BRANCH
=
"dev-ajrubio-montero"
\
...
...
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