This document contains details about the pecularities of managing sites and services of the Science Mesh.
SITE_ID
property if the short site name is changed.ORGANIZATION
property to the site.Every site needs to provide an instance of the REVAD
service. This acts as the main IOP entrypoint and also provides various other critical endpoints. The service URL needs to point to the main URL the IOP can be accessed under (e.g., https://sciencemesh.uni-muenster.de/iop
); it may not contain any port number. Monitoring needs to always be enabled for this service type.
To properly configure the REVAD
service, additional endpoints and properties must be provided, as shown below.
The REVAD
service exposes various additional endpoints that also must be configured properly. Each such endpoint consists of its relative (e.g., iop/metrics
) or absolute (e.g., https://iop.uni-muenster.de/metrics
) URL, its name (which must match its type), as well as its interface name, which is interpreted as its type (this means that the endpoint and interface names are identical).
Name | Description | URL (common value) | Interface | Monitored? |
---|---|---|---|---|
GATEWAY | Main gRPC endpoint; note that the protocol (grpc:// ) and the gRPC port must always be specified | grpc://<host>:<port> | GATEWAY | Yes |
METRICS | Prometheus metrics endpoint | metrics | METRICS | Yes |
OCM | OpenCloudMesh endpoint | ocm | OCM | No |
WEBDAV | Webdav endpoint | remote.php/webdav | WEBDAV | No |
Only the URLs of the endpoints may differ from above common values; all endpoints need to be added, and their names, interfaces and monitoring need to exactly match what is listed above.
There are also a few optional endpoints that you might need to add depending on your deployment. If in doubt, simply do not add them.
Name | Description | URL (common value) | Interface | Monitored? |
---|---|---|---|---|
MESHDIR | Mesh directory endpoint | meshdir | MESHDIR | Yes |
API_VERSION
property. Note that this property might be removed in future iterations.