All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- SPS Version 2.2.0
- OGC API Version 2.0.0
- OGC Python Client Version 2.0.0
- unity-sps: https://github.com/unity-sds/unity-sps/releases/tag/2.2.0
- unity-sps-ogc-processes-api: https://github.com/unity-sds/unity-sps-ogc-processes-api/releases/tag/2.0.0
- unity-sps-ogc-processes-api-client-python: https://github.com/unity-sds/unity-sps-ogc-processes-api-client-python/releases/tag/2.0.0
- EPIC:
Security
- EPIC:
Scaling
- [New Feature]: Increase ephemeral disk space for Airflow workers
- [New Feature]: Enable users to select the EC2 type to execute a workload
- [New Feature]: Set the DAG run status to "failed" if the main worker task failed
- [[New Feature]: Demonstrate use of ECR within an Airflow DAG (#186)
- EPIC:
Airflow/WPS-T Integration
- EPIC:
Production Venue Deployments
- EPIC:
SPS Infrastructure
- ghcr.io/unity-sds/unity-sps/sps-airflow:2.2.0
- ghcr.io/unity-sds/unity-sps/sps-docker-cwl:2.2.0
- ghcr.io/unity-sds/unity-sps-ogc-processes-api/unity-sps-ogc-processes-api:2.0.0
- For Administrators:
- For Deverlopers:
- For Users:
- SPS Version 2.1.0
- OGC API Version 1.0.0
- OGC Python Client Version 1.0.0
- unity-sps: https://github.com/unity-sds/unity-sps/releases/tag/2.1.0
- unity-sps-ogc-processes-api: https://github.com/unity-sds/unity-sps-ogc-processes-api/releases/tag/1.0.0
- unity-sps-ogc-processes-api-client-python: https://github.com/unity-sds/unity-sps-ogc-processes-api-client-python/releases/tag/1.0.0
- EPIC:
Airflow/WPS-T Integration
- EPIC:
Airflow Scaling Improvements
- [New Feature]: Implement autoscaling of Kubernetes worker nodes
- [New Feature]: Nightly test for SBG end-to-end workflow
- [Dependency]: PSE to provide analysis of resources needed by each SBG Task
- [New Feature] Only use MCP Golden AMIs
- [New Feature] Configure multiple pools of Kubernetes nodes
- [New Feature] Retrieve venue-dependent parameters from SSM
- [New Feature] Store deployment parameters as AIRFLOW variables
- [New Feature] Enable Airflow "plugins" folder
- [Task] Add TESTING.md file to SPS repo
- EPIC:
SPS Infrastructure
- EPIC:
SPS Security
- ghcr.io/unity-sds/unity-sps/sps-airflow:2.1.0
- ghcr.io/unity-sds/unity-sps/sps-docker-cwl:2.1.0
- ghcr.io/unity-sds/unity-sps-ogc-processes-api/unity-sps-ogc-processes-api:1.0.0
- SPS Deployment with Terraform
- Interacting with an Existing SPS Deployment
- SPS Airflow Custom Docker Image Build Instructions
- Tutorial: Register, Execute, and Unregister a Process using the OGC API - Processes
- Tutorial: Register and Execute a CWL Workflow
Version 2.0.0
- unity-sps: https://github.com/unity-sds/unity-sps/releases/tag/2.0.0
- unity-sps-ogc-processes-api: https://github.com/unity-sds/unity-sps-ogc-processes-api/releases/tag/2.0.0
- EPIC:
Airflow Deployment
- [New Feature]: Deploy EKS to MCP venues with Terraform
- [New Feature]: Deploy Airflow to MCP venues with Terraform (no adaptation yet)
- [New Feature]: Create a CWL Operator or simply a CWL DAG to execute a CWL workflow
- [New Feature]: Using shared disk space for inter-task communication
- [New Feature]: Implement autoscaling of Kubernetes pods on a given set of worker nodes
- [Task] Migrate the new SPS with Airflow code to unity-sps repository
- [New Feature] Allow choosing EC2 types when deploying an EKS cluster
- [New Feature]: Allow propagation of permissions to Docker containers
- [New feature] Add Terraform parameters to customize the amount of disk available to each Pod
- EPIC:
SBG Venue Deployment
- EPIC:
SPS Infrastructure
- ghcr.io/unity-sds/unity-sps/sps-airflow:2.0.0
- ghcr.io/unity-sds/unity-sps/sps-docker-cwl:2.0.0
- ghcr.io/unity-sds/unity-sps-ogc-processes-api/unity-sps-ogc-processes-api:2.0.0
- SPS EKS Cluster Provisioning with Terraform
- SPS Airflow Deployment with Terraform
- SPS Airflow Custom Docker Image Build Instructions
- unity-sps-prototype: https://github.com/unity-sds/unity-sps-prototype/releases/tag/1.2.0
- unity-sps-api: https://github.com/unity-sds/unity-sps-api/releases/tag/1.2.0
- unity-sps-register_job: https://github.com/unity-sds/unity-sps-register_job/releases/tag/1.2.0
- unity-sps-workflows: https://github.com/unity-sds/unity-sps-workflows/releases/tag/1.2.0
- ades_wpst: https://github.com/unity-sds/ades_wpst/releases/tag/1.2.0
- unity-sps : https://github.com/unity-sds/unity-sps/releases/tag/1.2.0
- EPIC:
workflow metadata
- [unity-sps-prototype #210] [New Feature]: Store arbitrary labels in the Jobs Database
- [unity-sps-prototype #211] [New Feature]: Query the Jobs Metadata by arbitrary labels
- [unity-sps-prototype #217] [Risk]: Evaluate scalability of WPS-T API for querying the Jobs Database
- EPIC:
chirp-workflow-execution
- [unity-sps-workflows #8] [Dependency]: Stub implementation for CHIRP workflow
- [unity-sps-workflows #10] [Dependency]: Docker container for execution of CHIRP rebinning PGE
- [unity-sps-workflows #11] [Dependency]: Full implementation of CHIRP workflow
- [unity-sps-workflows #12] [Dependency]: Docker container for CMR search
- [unity-sps-workflows #13] [Dependency]: Docker container for Cataloging
- [unity-sps-workflows #14] [Risk]: Processing large data volumes with CWL and Docker
- [unity-sps-prototype #192 ] [New Feature]: Add an optional PVC to an SPS deployment
- [unity-sps-prototype #195] [Dependency]: Docker container for stage-in step
- [unity-sps-prototype #227] [New Feature]: Use stage EFS as data temporary location for CHIRP execution
- EPIC:
no magic
- [unity-sps-prototype #132] As a user, i want to be explicit about inputs into my process execution (no magic)!
- [unity-sps-prototype #157] [New Feature]: Pass environment variables to a Docker container execution
- EPIC:
sps-improvements-23.3
- [unity-sps-prototype #221] [Dependency]: Tagging U-SPS resources
- [unity-sps-prototype #222] [Dependency]: Add SPS API URL to the SSM store
- [unity-sps-prototype #230] [Bug]: One SPS deployment can accidentally execute another SPS deployments deployed process containers
- EPIC:
workflow-label-inputs
- [unity-sps-prototype #160] [New Feature]: Pass arbitrary labels when requesting a job execution
- [unity-sps-prototype #181] [Risk]: Define how labels should be specified during workflow submission
- ghcr.io/unity-sds/unity-sps-prototype/hysds-core:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-ui-remote:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-mozart:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-grq2:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-verdi:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-factotum:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/ades-wpst-api:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-api:unity-v1.2.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-hysds-pge-base:unity-v1.2.0
- docker.elastic.co/elasticsearch/elasticsearch:7.9.3
- docker.elastic.co/logstash/logstash:7.10.2
- rabbitmq:3.11.13-management
- redis:7.0.10
- docker:23.0.3-dind
- busybox:1.36.0
- Tutorial on using the WPS-T API to register an application package and to execute a job
- SPS API with examples
- Tutorial on pre-warming a U-SPS cluster
- Description of the Jobs Database: architecture and usage
- unity-sps : https://github.com/unity-sds/unity-sps/releases/tag/1.1.0
- unity-sps-prototype: https://github.com/unity-sds/unity-sps-prototype/releases/tag/1.1.0
- unity-sps-api: https://github.com/unity-sds/unity-sps-api/releases/tag/1.1.0
- unity-sps-register_job: https://github.com/unity-sds/unity-sps-register_job/releases/tag/1.1.0
- unity-sps-workflows: https://github.com/unity-sds/unity-sps-workflows/releases/tag/1.1.0
- ades_wpst: https://github.com/unity-sds/ades_wpst/releases/tag/1.1.0
- EPIC #7:
jobs-database
- [unity-sps-prototype #185] [Epic]: Implement Jobs Database
- [unity-sps-prototype #186] [New Feature]: Send SNS message for job creation task
- [unity-sps-prototype #187] [New Feature]: Send SNS message for job completion task
- [unity-sps-prototype #188] [New Feature]: Consume SNS message for job creation task and job completion tasks
- [unity-sps-prototype #189] [New Feature]: Deploy jobs database
- [unity-sps-prototype #193) [New Feature]: Create SNS topic, SQS queue and Lambda function for Jobs Database as part of U-SPS deployment
- [unity-sps-prototype $194] [Bug]: Prevent duplicate documents in jobs database
- EPIC #10:
chirp-workflow-execution
- [unity-sps-workflows #8] [Dependency]: Stub implementation for CHIRP workflow
- [unity-sps-workflows #12] [Dependency]: Docker container for CMR search
- [unity-sps-workflows #14] [Risk]: Processing large data volumes with CWL and Docker
- [unity-sps-prototype #192] [New Feature]: Add an optional PVC to an SPS deployment
- EPIC #1:
min/max scaling
- [unity-sps-prototype #141] As a project Manager, i want to set maximum and minimum limits on scaling for processing at venue creation time (static)
- EPIC #4:
no magic
- [unity-sps-prototype #132] As a user, i want to be explicit about inputs into my process execution (no magic)!
- ghcr.io/unity-sds/unity-sps-prototype/hysds-core:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-ui-remote:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-mozart:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-grq2:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-verdi:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-factotum:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/ades-wpst-api:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-api-fork:unity-v1.1.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-hysds-pge-base:unity-v1.1.0
- docker.elastic.co/logstash/logstash:7.10.2
- rabbitmq:3.11.13-management
- redis:7.0.10
- docker:23.0.3-dind
- busybox:1.36.0
- Tutorial on using the WPS-T API to register an application package and to execute a job
- SPS API with examples
- Tutorial on pre-warming a U-SPS cluster
- MCP Test:
- Processing Endpoint (WPS-T API): http://a720fb4de892844bf884f037c17bb583-1070798053.us-west-2.elb.amazonaws.com:5001
- Scaling Endpoint (SPS API): http://a7096fc6842e84da688b45586d194498-2116025617.us-west-2.elb.amazonaws.com:5002
- MCP Dev:
- Processing Endpoint (WPS-T API): http://aa17aedf4454a4cc596a67a1efb73411-1350404365.us-west-2.elb.amazonaws.com:5001
- Scaling Endpoint (SPS API): http://a440158f49fab4278bdcf2bcb145082b-625745.us-west-2.elb.amazonaws.com:5002
- unity-sps : https://github.com/unity-sds/unity-sps/releases/tag/1.0.0
- unity-sps-prototype: https://github.com/unity-sds/unity-sps-prototype/releases/tag/1.0.0
- unity-sps-api: https://github.com/unity-sds/unity-sps-api/releases/tag/1.0.0
- unity-sps-register_job:
- unity-sps-workflows: https://github.com/unity-sds/unity-sps-workflows/releases/tag/1.0.0
- ades_wpst: https://github.com/unity-sds/ades_wpst/releases/tag/1.0.0
- EPIC #130:
ancillary data
- [unity-sps-prototype #148] Mount EFS partitions on U-SPS cluster
- EPIC #146:
automatic testing
- [unity-sps-prototype #153] Smoke test to deploy a simple process and execute a job request
- EPIC #132:
no magic
- [unity-sps #154]: Pass explicit input parameters to a WPS-T job request
- [unity-sps-prototype #159]: Return the input parameters as part of the WPS-T DescribeProcess method
- [unity-sps-prototype #167]: The WPS-T method to register a process may time out while building the PGE Docker image
- EPIC #142:
processing-instance-types
- [unity-sps-prototype #142]: As a project manager, i want to set default compute types for processing nodes at deploy time, so that i can predict costs for the system (Static)
- EPIC #162:
u-sps-api
- [unity-sps-prototype #163]: New SPS API with stub pre-warm method
- [unity-sps-prototype #167]: Refactor the HySDS workers as a Kubernetes DaemonSet
- [unity-sps-prototype #167]: Scale the number of worker nodes in the Kubernetes cluster
- ghcr.io/unity-sds/unity-sps-prototype/hysds-core:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-ui-remote:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-mozart:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-grq2:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-verdi:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/hysds-factotum:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/ades-wpst-api:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-api-fork:unity-v1.0.0
- ghcr.io/unity-sds/unity-sps-prototype/sps-hysds-pge-base:unity-v1.0.0
- docker.elastic.co/logstash/logstash:7.10.2
- rabbitmq:3.11.13-management
- redis:7.0.10
- docker:23.0.3-dind
- busybox:1.36.0
- Tutorial on using the WPS-T API to register an application package and to execute a job
- SPS API with examples
- Tutorial on pre-warming a U-SPS cluster
- MCP Test:
- Processing Endpoint (WPS-T API): http://a720fb4de892844bf884f037c17bb583-1070798053.us-west-2.elb.amazonaws.com:5001
- Scaling Endpoint (SPS API): http://a7096fc6842e84da688b45586d194498-2116025617.us-west-2.elb.amazonaws.com:5002
- MCP Dev:
- Processing Endpoint (WPS-T API): http://aa17aedf4454a4cc596a67a1efb73411-1350404365.us-west-2.elb.amazonaws.com:5001
- Scaling Endpoint (SPS API): http://a440158f49fab4278bdcf2bcb145082b-625745.us-west-2.elb.amazonaws.com:5002