13. Anabrid Operations

This section is dedicated to the REDAC1 Systems Operations Team at anabrid GmbH. The term REDAC1 refers to the REDAC system with serial number 1, see About the first REDAC for details. Some software solutions that are not part of REDAC are provided and operated within this transitional time. These are listed in this section and their use is documented. There is no documentation regarding administration, as administration is carried out by the Anabrid Systems Operations Team. Within this transitional time, the system operated by anabrid is globally reachable via the internet at https://redac.anabrid.com

schema drawing — Fig. 13.1 Overview about the REDAC-internal services vs. the services operated by anabrid. Click to enlarge.

13.1. List of provided services

The following services are not part of REDAC but part of the operations teams, next to the actual REDAC hardware and software maintenance. Similar systems are supposed to be hosted by a REDAC customer. See also figure Overview about the REDAC-internal services vs. the services operated by anabrid. Click to enlarge. for an overview.

Systems Access to redac.anabrid.com: General system access is provided over anabrid paid 1gbit/sec symmetric internet fiber uplink which has a guaranteed uptime of certainly less then 99% (i.e. 14min downtime per day).
Systems website landing page “User Interface” https://redac.anabrid.com/ui/: This is a little static website (Sveltekit) which is managed, amongst other static assets, via SFTP. The website itself, in particular, is a goodie and not part of the official software infrastructure
Status Page https://status.anabrid.net/status/redac1: Anabrid operates a number of status services which allows to have a quick overview about the availability and reliability of the services. The reachability of the REDAC1 System is monitored on this website.
Grafana dashboard https://stats.redac.anabrid.com/: For demonstrating/displaying temperature readout. Runs as a docker container on the SuperController.
JupyterHub instance https://jupyter.redac.anabrid.com/: This is a Kubernetes cluster operated by the OPs team which has direct access to REDAC internal network. However, it is physically hosted and served not on SuperController but dedicated bare metal digital hardware.
Authentification https://auth.redac.anabrid.com/: Anabrid transitionally operates the user authentification system for REDAC1. The underlying software system Keycloak is an official suggestion to be used also by the customer within the REDAC software infrastructure, cf. Authentification.
User Helpdesk https://helpdesk.anabrid.com/: Anabrid runs a ticketing system in order to provide help for REDAC1 users. This is a company wide ticketing system where anabrid employees help on improving the customers jorney. Users can open a ticket straight on the helpdesk or write a mail to helpdesk@anabrid.com. Please insert the term REDAC1 in the subject message of your tickets. Clearly, this ticketing system is not part of REDAC infrastructure.
Anabrid User Hotline 0049 30 629 3047 20: Anabrid runs a telephone line which allows people to ask for help within regular office hours. There is no guarantee that support can be provided via telephone. However, the onsite team in Ulm is always happy to receive inqueries at a direct visit.

Note

Note that REDAC1 has a standalone user account system (see Authentification) which is by no means related to any institutional user managament systems by DLR or anabrid.

13.2. About bringing REDAC1 to another network

Currently, REDAC1 is “hard-wired” to the Anabrid Ulm network by means that the public domain redac.anabrid.com resolves to the IP address of the Anabrid Ulm gateway and thus https://redac.anabrid.com will stop working once you disconnect REDAC from Anabrid’s network in Ulm and plug it into an Ethernet socket of some other network, for instance a network owned by DLR.

More to write here.