@@ -38,6 +39,7 @@ The source code for the Network Access Tokens service is spread over the followi
| Repository | Description
| ----------- | ------------------ |
| [Application Server](https://gitlab.developers.cam.ac.uk/uis/devops/network-access/network-access) | The source code for the main application server |
| [Ansible](https://gitlab.developers.cam.ac.uk/uis/devops/grails-application-ansible-deployment) | The Ansible used to deploy all the Dev Group Grails Apps |
## Technologies used
...
...
@@ -46,23 +48,24 @@ The following gives an overview of the technologies the Network Access Tokens se
| Category | Language | Framework(s) |
| -------- | -------- | --------- |
| Server | Groovy 2.4.12 | Grails 1.3.10 |
| DB | Postgres | 10.5 |
| DB | Postgres | 13 |
## Operational documentation
The following gives an overview of how the Network Access Tokens service is deployed and maintained.
### How and where the Network Access Tokens service is deployed
The Network Access Tokens service application is deployed using RPM packages. These are built by Gitlab CI in the [Application Server repository](https://gitlab.developers.cam.ac.uk/uis/devops/network-access/network-access). These can be copied to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) run by infra-sas@uis by following these [instructions](https://wiki.cam.ac.uk/ucs/Bes_-_Managed_Installation_Service#How_to_add_SLES_10.2F11_or_RHEL_.28S.29RPMS_to_Bes). As a last resort RPMs can be manually copied and installed.
The Network Access Tokens service application is deployed using WAR packages. These are built by Gitlab CI in the [Application Server repository](https://gitlab.developers.cam.ac.uk/uis/devops/network-access/network-access). These are deployed using the Ansible above
### Deploying a new release
Once the RPM packages are added to the [Bes RPM package repository](https://bes.csi.cam.ac.uk) running `zypper in <package name>` will install, if the package is an upgrade, `zypper up` should upgrade the package(s).
Once the WAR packages are built they can be deployed using the Ansible. See the Ansible docs for information on how to.
### Monitoring
The Network Access Tokens service is monitored by [nagios](https://nagios.uis.cam.ac.uk/nagios/).
There is also a [status page](https://tokens.uis.cam.ac.uk/adm/status) that checks the various components of the service and returns 200 if everything is functioning normally.
There is a [liveness](https://tokens.uis.cam.ac.uk/adm/liveness) page used by the traffic manager to determine live nodes.
## Other documentation
*[End user documentation](https://help.uis.cam.ac.uk/service/network-services/tokens)
...
...
@@ -80,3 +83,5 @@ The following engineers have operational experience with the Network Access Toke
