Service Reference Card

Functional Description
Daemons Running
Init scripts and options
Configuration files location with example or template
Logfile locations and other useful audit information
Open ports
Where is service state held (and can it be rebuilt)
Security information
Utility scripts
Location of reference documentation for users and administrators

CDMI provides the official reference implementation of the SNIA Cloud Data Management Interface (CDMI), an ISO standard, and also a Spring Boot application port of the SNIA CDMI-Server.

The CDMI server has been extended to support Quality-of-Service (QoS) and Data Life-cycle (DLC) operations for multiple storage back-ends like dCache, Ceph, GPFS, Gemss+TSM, StoRM and HPSS.

CDMI is composed of two main components:

the CDMI core server, which handles the CDMI REST calls and passes them on to the back-end module
the CDMI back-end module, which is used to connect the CDMI server to a specific storage back-end

## Daemons running

The following daemons need to be running:

cdmi-server
redis-server (in case of redis DB is running directly on the CDMI server)

## Init scripts and options

For the cdmi-server service

service cdmi-server start
service cdmi-server status
service cdmi-server stop

## Configuration files location with example or template

The configuration files are located in

/var/lib/cdmi-server/config

## Logfile locations and other useful audit information

The log files can be found under (default)

/var/log/syslog

or as configured

## Open ports

The following ports need to be open depending on the services running:

cdmi-server: one for the REST API, typically 80 or 443 (8888 default)

## Where is service state held (and can it be rebuilt)

The CDMI server state is kept in the redis database. Location and access information for the database can be found in the configuration files.

## Security information

Access control Mechanism description (authentication & authorization)

The CDMI server supports two authentication & authorization mechanisms, HTTP Basic authentication and OpenID Connect. HTTP Basic authentication is typically used by the administrator, OpenID Connect for user access. The OIDC provider can be configured and defaults to the INDIGO IAM service. For more documentation see the INDIGO IAM user guide.

Network Usage

Two services are running that need (local) network access on this node

the redis server. The server binds to the 6379/tcp port (localhost, default)
the CDMI server which binds to one tcp port (usually something like 80/tcp, 443/tcp)