nomad-FAIR issueshttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues2024-03-19T09:37:50Zhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1944Config does not allow string loglevel like "INFO" anymore2024-03-19T09:37:50ZMarkus ScheidgenConfig does not allow string loglevel like "INFO" anymoreMarkus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1812Scaffolding for the plugin example projects.2024-03-13T10:24:56ZMarkus ScheidgenScaffolding for the plugin example projects.We could add more features to the example plugin projects:
- [x] code style checks
- [ ] autoformatting checks and autoformatting pre-commit hooks (both opt-in)
- [x] linting
- [x] an empty mkdocs + github actions to deploy as gh-pages
...We could add more features to the example plugin projects:
- [x] code style checks
- [ ] autoformatting checks and autoformatting pre-commit hooks (both opt-in)
- [x] linting
- [x] an empty mkdocs + github actions to deploy as gh-pages
- [x] test coverage badge, pipeline badge
The mkdocs should include the theming/styling from the main project. We still need to figure out what should in the docs by default.
Some other ideas:
- maybe gh actions to build pypi package (is there something like a package/release registry in github?)
- maybe gh actions to build the docker file (gh does not have a docker resgistry? this would only make sense as opt-in where users define a registry to use)
The projects are :
https://github.com/nomad-coe/nomad-schema-plugin-example
https://github.com/nomad-coe/nomad-parser-plugin-example
@ladinesa is about to create a third one for normalizers
Just start with one project. Create PR there on github.Markus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1598The dev_python image cannot be used as a replacement for the production image2024-01-11T23:35:14ZMarkus ScheidgenThe dev_python image cannot be used as a replacement for the production imageThe dev_python image has at least two differences to the production image that prohibit me to use it in a deployment
- the user is not set to nomad (1000)
- the run.sh script is not available in the default working directory.
Maybe the...The dev_python image has at least two differences to the production image that prohibit me to use it in a deployment
- the user is not set to nomad (1000)
- the run.sh script is not available in the default working directory.
Maybe there is more.
It must be possible to use the dev_python image in real deployments, because for certain debugging things the prod image is too limited.
I didn't noticed the user thing and accidentally screwed up a few file ownerships during the reprocessing.Adam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/757NOMAD Oasis UX Test: user roles2024-01-09T14:00:27ZFelix DietrichNOMAD Oasis UX Test: user rolesRelated to #756.
What people/roles are involved when a NOMAD Oasis is installed?
A person involved with the Oasis should be in one or multiple of the following roles:
- Oasis Owner
- Oasis Admin
- It Admin
- Data Producer
- Data C...Related to #756.
What people/roles are involved when a NOMAD Oasis is installed?
A person involved with the Oasis should be in one or multiple of the following roles:
- Oasis Owner
- Oasis Admin
- It Admin
- Data Producer
- Data Consumer
Oasis Owner:
- Responsible for the Oasis
- Usually professor, post-doc, lab owner...
- Decides to create the Oasis
- All general decisions are made by them
- Represents Oasis to the outside world
Oasis Admin:
- Can be the Owner or a delegated person (PhD candidate, post-doc, ...)
- Deals with more technical day-to-day issues
- Handles user management issues (from global keycloak repository? local users?)
- Plans and executes the setup of the IT infrastructure together with IT Admins
- Interacts with all other roles (Owner, IT, Producer, Consumer)
- Main contact person for users and for main NOMAD team regarding technical issues
IT Admin:
- Responsible for providing the technical infrastructure
- Setting up the server + providing hostname
- Setting up the installation of NOMAD (alternative: Oasis Admin?)
- Creates means for access restriction (VPN? HTTPS?)
Data Producer:
- Material Scientist who performs experiments and collects data
- Collects and prepares/sanitizes data
- Uploads data to the NOMA Oasis
- Decides on Access restrictions
- Potentially publishes the data to central NOMAD instance
Data Consumer:
- Scientist or Data Analyst or other end user of the materials science data
- Has read access to the data stored in the Oasis
- Downloads and analyzes data
- Compares different data items
- Visualizes dataFelix DietrichFelix Dietrichhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1008Plugin mechanism2023-12-21T16:06:49ZMichael GöttePlugin mechanismOasis administrators need to add more functionality to NOMAD without requiring a new image.
NOMAD develops want to separate non core functionality from the nomad-FAIR codebase and NOMAD images.
Potential functionality that can be added...Oasis administrators need to add more functionality to NOMAD without requiring a new image.
NOMAD develops want to separate non core functionality from the nomad-FAIR codebase and NOMAD images.
Potential functionality that can be added via plugins:
- schemas
- parsers
- normalisers
- APIs
- CLI commands
--
The original report by Micha: *Loading individual ELN code into an existing docker image*
Hey all,
this is a feature request. Imagine you want to use a fresh and tested docker image from your gitlab registry but you are not happy with the ELN normalizers in that image. Is it possible to develop and commit the ELN part in a different git project and then load this into the image of the registry?
An idea would be to do this in the ```docker-compose```file, e.g. add:
```
volumes:
- ./configs/nomad.yaml:/app/nomad.yaml
- ./eln/:/app/nomad/datamodel/metainfo/eln/
```
I will test this and let you know!
Best Michahttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1261Improve the release process2023-12-21T16:06:49ZMarkus ScheidgenImprove the release process- Don't know how to create an actual release with a NOMAD version that matches the tag. You'll always get a version like `1.1.7.dev0+g2ecdd77f8.d20221223`. How to i create a `1.1.6` image and python package?
- There is no docker tag crea...- Don't know how to create an actual release with a NOMAD version that matches the tag. You'll always get a version like `1.1.7.dev0+g2ecdd77f8.d20221223`. How to i create a `1.1.6` image and python package?
- There is no docker tag created for the gitlab tag
- The tag pipeline is not building an image. So I have to re-run the latest `develop` pipeline to build with the new git generated version
- The integrations test don't work. Probably a file is missing from the image that is used to run the integration test client.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1186Possible improvements on python packaging2023-12-21T16:06:49ZAdam FeketePossible improvements on python packaging- [ ] using src layout
- [ ] ease (>=) on package dependencies in the submodules and constrain them in the main (~=)
- [ ] python version ?? 3.10 or 3.11 (local oasis)
- [ ] test matrix ?
- [ ] convert parsers into plugins/extensions ...- [ ] using src layout
- [ ] ease (>=) on package dependencies in the submodules and constrain them in the main (~=)
- [ ] python version ?? 3.10 or 3.11 (local oasis)
- [ ] test matrix ?
- [ ] convert parsers into plugins/extensions VS monolithic package (Distribution package VS individual packages)
- [ ] implicit namespaces
```python
/src/nomad_lab/parser
/src/nomad_lab/gui
import nomad_lab.parser
import nomad_lab.gui
```
- [ ] linting: we might ignoring too much warnings (ignore them in the code instead)
alternative: black
- [ ] run `gui` and `jupyterhub` independently
- gui: is an independent application which depends on some artefacts
- [ ] adding `linter` and `pytest` configs to `myproject.toml`
- [ ] examples: storing examples in a separate repository using [git LFS](https://docs.gitlab.com/ee/topics/git/lfs/) for the zipped files like: https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-fair-examples
- [ ] docs: The "compiled" documentation should not be part of the python source distribution. Reasoning:
* we need the nomad package to build the documentation which actually should also contain the documentation... Currently the only way to build the python sdist by building it twice.
* most of the other links on the gui are also pointing to external link
* the link of the logo of the documentation redirect to a another page (central deployment) and not to the one where it was actually deployed.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/886Link between NOMAD OASIS and NOMAD Central2023-12-21T16:05:24ZFelix DietrichLink between NOMAD OASIS and NOMAD Central## General
Currently every OASIS is just a clone of the central repository.
They are not linked together, not even through simple pings.
In addition to simple links, it is necessary to define how OASES can differ from the central instal...## General
Currently every OASIS is just a clone of the central repository.
They are not linked together, not even through simple pings.
In addition to simple links, it is necessary to define how OASES can differ from the central installation (in their version, their data, their user rights, ...).
This may be communicated to central, too. In this issue, we outline these challenges and provide a road map for implementation and discussion.
## Current GIT Issues related to OASIS (2022-05-24)
* Improve oasis synchronisation functionality #585
* Integrating NORTH into OASIS #825
* Oasis installation and registration #820
* NOMAD Oasis (GUI) #784
* NOMAD Oasis UX Test: user roles #757
## Requirements: LINK
* Use case 1: Send telemetry data to central in regular intervals. This is discussed in {## Requirements: Telemetry}
* Use-case 2: send data buckets + metadata. This is discussed in section {## Requirements: Data LINK}
## Requirements: Telemetry
* Which data should be sent?
* Users registered
* Data uploaded, stored
* Number of searches
* OASIS location
* Do we need fine-grained info about site-access? This may be a security/leak risk that some may not like.
* See #820
## Requirements: Soft constraints / Installation
* Central: be careful with DDOS attacks from "too many / malicious OASIS links"
* LINK is opt-out, enabled by default
* OASIS owners can disable LINK in a config
* See roles, #757
* The fact that each OASIS sends telemetry data by default MUST be communicated clearly, also how to disable it
* We must be careful with "user data processing" requirements (GDPR). Aggregated data should be fine, but maybe some telemetry data can be used to identify users (link clicks, etc.).
## Requirements: Data LINK
* Also called "Synchronization"
* Send data buckets
* Send metaschema information, when they are stored in files
* How to send new metaschemas defined in python? Not send at all?
* Versioning of data: what if metaschema in the OASIS is newer/older than the one in central?
* See #784
* See #585Daniel LehmbergDaniel Lehmberghttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/628Better user-magement2023-12-21T15:55:38ZMarkus ScheidgenBetter user-magement- upgrade keycloak (to version 8?), keeping our custom interface
- connect via OAuth (e.g. with github, google)
- connect via SAML (e.g. with DFN AAI)
- allow local keycloaks for Oasis (why?)
- common user id (e.g. ORCID)
- consolidate u...- upgrade keycloak (to version 8?), keeping our custom interface
- connect via OAuth (e.g. with github, google)
- connect via SAML (e.g. with DFN AAI)
- allow local keycloaks for Oasis (why?)
- common user id (e.g. ORCID)
- consolidate users (e.g. automatically based on ORCID, CLI functions to migrate users)
- properly use (or don't use at all) affiliations
- allow authors that are not usershttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1415cannot run the pipeline manually2023-12-21T15:40:10ZMohammad Nakhaeecannot run the pipeline manuallyNormally we should be able to run the pipeline manually for the branches that failed because of unexpected server errors. But the rules do not allow.
![Screenshot_from_2023-03-30_13-39-37](/uploads/1587ce4269d10bb6c03851950b9d4978/Scree...Normally we should be able to run the pipeline manually for the branches that failed because of unexpected server errors. But the rules do not allow.
![Screenshot_from_2023-03-30_13-39-37](/uploads/1587ce4269d10bb6c03851950b9d4978/Screenshot_from_2023-03-30_13-39-37.png)https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1778The nomad's appworker doesn't run outside of the nomad's root folder2023-12-21T15:40:07ZAdam FeketeThe nomad's appworker doesn't run outside of the nomad's root folderrunning nomad appworker other place than the nomad's root folder fails:
```
$ nomad admin run appworker
-------------- celery@fekad-mbp2015.local v5.2.7 (dawn-chorus)
--- ***** -----
-- ******* ---- macOS-12.3.1-x86_64-i386-64bit 202...running nomad appworker other place than the nomad's root folder fails:
```
$ nomad admin run appworker
-------------- celery@fekad-mbp2015.local v5.2.7 (dawn-chorus)
--- ***** -----
-- ******* ---- macOS-12.3.1-x86_64-i386-64bit 2023-11-13 17:23:49
- *** --- * ---
- ** ---------- [config]
- ** ---------- .> app: nomad.processing:0x125987310
- ** ---------- .> transport: amqp://rabbitmq:**@localhost:5672//
- ** ---------- .> results: disabled://
- *** --- * --- .> concurrency: 4 (prefork)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
-------------- [queues]
.> celery exchange=celery(direct) key=celery
[tasks]
. nomad.app.resources.routers.resources.retrieve_resources
. nomad.processing.base.proc_task
INFO: Started server process [90059]
INFO: Waiting for application startup.
ERROR: Traceback (most recent call last):
File "/Users/fekad/Work/nomad-1549-notebook-plugin/.venv/lib/python3.9/site-packages/starlette/routing.py", line 671, in lifespan
async with self.lifespan_context(app):
File "/Users/fekad/Work/nomad-1549-notebook-plugin/.venv/lib/python3.9/site-packages/starlette/routing.py", line 566, in __aenter__
await self._router.startup()
File "/Users/fekad/Work/nomad-1549-notebook-plugin/.venv/lib/python3.9/site-packages/starlette/routing.py", line 648, in startup
await handler()
File "/Users/fekad/Work/nomad-1549-notebook-plugin/nomad/app/main.py", line 152, in startup_event
GuiFiles.gui_artifacts_data = get_gui_artifacts_js()
File "/Users/fekad/Work/nomad-1549-notebook-plugin/nomad/cli/dev.py", line 79, in get_gui_artifacts_js
'exampleUploads': _generate_example_upload_metadata(),
File "/Users/fekad/Work/nomad-1549-notebook-plugin/nomad/cli/dev.py", line 259, in _generate_example_upload_metadata
with open('examples/data/uploads/example_uploads.yml') as infile:
FileNotFoundError: [Errno 2] No such file or directory: 'examples/data/uploads/example_uploads.yml'
ERROR: Application startup failed. Exiting.
```
Expected: behaviour: The appworker should run independently what folder you are.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1357Running nomad-oasis on the root path2023-12-21T15:40:06ZAdam FeketeRunning nomad-oasis on the root pathissues/workarounds:
- [ ] update nginx.conf
- [x] update north's health check
- [ ] check on mounted folder ownerships
- [x] fixing GUI's double leading slashes("//api/v1/north/apmtools")issues/workarounds:
- [ ] update nginx.conf
- [x] update north's health check
- [ ] check on mounted folder ownerships
- [x] fixing GUI's double leading slashes("//api/v1/north/apmtools")Adam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/402Enforcing HTTPS across all services2023-12-21T15:40:02ZLauri HimanenEnforcing HTTPS across all servicesCurrently many of the resources that our production machine serves can be retrieved both with http or https protocols.
As far as I understand, the standard these days is to always use https, no matter what the resource is. This ensures ...Currently many of the resources that our production machine serves can be retrieved both with http or https protocols.
As far as I understand, the standard these days is to always use https, no matter what the resource is. This ensures that all outgoing data is always properly secured (we don't have to selectively enable https, as that is prone to mistakes), and that there will be no issue with resources interacting with different protocols.
Doing this should be relative easy: we will still accept incoming requests through http, but these requests will always be redirected to https. This can be done through our nginx server, [with something like this.](https://serversforhackers.com/c/redirect-http-to-https-nginx) You can see that most sites do something similar, e.g. if you try to load this issue page with http, Gitlab will automatically switch to https.
What do you think?https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/616Use pydantic settings management for nomad.config2023-12-21T15:40:00ZMarkus ScheidgenUse pydantic settings management for nomad.configPydantic has build in support for [settings management](https://pydantic-docs.helpmanual.io/usage/settings/). This supports everything that our `NomadConfig`-obj system provides (but better):
- nested config objects
- override from first...Pydantic has build in support for [settings management](https://pydantic-docs.helpmanual.io/usage/settings/). This supports everything that our `NomadConfig`-obj system provides (but better):
- nested config objects
- override from first env (limited), than config file, than default values
Here is an example of how it could work:
```python
from typing import Dict, Any
from pydantic import BaseModel, Field, BaseSettings, HttpUrl
import yaml
import os.path
import os
class Client(BaseModel):
user: str = Field('test', description='The username.')
password: str = '*'
url: HttpUrl = Field('http://nomad-lab.eu')
class NomadConfig(BaseSettings):
client: Client = Client()
not_nested: str = 'hello'
class Config:
env_prefix = 'nomad_'
case_sensitive = False
@classmethod
def customise_sources(
cls,
init_settings,
env_settings,
file_secret_settings):
return (
init_settings,
env_settings,
yaml_config_settings_source, file_secret_settings)
def yaml_config_settings_source(settings: BaseSettings) -> Dict[str, Any]:
if not os.path.exists('nomad.yaml'):
return {}
try:
with open('nomad.yaml') as f:
data = yaml.load(f, Loader=yaml.FullLoader)
if data is None:
return {}
return data
except yaml.YAMLError as e:
raise e
config = NomadConfig()
```
The support of env vars is limited as they only apply to the first level (e.g. NomadConfig). To set nested fields, the top level env var has to be set with a json value:
```
export NOMAD_CLIENT='{"password":"mypassword"}'
```
If necessary this could be replaced by a custom settings source.
```https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/845Updating the legacy Keycloak deployment2023-12-21T15:39:09ZAdam FeketeUpdating the legacy Keycloak deploymentAlthough the 16.1.1 of Keycloak was released about 5 months ago since there is a major update starting with version 17.0.0. The "backend" has been changed and some migration is needed for using the latest versions.
Useful documentations...Although the 16.1.1 of Keycloak was released about 5 months ago since there is a major update starting with version 17.0.0. The "backend" has been changed and some migration is needed for using the latest versions.
Useful documentations:
- [Main page about the migration](https://www.keycloak.org/migration/migrating-to-quarkus)
- [New base image is used for building a container](https://www.keycloak.org/server/containers)
- [Development (using localhost) versus production mode](https://www.keycloak.org/server/configuration)
- https://www.keycloak.org/guides#serverhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/995Mail delivery failed: returning message to sender2023-12-21T15:39:05ZAdam FeketeMail delivery failed: returning message to senderit looks like all the emails that should got to the specific users ends up in support@nomad-lab.hu (and in my spam folder)
For example:
```
Mail Delivery System <Mailer-Daemon@www153.your-server.de>
A message that you sent could not b...it looks like all the emails that should got to the specific users ends up in support@nomad-lab.hu (and in my spam folder)
For example:
```
Mail Delivery System <Mailer-Daemon@www153.your-server.de>
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
lauri.himanen@gmail.com
(ultimately generated from support@nomad-lab.eu)
host gmail-smtp-in.l.google.com [142.251.5.27]
SMTP error from remote mail server after pipelined end of data:
550-5.7.1 [213.133.104.153] Messages missing a valid messageId header are not
550 5.7.1 accepted. t1-20020adfe101000000b0021f157ae467si6385629wrz.115 - gsmtp
---------- Forwarded message ----------
From: support@nomad-lab.eu
To: Lauri Himanen
Cc: The nomad team <support@nomad-lab.eu>
Bcc:
Date:
Subject: Processing completed
Dear Lauri Himanen,
your data uploaded at 2022-08-23T11:36:32.722000 has completed processing. You can review your data on your upload page: https://nomad-lab.eu/prod/v1/staging/gui/uploads
If you encounter any issues with your upload, please let us know and reply to this email.
The nomad team
```https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1404Operatin Nomad Oasis, manage Rabbitmq storage2023-12-21T15:38:53ZMichael GötteOperatin Nomad Oasis, manage Rabbitmq storageHey Nomad,
I am running a nomad oasis and for some reason rabbitmq has docker volumes with 33GB, that does not seem to be reasonable to me. If this grows in a similar rate it quickly becomes too big.
Here you see what i mean.
![image](...Hey Nomad,
I am running a nomad oasis and for some reason rabbitmq has docker volumes with 33GB, that does not seem to be reasonable to me. If this grows in a similar rate it quickly becomes too big.
Here you see what i mean.
![image](/uploads/9dd36d90a3520b557c4cf1a0619b84fb/image.png)
Do you have an idea what to do?
Best MichaMarkus ScheidgenMarkus Scheidgenhttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1685Getting complaint in installation of nomad with python3.102023-12-21T15:38:52ZRubel MozumderGetting complaint in installation of nomad with python3.10In the dev environment installation process having a complaint from mdtraj package while `python version 3.10`:
```
File "/home/rubel/NOMAD-FAIRmat/GL/nomad-FAIR/.NF_1674_xrd/lib/python3.10/site-packages/pip/_vendor/pyproject_hoo...In the dev environment installation process having a complaint from mdtraj package while `python version 3.10`:
```
File "/home/rubel/NOMAD-FAIRmat/GL/nomad-FAIR/.NF_1674_xrd/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
main()
File "/home/rubel/NOMAD-FAIRmat/GL/nomad-FAIR/.NF_1674_xrd/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/rubel/NOMAD-FAIRmat/GL/nomad-FAIR/.NF_1674_xrd/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
return hook(metadata_directory, config_settings)
File "/tmp/pip-build-env-ghmqe1s6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 396, in prepare_metadata_for_build_wheel
self.run_setup()
File "/tmp/pip-build-env-ghmqe1s6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 507, in run_setup
super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
File "/tmp/pip-build-env-ghmqe1s6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 341, in run_setup
exec(code, locals())
File "<string>", line 301, in <module>
File "/tmp/pip-build-env-ghmqe1s6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1134, in cythonize
cythonize_one(*args)
File "/tmp/pip-build-env-ghmqe1s6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one
raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: mdtraj/geometry/src/_geometry.pyx
```
But no issues are found with `python 3.9`.https://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1220Keycloak redirect problem with nomad-oasis behind ssl (traefik) proxy2023-12-21T15:38:48ZAdam FeketeKeycloak redirect problem with nomad-oasis behind ssl (traefik) proxyThe url returns with "502 Bad gateway nginx/1.13.9"
```
https://nomad.eln.data.fau.de/keycloak/auth/realms/nomad/protocol/openid-connect/auth?response_type=code&redirect_uri=http%3A%2F%2Fnomad.eln.data.fau.de%2Fnomad-oasis%2Fnorth%2Fhub%...The url returns with "502 Bad gateway nginx/1.13.9"
```
https://nomad.eln.data.fau.de/keycloak/auth/realms/nomad/protocol/openid-connect/auth?response_type=code&redirect_uri=http%3A%2F%2Fnomad.eln.data.fau.de%2Fnomad-oasis%2Fnorth%2Fhub%2Foauth_callback&client_id=nomad_public&state=eyJzdGF0ZV9pZCI6ICJmOTMxYWIyMWM3NDU0MWUwYTRkNzczYTVmZDU1Y2FiNCIsICJuZXh0X3VybCI6ICIvbm9tYWQtb2FzaXMvbm9ydGgvaHViL2FwaS9vYXV0aDIvYXV0aG9yaXplP2NsaWVudF9pZD1qdXB5dGVyaHViLXVzZXItYWRtaW4tanVweXRlciZyZWRpcmVjdF91cmk9JTJGbm9tYWQtb2FzaXMlMkZub3J0aCUyRnVzZXIlMkZhZG1pbiUyRmp1cHl0ZXIlMkZvYXV0aF9jYWxsYmFjayZyZXNwb25zZV90eXBlPWNvZGUmc3RhdGU9ZXlKMWRXbGtJam9nSW1VME9EVTJOVFU0WkRrNFpUUXhOemc0TkRWaVltUTVNamt6TXpCallXTXlJaXdnSW01bGVIUmZkWEpzSWpvZ0lpOXViMjFoWkMxdllYTnBjeTl1YjNKMGFDOTFjMlZ5TDJGa2JXbHVMMnAxY0hsMFpYSXZkSEpsWlNKOSJ9&scope=openid+profile
```Adam FeketeAdam Feketehttps://gitlab.mpcdf.mpg.de/nomad-lab/nomad-FAIR/-/issues/1017Customize NOMAD installations2023-12-21T15:38:47ZMarkus ScheidgenCustomize NOMAD installationsOasis admins might want to disable some features. This can be archived with filters on
- available search filters
- available schemas (e.g. for eln, but also in the metainfo)
- available parsers
- available examples
- available north too...Oasis admins might want to disable some features. This can be archived with filters on
- available search filters
- available schemas (e.g. for eln, but also in the metainfo)
- available parsers
- available examples
- available north tools
This is pure on an installation or run level and should not require a build or separate images.