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

Move High Water Probability (and maybe ROF Probability) from EC2 to Lambda #468

Closed
6 of 8 tasks
TylerSchrag-NOAA opened this issue Jun 14, 2023 · 1 comment · Fixed by #543
Closed
6 of 8 tasks
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@TylerSchrag-NOAA
Copy link
Contributor

TylerSchrag-NOAA commented Jun 14, 2023

With Corey's enhancement to bring the lambda max values into the step function, we can now easily have that same lambda function run high water probability services, and potentially ROF probability (if run times can be consistently lower than 15 minutes).

  • SRF High Water Probability
  • MRF High Water Probability
  • SRF ROF Probability
  • MRF ROF Probability

Dev Tasks

  • Update lambda_shared_funcs to support multiple range_tokens in file_pattern
  • Tweak max_values lambda configuration to support larger ephemeral storage, and viz db connection info (and rename?)
  • Add Probability python code to max_values lambda function
  • Disable/remove corresponding EC2 services
@TylerSchrag-NOAA TylerSchrag-NOAA self-assigned this Jun 14, 2023
@TylerSchrag-NOAA TylerSchrag-NOAA added the enhancement New feature or request label Jun 14, 2023
@TylerSchrag-NOAA
Copy link
Contributor Author

Update for documentation: I had SRF and MRF High Water Prob running in the Max Values lambda function as part of the historic data requests, but lost most of that work in the Great TI Purge of '23. I probably need a week to get it working again, and am waiting for the right timing to do that.

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

Successfully merging a pull request may close this issue.

1 participant