Viz EC2 Services to Lambda - Part 2 - Rapid Onset Flooding Probability #558
Conversation
…processing lambda function
TylerSchrag-NOAA
changed the title
There was a problem hiding this comment.
@TylerSchrag-NOAA can you double check the HWP file changes in all these files? I think there might be some issues with the table references and whether or not the "max" is there.
There was a problem hiding this comment.
as in the product is creating a "mrf_gfs_5day_high_water_probability_hucs" table but the mapx is looking for a "mrf_gfs_5day_max_high_water_probability_hucs"
There was a problem hiding this comment.
You're right, I missed/botched this one somehow. Thank you!
removed HWP services from the pipelines_config.yml so that the EC2 doesn't create windows services for them to run
|
@TylerSchrag-NOAA I also updated the pipeline_config file which is used by the EC2 to create the windows services |
Thank you! I totally missed that. |
Thanks Shawn - Sorry to make you approve again, but I just realized I forgot to add the new dask lambda layer. |
#558) This PR migrates the ensemble-based Rapid Onset Flooding Probability products from the Viz EC2 to the Viz Max Values lambda function (now called Python Preprocessing). It broadly encapsulates the following changes: **Changes** - New rapid_onset_flooding product script in the python_preprocessing lambda function that supports both 12 hour SRF and 5 day GFS MRF configurations. - Removal of rapid_onset_flooding pipeline and product files in the source-aws_loosa library **Deployment Considerations:** - Not sure if we should include this in the 2.1.4 release or not? I'm good to test/fix quickly and thoroughly next week if you want to include it. Otherwise, fine to go in the next one (wait to merge for now) - We will need to include a ingest schema db dump when deploying to UAT. --------- Co-authored-by: CoreyKrewson-NOAA <[email protected]>
This PR migrates the ensemble-based Rapid Onset Flooding Probability products from the Viz EC2 to the Viz Max Values lambda function (now called Python Preprocessing). It broadly encapsulates the following changes:
Changes
Deployment Considerations: