TI3 Operational Activities

• Outcome Description:  

  • FOR WHO: Staff, students all stakeholders of DLE systems/platforms and integrations

  • WHAT: Providing support, maintenance, development and testing of the DLE platforms, in partnership with hosting partners, 3rd party product vendors across both product software, infrastructure and DEV/OPS implementations.

  • WHY (Business Value): Ensuring business continuity, security of service, scalability and performance for core systems

• Dependencies

  • Catalyst IT, Internal product resources, specialist skill sets as required

• Risks:

  • Lack of internal resource

• Outcome Deliverables EPICs:

TI3

• Preview in the Cloud - CTP-659

  • What: o rewrite the jenkins_preview tagged steps of the build pipeline

  • Why: The preview server is paid for until summer 2023. Beyond that, we will need to pay for running costs.

  • Dependency: k8s/ECS usage maturity / Risk: ?

• Migrate to Azure SSO - CTP-1798

  • What: Reflect/Blogs

  • Why: ISD is driving the case for applications to move away from Shibboleth to Azure SSO. Shibboleth will no longer work after 31st March 2023. Full details can be found here.  Azure AD SSO  Our following services currently use Shibboleth for login authentication.

  • Dependency: ? / Risk: ?

• CLC - Rollover Tool improvements - CTP-762

  • What: Capture all stories that we can work on once the MVP is built

  • Why: ???.

  • Dependency: ? / Risk: ?

• Miscellaneous Feature request - CTP-252

  • What: This feature is needed to record feature requests that will need consideration in future TIs.

  • Why: ???.

  • Dependency: ? / Risk: ?

• Miscellaneous Plugin Reviews - CTP-150

  • What: Any plugin or requests received during TI 3

  • Why: Any plugin reviews and requests during TI 3 may be placed here as stories along with any associated material so that they can be allocated as part of TI 4 planning.

  • Dependency: ? / Risk: ?

• Preview Improvements for Moodle 4 - CTP-2021

  • What: ??

  • Why: In TI2, the Preview environment was implemented in AWS and the pipeline migrated to GitHub Actions. We now need to keep improving this environment to support its availability to demo Moodle 4.

  • Dependency: ? / Risk: ?

• DLE Operations - CTP-392

  • What: FR, CIs, Moodle releases, Monthly Manual patching, Service Health Reviews - Schedule & docs, etc.

  • Why: Day-to-day operational support and monitoring are essential to maintain a complex system such as Moodle and ensure value for stakeholders.

  • Dependency: Catalyst/Vendor resource / Risk: The product requires an additional member of staff within this team area to support our services.