Page Comparison

Meeting Time

August 9th, 2024 at 11:00 am Central Time

Meeting Location (WebEx / Virtual)

( To be provided here before the meeting. )

...

Participants

Meeting Materials

• Agenda

  View file
  name Administrative Tooling Working Group - August 2024.pptx

• Use Cases for Tenant Management API

Notes

These note complement the slide deck above and make the most sense when read along with the deck.

• Workgroup and member intro

• Discuss purpose and scope

  Recommendations

• Quick intro of Ed-Fi admin tools roadmap projects

  • Admin API

  • API Publisher

  • Plans for Admin Console

Field scan of today’s implementations

• Mandate from TC to start work group to discuss API Publisher, Admin App,and other tools to develop

• What do you want to tackle here?

• Ed-Fi Tools 2024 Roadmap Review

  • Admin API replaced Admin App

    • EA - we are still only deploying 2.1, based on our work load, also based on historical release have worked around breaking change

      • Can expand to other Ed-Fi products, e.g. ODS/API 7.1

    • SF - don’t understand why it’s a blocker when 5.2 is backward compatible with 5.1

      • EA - we saw table change in 5.2

      • SF - will follow up

    • JH - inform Customer Support Team with bugs; we have upgraded QA operation and improved documentation

    • EdWire - documented changes are helpful; we can forward the ones we have with the upgrades

      • Discussed in MSP SIG - Potential to have a release channel? 

      • SF - we have pre-release binaries or Docker image; just need to let you know where to find those

      • EdWire - We can do pre-flight testing ahead of time and provide feedback to you before production

      • SF - which code are you using?

        • EA - we grab the Docker image, just using that as base and add our modification

        • EdWire - we pull the full source, assuming we need to debug

    • SF -when we have a specific bug fix but not ready to do a patch release

    • JH - Support team can release a Docker image for pre-release

    • EdWire - sometimes we pull the codes down for security scanning, to address the dependency fixes

      • JF - we always have to adopt the code for some infrastructure

      • For 7.1, if we don’t want to hardcode the tenants, we have to do source code to make it more scannable

    • EA - we run straight Ed-Fi code

    • JF - we want to support both models, understand the utilities, and build pipeline

    • EdWire - going forward, we can probably go some code contribution with multi tenancy

  • API Publisher 1.1

    • EA - using a lot for SC and TX, doing everything we need it to

      • But we are not on the latest release, need to take the code and modify to get log in to work

      • Problem with how log message is sent

      • JH - will put a ticket on this issue

      • How long and how many to get matrix out

    • SF - need to think about difference between basic application that is running and to limit tree log in

    • EA - we want to put a UI in front of it, actual error or actual payload

      • SF - maybe data import, can add database synch

      • EdWire - it’s another database to maintain, there are already a lot of pattern in native library

      • SF - error to collect to find options

    • EA - another issue with TX is they want to put grade limit on API

      • Control how many request can be sent

      • SF - Rate limit with Status code 429, .NET package “POLLY”?

      • SF - problem Circuit breaker multi threaded

      • Jason  to Mark -  please make that a CSR / Salesforce ticket!

    • EdWire - other implementation in TX, error may be with API itself

      • SF - adding rate limit directly to API

    • EdWire - different client may have different performance requirement

      • For us, it’s at the tenant level

      • For rate limit, Publisher needs to learn from Ed-Fi

      • Can 429 provide response

      • EA -  429 response does not include what the limits are

      • SF - David or JF - open ticket on rate limiting on ODS/API

• Tenant Management API

  • EA - like the idea but hope don’t have to use it

    • Have a lot of custom logic for how to parse name, log things

    • We can’t deal with 6 months timeline to get bug fixes

  • SF - would still like to get feedback

    • •Use Cases for Tenant Management API

  • EdWire - may want to have non-MSP users to take a look

    • We have our own concept of tenant at high level, data boundary

    • We are looking at Admin API as the mechanism with the same structure already in place

    • We will provide feedback in a few weeks

• Group discussion & next meeting schedule review

  • Admin API

    • EdWire - hitting performance issue with 2x line

    • JH - Release this month with enhancement for 2x and maintenance for 1x

    • EdWire - support for multi data standard with 7.x

Next Meeting: 2024-09-13 11am CT