HyP3 v7.5.0

Added

• The SRG_GSLC_CPU job spec
• The SRG_GSLC_CPU job type to the hyp3-lavas and hyp3-lavas-test HyP3 deployments

Changed

• The hyp3-tibet-jpl deployment now uses the m6id[n] instance families and includes the ARIA_RAIDER job spec

HyP3 v7.4.0

Added

• The hyp3-lavas and hyp3-lavas-test enterprise HyP3 deployments.

HyP3 v7.3.0

This release adds support for access codes. If a user specifies an active access code when they apply for HyP3 access, they will be granted automatic approval without the need for a HyP3 operator to review their application.

If you operate a HyP3 deployment, you can create a new access code by adding an item to the AccessCodesTable DynamoDB table for your deployment, with any string for the access_code attribute and an ISO-formatted UTC timestamp for the start_date and end_date attributes, e.g. 2024-06-01T00:00:00+00:00 and 2024-06-02T00:00:00+00:00 for an access code that becomes active on June 1, 2024 and expires on June 2, 2024.

Added

• The PATCH /user endpoint now includes an optional access_code parameter and returns a 403 response if given an invalid or inactive access code.

Changed

• Turn off hyp3 ACCESS spend by zeroing the max VCPUs in the associated deployment.
• Reduce product lifetime in hyp3 ACCESS deployment to 14 days.

HyP3 v7.2.1

Fixed

• Added missing requests dependency to lib/dyanmo/setup.py. Fixes #2269.

HyP3 v7.2.0

This release includes changes to support an upcoming user whitelisting feature. A new user will be required to apply for HyP3 access and will not be able to submit jobs until an operator has manually reviewed and approved the application. As of this release, all new and existing users are automatically approved without being required to submit an application, but this will change in the near future.

⚠️ Important notes for HyP3 deployment operators:

• Changing a user's application status (e.g. to approve or reject a new user) requires manually updating the value of the application_status field in the Users table.
• The response for both /user endpoints now automatically includes all Users table fields except those prefixed by an underscore (_).
• The following manual updates must be made to the Users table upon deployment of this release:
  • Add field application_status with the appropriate value for each user.
  • Rename field month_of_last_credits_reset to _month_of_last_credit_reset.
  • Rename field notes to _notes.

Added

• A new PATCH /user endpoint with a single use_case parameter allows the user to submit an application or update a pending application. The structure for a successful response is the same as for GET /user.
• A new default_application_status deployment parameter specifies the default status for new user applications. The parameter has been set to APPROVED for all deployments.

Changed

• The POST /jobs endpoint now returns a 403 response if the user has not been approved.
• The response schema for the GET /user endpoint now includes:
  • A required application_status field representing the status of the user's application: NOT_STARTED, PENDING, APPROVED, or REJECTED.
  • An optional use_case field containing the use case submitted with the user's application.
  • An optional credits_per_month field representing the user's monthly credit allotment, if different from the deployment default.

Removed

• The reset_credits_monthly deployment parameter has been removed. Credits now reset monthly in all deployments. This only changes the behavior of the hyp3-enterprise-test deployment.

HyP3 v7.1.1

Changed

• Reduced start_execution_manager batch size from 600 jobs to 500 jobs. Fixes #2241.

HyP3 v7.1.0

Added

• A hyp3-its-live-test deployment to deploy-enterprise-test.yml for ITS_LIVE testing in preparation for some significant ITS_LIVE project development
• A hyp3-a19-jpl-test deployment to deploy-enterprise-test.yml for ARIA testing of the m6id[n] instance families
• An ARIA_RAIDER job spec that allows RAIDER processing of previous INSAR_ISCE job that either did not include a weather model or failed on the RAiDER step.
• ARIA_RAIDER jobs are now available in the hyp3-a19-jpl and hyp3-a19-jpl-test deployments.

Changed

• The INSAR_ISCE_TEST.yml job spec now only differs from the INSAR_ISCE.yml with respect to the ++omp-num-threads parameter, because the value is specific to a particular instance family
• Job specs are no longer required to include the granules parameter.

Removed

• The AUTORIFT_ITS_LIVE_TEST.yml job spec which supported running test versions of the AUTORIFT jobs in the production hyp3-its-live deployment

HyP3 v7.0.0

This release marks the final transition to the new credits system. These changes apply to the production HyP3 API at https://hyp3-api.asf.alaska.edu. Read the announcement for full details.

Changed

• Each type of job now costs a different number of credits, as shown in the table here.
• Users are now given an allotment of 10,000 credits per month.

HyP3 v6.5.1

Fixed

• Added a Lambda function that sets Private DNS names enabled to false for VPC endpoint in EDC.

HyP3 v6.5.0

Added

• A publish_bucket parameter to AUTORIFT_ITS_LIVE and AUTORIFT_ITS_LIVE_TEST that specifies if product should be uploaded to either the ITS_LIVE open data bucket or test bucket.
• Access key secrets to AUTORIFT_ITS_LIVE and AUTORIFT_ITS_LIVE_TEST that allow for S3 upload of products.

Changed

• Update throughput for ACCESS deployments by factor of 4 (from 1000 to 4000 vcpus).