Skip to content

Slice 4: Deploy vv1.89.1 to modelharbor (amd64 CI image) #5

@utarn

Description

@utarn

Parent

What to build

Deploy the verified vv1.89.1 to production on modelharbor. Push vv1.89.1 so the CI image-build workflow builds the real amd64 image (NOT the throwaway local arm64 image) and pushes it to the registry. Before touching the running proxy, capture a current production database backup and check prisma migrate status for drift. Then docker compose pull litellm && docker compose up -d litellm, verify the proxy is healthy, and confirm one live glm request records response_cost > 0. Retain the previous vv1.82.3-stable.patch.4 image and the database backup as the rollback path (Prisma migrations are forward-only, so rollback is image-swap plus backup-restore).

Acceptance criteria

  • vv1.89.1 is pushed and CI builds + pushes the amd64 image to the registry
  • A production database backup is captured before deploy
  • prisma migrate status is checked for drift before deploy
  • modelharbor pulls the amd64 image and docker compose up -d litellm succeeds
  • The proxy is healthy after deploy
  • One live glm request records SpendLogs.response_cost > 0
  • The previous vv1.82.3-stable.patch.4 image and DB backup are retained for rollback
  • Only the modelharbor litellm stack is touched (other litellm stacks on the host are untouched)

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentReady to be picked up by an agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions