Education Space Scheduling and Modelling Sync¶
This page gives an overview of the Education Space Scheduling and Modelling synchronisation service, describing its current status, where and how it's developed and deployed, and who is responsible for maintaining it.
Student Registry procured a room scheduling application called TermTime from Semestry. Room Booking is currently handled by Booker from EventMap. A synchronisation process was required where the activities scheduled in TermTime would become room bookings in Booker. Also, for consistency the room and building definitions in Booker would need to be synchronised to TermTime.
The ESSM Sync is currently
Currently, which databases and discrepancies between Booker and TermTime are being ironed out.
Following this, a testing stage using a combination of Booker live and staging and a TermTime training database, will confirm that the synchronised works as expected.
Finally, this will become live using a production TermTime database and Booker live.
Technical queries and support should be directed to email@example.com and will be picked up by a member of the team working on the service. To ensure that you receive a response, always direct requests to firstname.lastname@example.org rather than reaching out to team members directly.
Issues discovered in the service or new feature requests should be opened as GitLab issues in the administration project or sync-tool repository, if a sync tool specific issue or you lack permission to the administration project.
The ESSM Sync is currently deployed as Gitlab CI and Scheduled Pipelines in the Gitlab Synchronisation Tasks project.
There is no additional infrastructure other than Gitlab itself and the DevOps Gitlab CI runners.
The source code for the ESSM Sync is spread over the following repositories:
|Sync Tool||The source code for the synchronisation processing|
|Sync Tasks||The Gitlab CI and Terraform infrastructure code for creating the Scheduled Pipelines|
|Administration||General project wide issue tracking and documentation|
The following gives an overview of the ESSM Sync is built on.
|Sync Tool||python||requests, PyYAML and dpath|
|Sync Tasks - Infrastructure||terraform||gitlab provider|
|Sync Tasks - Gitlab CI||bash||docker|
The following gives an overview of how the ESSM Sync is deployed and maintained
How and where the ESSM Sync is deployed¶
See Sync Tasks Gitlab project.
Deploying a new release¶
Updates to the sync-tool will be used automatically by next schedule pipeline.
Gitlab CI pipeline failures will cause automatic notification to the schedule owner (UIS DevOps Division Robot).
A local setup can be created by:
- installing the sync tool
pip install https://gitlab.developers.cam.ac.uk/uis/devops/essm/sync-tool
- creating configuration files from the templates used in the Sync Tasks repository, containing Booker and TermTime API credentials from ESSM 1password vault
essmsync -c <configuration> <operation>as described in sync tool README
Testing should be initially done against Booker staging instance and TermTime CambTest database.
Detailed investigation of API usage and the synchronised processes may be found in the Administration Wiki.
Service Management and tech lead¶
The service owner is Student Registry.
The service manager is Neil King.
The tech lead is Robin Goodall.