yangyl/managed-portal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
c507edd81b4b1e58bfdea18a2b90ca3600fe44c5
managed-portal/tasks/todo.md

3.2 KiB
Raw Blame History

Task Plan

Checklist

  • Reuse the already-published managed-portal-20260519-f3f40b5-11.zip main bundle and cut updated installer/weights artifacts for the same tag.
  • Publish the updated installer and separate weights archive to 10.8.0.1 and verify the HTTP endpoints.
  • Commit and push the repository changes for the split-weights Ubuntu installer flow.

Scope And Risks

  • Scope: keep the existing OTA application ZIP for 20260519-f3f40b5-11, generate a refreshed installer plus separate people-flow weights archive for that same release tag, publish them to 10.8.0.1, and push the supporting repository changes to Git.
  • Expected touch points: .11 release artifacts, /var/www/html/ai_deploy on 10.8.0.1, deploy/package-managed-portal-ota.sh, deploy/install-managed-portal-ota.sh, README.md, .gitignore, and task tracking files.
  • Risk: reusing the existing main ZIP means the installer and weights archive must remain compatible with the already-published managed-portal-20260519-f3f40b5-11.zip.
  • Risk: the current local repository does not contain real weights payload files, so the separate weights archive may need to be generated from the .11 host release workspace or a stable host weights directory instead of local source control.
  • Risk: the commit must exclude local artifact files and only capture the intended repo changes.

Validation Intent

  • Prove the refreshed installer and separate weights archive exist for tag 20260519-f3f40b5-11.
  • Prove both artifacts are downloadable from 10.8.0.1/ai_deploy.
  • Prove the Git commit/push contains only the intended repository changes.

Review

  • Status: complete.
  • Reused OTA application bundle:
    • Kept the already-published managed-portal-20260519-f3f40b5-11.zip as-is because the main program contents did not change.
    • Regenerated only the installer and the separate weights archive for the same release tag.
  • .11 artifact refresh:
    • Synced the updated packaging and installer scripts to /home/xiaozheng/managed-portal.
    • Reused release_build/release-manifest-20260519-f3f40b5-11.env.
    • Generated release_build/install-managed-portal-20260519-f3f40b5-11.sh.
    • Generated release_build/people-flow-weights-20260519-f3f40b5-11.tar.gz from /home/xiaozheng/people_flow_project/weights.
  • OTA publication result on 10.8.0.1:
    • Published install-managed-portal-20260519-f3f40b5-11.sh.
    • Published people-flow-weights-20260519-f3f40b5-11.tar.gz.
    • Preserved the existing managed-portal-20260519-f3f40b5-11.zip.
    • Confirmed install-managed-portal-latest.sh still resolves to install-managed-portal-20260519-f3f40b5-11.sh.
    • Confirmed managed-portal-latest.zip still resolves to managed-portal-20260519-f3f40b5-11.zip.
  • HTTP verification:
    • http://10.8.0.1/ai_deploy/people-flow-weights-20260519-f3f40b5-11.tar.gz returns 200 OK with Content-Length: 1135171626.
    • http://10.8.0.1/ai_deploy/install-managed-portal-20260519-f3f40b5-11.sh returns 200 OK with Content-Length: 8081.
    • http://10.8.0.1/ai_deploy/managed-portal-20260519-f3f40b5-11.zip returns 200 OK with Content-Length: 4880.
  • Git result:
    • Committed the repo changes as d1c4b77 with message Split OTA weights for Ubuntu installs.
    • Pushed main to origin.