Openstack VM Test System

STAC test VM

• STAC browser: http://stac2.cloud.dkrz.de
• API: http://stac2.cloud.dkrz.de:8081/api.html
• 16 GB Rams and 8 CPUs.

... tbd. .. info on setup, access, roadmap etc ....

Setup

using podman installation to run docker containers:

• https://podman.io/

Installed STAC with elasticsearch:

• https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch

Using docker-compose.yml based on the project default:

• https://github.com/stac-utils/stac-fastapi-elasticsearch-opensearch/blob/main/docker-compose.yml

We had to tweak the docker-compose and added a volume for the elastic-search container to persist the index:

volumes:
   - es_data2:/usr/share/elasticsearch/data # this was missing!

stac-browser:

• https://github.com/radiantearth/stac-browser

fabis announcement mail:

We used a podman-container configuration that combines mainly three APIs:

• stac-browser with Nginx
• stac-api
• elasticsearch

The main page is the stac-browser´s view on the stac-api index. You can now start to insert stac objects into this API via the stac-api within the DKRZ internet. They should become visible in the browser after injection.

We have neither put any efforts on sustainability (injected stac objects may vanish over time), nor on sharing this VM with the world (all runs as sudo so far, no https or certificates, firewall settings, aliases,..) and I am not sure if we want that or even can do that as there are no certs right now afaik.

We have not agreed on any structure but maybe we can use system names for the entry stage collections (freva, esgf, pool, eerie, ...)? Just an Idea...

Anyway, have fun, break the system.