DRAFT – DRAFT – DRAFT – DRAFT – DRAFT
Introduction
The Huginn service is an event/message stream aggregation/processing/publishing service used with the DUL Website.
Governance:
This service was created in response to a need to integrate services that were not otherwise well-integrated, particularly around the Duke University Calendar system.
Mission and Scope:
The mission/scope of this service is extremely limited. It is designed to aggregate feeds and re-present them on the DUL website.
Stakeholders:
- John Pormann, Core Services
- Tom Hadzor, AUL for Development
Owners:
- Functional Owner: Aaron Welborn, Director of Communications
- Technical Owner: David Chandek-Stark has the most in-depth knowledge of these servers
- OIT owns and operates the OpenShift container system (similar to their VMware system); OIT runs Group-Manager which provisions accounts and can change passwords
Users:
- Primary users are the Development/Communications team in the Libraries
- Patrons are the end-consumer of the different data-feeds that Huginn integrates.
Maintenance and Sustainability:
Huginn
| Description | This is a somewhat bare-bones Linux container running the Huginn app. | |
| Support | Huginn is an open-source tool and does not have a formal support channel. The container is running on OIT's OpenShift container management system. | |
| Community | As an open-source tool, there may be some community support available. | |
| Strategy | The technology team is responsible for monitoring of security patches, etc. The design is for this server to be "bare bones" so feature requests and expansions should be limited. | |
| Sunsetting | This service should be a prime candidate for sunsetting if/when the separate tools can integrate directly. As one of the main tools is the Duke University Calendar, we may have to support Huginn (or similar) until that tool changes. | |
| Risks | All the risks of any other open-source tool; in this case, since it is integrating disparate feeds, there is the risk that the feed could change (breaking the connection) and we may be the only ones experiencing that breakage. |
Issue Submission and Escalation:
- Any user may submit an issue via the IT Support @ Duke University Libraries web form. In response to the prompt What can we help you with?, specify Servers & Systems Operations.
- Members of the stakeholder group may reach the technical team on Slack at #devops
- The technical team will use Gitlab issue boards to track deeper problems or issues with the system (https://gitlab.oit.duke.edu/devops/devops-planning/-/boards/734)
- There is no expectation for other staff to have access to this system (i.e. no privileged access beyond sys admins).
Review:
Annual:
The stakeholders team will meet annually with the technology team to:
- Review the existing service description, stakeholder list, support structure,
- Close out any issues that may no longer be relevant,
- Review the list of users with privileged access,
- Estimate any project efforts or needs for the coming year,
- Review and adjust the list of users with access to the system, including both privileged and non-privileged access control groups, in Grouper/Group Manager as well as programmatic access.
This activity falls in the November-December time frame. Any actionable work will be documented and reviewed by DST-LT.
Servers/Service Details:
| huginn | main container running the ssh/sftp service |