Closed horsburgh closed 3 days ago
benlee0423
commented
2 weeks ago USU-Hydrologic project was created. @horsburgh You should get an invite to join the project. The other 4 users were assigned to Viewer Role. Let me know if any services you need access to.
benlee0423
commented
2 weeks ago @horsburgh We are wondering if all 5 users in the requests get invitation email to join the project. If not, can we ask them to associate *.usu email accounts to google?
arpita0911patel
commented
3 days ago Closing this ticket based on email from Jeff as he is able to access the account now.
1. Requester Information: This should include the name and contact information of the person making the request.
Details: We are requesting that the following individuals be given access to CIROH's Google Cloud Platform account: Jeff Horsburgh: jeff.horsburgh@usu.edu (project Co-PI) Sierra Young: sierra.young@usu.edu (project PI) Sajan Neupane: sajan.neupane@usu.edu (project MS student) Razin Issa: razinbin.issa@usu.edu (project MS student) Safran Khan: safran.khan@usu.edu (project PhD student)
2. Project Information: Provide a brief description of the project and its goals. This can help the infrastructure team understand the context and purpose of the requested resources. Please highlight how this project will be benefit from and/or provide benefit to other resources on the shared infrastructure.
Project Title: CIROH: Advancing Camera-Based Monitoring for Operational Hydrologic Applications Project Summary: https://ciroh.ua.edu/research-projects/advancing-camera-based-monitoring-for-operational-hydrologic-applications/ Project Goals: The overall goal of this project is to demonstrate how operational requirements for integrating low-cost cameras and computing infrastructure into existing hydrologic monitoring networks can be met, along with evaluating the benefits of cameras for continuous monitoring and prediction. Project Benefits: We seek to develop serverless cloud workflows/pipelines for processing imagery collected at stream gaging sites. Information extracted from images will provide realtime, hydrologically relevant information - e.g., stream width, depth, velocity to augment available data from realtime USGS streamflow gages and will make more data and information available at gage locations for use in NextGen modeling efforts. We are investigating serverless cloud as a means to achieve scalability for growing the number of locations from research scale (a handfull of sites with cameras) to operational scale with hundreds or even thousands of sites. Part of this work is examining advantages and tradeoffs of different cloud platforms. For that part of the work, we are starting with AWS (for which we already have access to CIROH's AWS account) and Google Cloud Platform (for which we are asking for access as part of this request).
3. Project Description: If your project involves developing software or scripts, briefly describe the software you plan to develop.
We will be developing lambda functions for AWS and equivalent Google Cloud Functions (for comparison) to automate the transfer, preprocessing, segmentation, and analysis of images collected using cameras at active stream gaging locations. Functions will execute machine learning models on the captured images to extract width, depth, and velocity. We plan to develop serverless cloud workflows/pipelines for processing imagery collected at stream gaging sites. Code will generally be written using Python, but will involve a variety of scripts designed to execute different parts of the image processing workflow (e.g., image capture on a datalogger, transfer to cloud storage, image preprocessing, model execution, results generation, and logging hydrologic variables to a data store). All of the code we develop will be hosted publicly in a GitHub repository.
4. Resource Requirements: Specify the compute, storage, and network resources needed for the project. Be as specific as possible about the number of resources required, and any specific configurations or capabilities needed. This information will help the infrastructure team determine the appropriate resources to allocate.
NOTE: Our needs for this part of the project are similar to the earlier request we sent to get access to the CIROH AWS account. We just need to be able to develop equivalent functions/pipelines across the different platforms for comparison purposes and to examine the potential cost and performance tradeoffs.
Options:
Cloud Provider: GCP
Required Services in the Cloud:
List of GCP services we anticipate needing
List of GCP Services we do not anticipate needing
5. Timeline: Indicate the expected timeline for the project and when the resources will be needed. This information can help the infrastructure team plan and allocate resources accordingly.
We anticipate using resources through the end of our project, which is a 3-year CIROH project funded starting June 1, 2023 and ending May 2026.
6. Security and Compliance Requirements: If there are any specific security or compliance requirements for the project, these should be clearly stated in the request. This will help ensure that the necessary security measures are in place for the project.
We don't currently have any specific security or compliance requirements for our development and testing. The image and video data we are collecting are not sensitive and have no restrictions on access or release. All of our source code and development is open, so no concerns there.
7. Estimation: Include any cost estimation or requirements for the project. This will help the infrastructure team select the most cost-effective solutions for the project.
We anticipate that the image/video storage will be relatively inexpensive in Google Cloud Storage, and the rate of data collected is not overly frequent (e.g., one new image/video per site every 30 minutes). We will incur additional costs with executing Google Cloud Functions. Storage in the Google Artifact Registry may be in the free tier. We anticipate that overall costs should be in the ballpark of $100 - $150 per month.
8. Approval: Indicate the necessary approval processes or sign-offs required for the request.
Please contact me with any questions
Jeff Horsburgh: jeff.horsburgh@usu.edu