Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade ecosystem to pgSTAC > 0.7 #176

Closed
3 of 4 tasks
anayeaye opened this issue May 16, 2023 · 3 comments
Closed
3 of 4 tasks

Upgrade ecosystem to pgSTAC > 0.7 #176

anayeaye opened this issue May 16, 2023 · 3 comments
Assignees

Comments

@anayeaye
Copy link
Collaborator

anayeaye commented May 16, 2023

What

We are maintaining this database for the long term and need to begin to add routine pgSTAC schema upgrades to our maintenance schedule. For each stage of the VEDA ecosystem the maintenance should include:

  1. Record the approximate time it takes to execute each step in this process (it will help inform future pgstac and RDS upgrade plans)
  2. Migrate pgSTAC schema to the latest recommended version
  3. Update pypgstac version used veda-stac-ingestor to match the database version
  4. Nice-to-have: Test stac-api, raster-api, and open a veda-config PR for the dev APIs to confirm that the dashboard functions as expected

PI Objective

Objective 223
Epic 242

Basic Testing Notes

While we are working out our standard operation procedures for updating the ecosystem, here are some notes for testing that the change is non breaking. Should be very simple to touch each system, we aren't going for coverage yet.

  • STAC API: /docs are reachable and browsing appears to work as expected
  • Raster API: /docs are reachable and tiling appears to work as expected (for example try the cog viewer and a notebook in veda-documentation)
  • Ingest systems working: whether running from a separate instance of veda-stac-ingestor or from the planned integrated ingest-api, we should be able to publish a collection and an item (re publish something we already have).
  • Nice to have: open a do not merge veda-config PR to confirm that the develop APIs support the dashboard as expected

AC

  • measurements for individual steps of the migration and ecosystem upgrade are recorded to plan future maintenance windows
  • dev update duration used to plan and advertise the staging upgrade (a formality for VEDA developers and EO Dashboard developers)
  • dev stage of veda-backend and veda-stac-ingestor upgraded to the same version and baseline smoke tests performed after deployment
  • staging stage of veda-backend and veda-stac-ingestor upgraded to the same version and baseline smoke tests performed after deployment
@smohiudd
Copy link
Contributor

I opened a PR to upgrade dev veda-backend pgstac but the deploy workflow failed because of an import error for urllib3 which is used viarequests: #180

Going to try again with another pull request with urllib3<2

@smohiudd
Copy link
Contributor

There's a bug with the migration to 0.7.6 so had to go with 0.7.4 instead. The upgrade to the dev deployment was successful and the migration took about 30 mins according to the cloudwatch logs.

@anayeaye
Copy link
Collaborator Author

This is debugged and released to all operational environments #178

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants