/
ATWG Meeting - 2025-04-17

ATWG Meeting - 2025-04-17

Meeting Time

April 16th, 2024 at 12:00 pm Central Time

Meeting Location (WebEx / Virtual)

Webex meeting recording: Admin Tooling WG - April 2025-20250416 1810-1
Recording link: Meet virtually with Cisco Webex. Anytime, anywhere, on any device.

pw: atwg2025

Participants

First Name

Last Name

Organization

Eshara

Mondal

Education Analytics

Mark

TenHoor

Education Analytics

David

Cintron

EdWire

Jean-Francois

Guertin

EdWire

Robert

Nield

Unicon

Katie

Favara

Region 4

Robert

Hunter

Ed-Fi Alliance

David

Clements

Ed-Fi Alliance

Stephen

Fuqua

Ed-Fi Alliance

Jason

Hoekstra

Ed-Fi Alliance

Support: Ann Su

Meeting Discussion Deck

 

Admin Console Framing Questions

  • Can we find adoption in new states/ESC like Delaware, Tennessee & others for SY2025-26?  If so, what do you need for support?

  • Can we code share into React apps for Claim Set and EdOrgs/Descriptor Management?  If so, how should we do this?

  • Would we support this for vendor integration cases and parallel test suite?

  • What is best to focus our roadmap & efforts on and support growth & deployment?

 

Meeting Minutes Summary

The meeting discussed updates and improvements to the admin console and API for state and ESC data hubs.

  • Focus on best practices, tools, and roadmap updates to unlock value for state and ESC data hubs.

  • Admin Console built off shared source from Texas Education Exchange, future compatible with ODS 7.X and Admin API 2.3.

  • Release of Admin Council 1.0 paired with Admin API a2.3 as release candidates, aiming for security checks before full release.

  • The team has added new faces and has been working on the admin console since last year.

  • The admin console is running in a Docker composed environment and serves as the user interface.

  • The instance management worker is responsible for creating, deleting, and managing instances in a dynamic manner.

  • The team is working on adding more functionality, such as retention policies and managing vendors and applications.

  • The admin console is attached to multiple deployments of the edfi ODS API, with each tenant having their own separate PG bouncer.

  • The admin API supports multi-tenant access and can connect to multiple admin APIs.

  • There is a plan to support cloud configuration stores like Azure and AWS parameter stores for the admin API.

  • There are discussions about the next steps for the admin console, including potential integration with new adopters and new functionality for version 1.1.

  • Admin API and DMS config service align with management API spec for unity in admin console interaction.

  • Integration challenges between different tech stacks (React vs Vue.js) require API-level sharing.

  • Emphasis on accelerating API availability to support diverse admin console functionalities and improve security measures.

Action items

  • Work with security vendors to ensure security checks for the release candidates

  • Investigate support for SQL servers running on-prem or in the cloud

  • Shape the product to work with different IDPs, such as Azure AD

  • Highlight bug fixes in the release notes

  • Gather feedback on admin council and admin API at tech congress

  • Fix the health check management worker issue

  • Implement a retention policy for soft deleted instances

  • Double check where the key and secret for applications are provisioned

  • Follow up on implementing cloud configuration store support and externalizing app settings for admin API

  • Follow up on tickets for connecting with multiple admin APIs

  • Continue discussions and follow up in the next week's tech congress meeting

Next Meeting:

  • We’ll meet at Tech Congress 2025 and follow up into MSP and other forums

  • We’ll regroup in late May or early June to resume Admin API topics