- The web interface is something that we are actively developing these months, so while there is
reana-uicomponent where you could see some mock-ups, it is better to wait for a more complete "live" version coming in February. We have user logins connected to GitLab for easy Continuous Integration use cases, we are working on workflow list and workflow run details visualisation. The important design principle is doing heavy stuff as React components, so that the UI could be eventually plugged into JupyterLab notebooks, so that one could easily launch workflows from within notebooks and monitor progress, for example.
Our main computing facility is the NERSC Cori machine at Berkeley National Lab (which runs SLURM for compute nodes, shifter for containers, and a separate k8 service called Spin), has anyone already successfully setup REANA there? And if not, any recommendations for how to go about it?
(myreana) [16:52]:~/myreana $ reana-client create -w myanalysis
Usage: reana-client create [OPTIONS]
Try "reana-client create --help" for help.
Error: Invalid value for "-f" / "--file": Path "./reana.yaml" does not exist.
(myreana) [10:10]:~/myreana/reana-demo-helloworld $ ls
code data environments LICENSE README.rst reana-cwl-htcondorcern.yaml reana-cwl.yaml reana-htcondorcern.yaml reana-yadage.yaml reana.yaml workflow
(myreana) [10:10]:~/myreana/reana-demo-helloworld $ reana-client create -n myanalysis
Workflow could not be created:
Extra data: line 1 column 5 - line 2 column 1 (char 4 - 19)
from the docs: https://reana-cluster.readthedocs.io/en/latest/gettingstarted.html
so I run that:
[root@river-c001 reana]# kubectl exec -ti $(kubectl get pods -l=app=server -o jsonpath='{.items[0].metadata.name}') -- flask users create -e lincolnb@uchicago.edu --admin-access-token $REANA_ACCESS_TOKEN
Defaulting container name to server.
Use 'kubectl describe pod/server-8c55d4649-j25f8 -n default' to see all of the containers in this pod.
Usage: flask users create [OPTIONS] EMAIL
Try "flask users create --help" for help.
Error: no such option: -e
command terminated with exit code 2
indeed running help gives me:
[root@river-c001 reana]# kubectl exec -ti $(kubectl get pods -l=app=server -o jsonpath='{.items[0].metadata.name}') -- flask users create --help
Defaulting container name to server.
Use 'kubectl describe pod/server-8c55d4649-j25f8 -n default' to see all of the containers in this pod.
Usage: flask users create [OPTIONS] EMAIL
Create a user.
Options:
--password TEXT
-a, --active
--help Show this message and exit.
reana-cluster ping and reana-client create -n blah work just fine
flask create -e johndoes@example.org, we have added SSO login (via Invenio digital library framework) and now the syntax is different, please see the example at https://github.com/reanahub/reana-server/blob/master/scripts/setup
-e, just supply email address directly)
- to debug client-side toubles, you can increase logging level option via
-largument toreana-client, for examplereana-client -l DEBUG ping
Hi, I was looking at https://github.com/reanahub/reana-ui and was wondering if external contributions are accepted at this stage of the project?
I tried setting up the project but looks like the backend can’t be accessed outside the CERN network.
reana.cern.ch instance is currently only available inside the CERN network. One can install REANA on premises though, several organisations already did.)
