Workshop Resource Request: [NGIAB Workshop]
Workshop Resource Request: Navigating the NextGen Ecosystem and NextGen In A Box (NGIAB)
1. Workshop Lead Information
As we prepare to host the CIROH DevCon2025 workshop, it is essential to have a clear understanding of the workshop lead's contact information. The workshop lead, Arpita Patel, is affiliated with the University of Alabama (UA) and can be reached at apatel54@ua.edu. This information will enable us to communicate effectively with the workshop lead and ensure a smooth execution of the event.
2. Workshop Information
The CIROH DevCon2025 workshop, titled "Navigating the NextGen Ecosystem and NextGen In A Box (NGIAB)," is scheduled to take place on [insert dates]. The workshop is expected to attract 50 participants, who will engage in a series of activities and learning objectives designed to equip them with the necessary skills to navigate the NextGen ecosystem. The workshop's primary focus is on providing hands-on experience with NextGen In A Box (NGIAB), a cutting-edge technology that has the potential to revolutionize various industries.
3. Workshop Description
The workshop content will be divided into several modules, each designed to build on the previous one. Participants will engage in a series of activities, including hands-on exercises, group discussions, and presentations. The workshop will cover a range of topics, including NextGen In A Box (NGIAB) architecture, deployment, and management. Participants will also have the opportunity to work on real-world projects, applying the skills and knowledge they acquire during the workshop.
4. Resource Requirements
To ensure the successful execution of the workshop, we require a range of computing resources. The following are the specific requirements:
4.1. Resource Type
We require access to the NSF ACCESS Allocation, which will provide us with the necessary resources to host the workshop.
4.2. Per-User Resource Requirements
Each participant will require the following resources:
- Number of vCPUs per user: 2
- Memory (GB) per user: 8
- Storage (GB) per user: 20
- GPU requirements (if any): NVIDIA Tesla T4, ~16GB, ~4 CPUs
4.3. Specific Service Requirements
We will need access to the following services:
- AWS Services:
- EC2 - Specify instance type(s): c5.xlarge
- S3 - Specify bucket type (public/private): private
- EBS (Amazon Elastic Block Store)
- RDS
- VPC (Virtual Private Cloud)
- Lambda
- ArcGIS on AWS
- Google Cloud Services:
- Google Compute Engine - Specify instance type(s): n1-standard-8
- Google Cloud Storage
- Google BigQuery (Note: we will provide one key per workshop)
- Google Cloud Functions
- CIROH-2i2c JupyterHub Resources:
- Small - 5GB RAM, 2 CPUs
- Medium - 11GB RAM, 4 CPUs
- Large - 24GB RAM, 8CPUs
- Huge - 52GB RAM, 16 CPUs
- GPU - NVIDIA Tesla T4, ~16GB, ~4 CPUs
- On-premise VM Resources (NSF ACCESS):
- Number of VMs: 70
- CPUs per node: 4
- Memory per node: 16GB
- Required software modules: NextGen In A Box (NGIAB)
5. Workshop User Management
To manage user access and authentication, we will use the following methods:
- Will participants need individual accounts? (Yes)
- Will you provide a list of participant emails? (Yes)
- Do participants need persistent storage beyond the workshop? (No)
6. Workshop Timeline
The following is the workshop timeline:
- Resource availability start date (for setup/testing): [insert date]
- Workshop date(s): [insert dates]
- Resource teardown date: [insert date]
- Will resources be needed after the workshop ends? (No)
7. Security and Compliance Requirements
We require the following security and compliance measures:
- Data encryption
- Access controls
- Audit logs
8. Cost Estimation
We estimate the following costs for the workshop duration:
- AWS Cost Calculator: https://calculator.aws/#/
- Google Cloud Pricing Calculator: https://cloud.google.com/products/calculator
9. Additional Information
We would like to request the following additional resources:
- A dedicated support team to assist with technical issues
- A backup plan in case of unexpected technical issues
10. Working Group Affiliation
We are affiliated with Working Group 1.
11. Approval
We require approval from the following individuals:
- [Insert names and titles]
Resource Information Links:
- CIROH-2i2c JupyterHub: JupyterHub Documentation
- NSF ACCESS: ACCESS Resource Allocations
By providing the necessary resources and support, we are confident that the CIROH DevCon2025 workshop will be a success and provide participants with the skills and knowledge they need to navigate the NextGen ecosystem.
Frequently Asked Questions (FAQs) for the CIROH DevCon2025 Workshop
Q: What is the CIROH DevCon2025 workshop, and what are its learning objectives?
A: The CIROH DevCon2025 workshop, titled "Navigating the NextGen Ecosystem and NextGen In A Box (NGIAB)," is a hands-on training event designed to equip participants with the necessary skills to navigate the NextGen ecosystem. The workshop's primary focus is on providing hands-on experience with NextGen In A Box (NGIAB), a cutting-edge technology that has the potential to revolutionize various industries.
Q: Who is the workshop lead, and how can I contact them?
A: The workshop lead is Arpita Patel, affiliated with the University of Alabama (UA). You can reach her at apatel54@ua.edu.
Q: What are the resource requirements for the workshop?
A: We require access to the NSF ACCESS Allocation, which will provide us with the necessary resources to host the workshop. Each participant will require 2 vCPUs, 8GB of memory, 20GB of storage, and an NVIDIA Tesla T4 GPU.
Q: What services will be needed during the workshop?
A: We will need access to the following services:
- AWS Services: EC2, S3, EBS, RDS, VPC, Lambda, and ArcGIS on AWS
- Google Cloud Services: Google Compute Engine, Google Cloud Storage, Google BigQuery, and Google Cloud Functions
- CIROH-2i2c JupyterHub Resources: Small, Medium, Large, Huge, and GPU
- On-premise VM Resources (NSF ACCESS): 70 VMs, 4 CPUs per node, 16GB of memory per node, and NextGen In A Box (NGIAB) software modules
Q: How will user access and authentication be managed?
A: We will use individual accounts for participants, and we will provide a list of participant emails. Participants will not need persistent storage beyond the workshop.
Q: What is the workshop timeline?
A: The workshop timeline is as follows:
- Resource availability start date (for setup/testing): [insert date]
- Workshop date(s): [insert dates]
- Resource teardown date: [insert date]
- Will resources be needed after the workshop ends? (No)
Q: What are the security and compliance requirements for the workshop?
A: We require the following security and compliance measures:
- Data encryption
- Access controls
- Audit logs
Q: How will the costs for the workshop be estimated?
A: We will use the AWS Cost Calculator and the Google Cloud Pricing Calculator to estimate the costs for the workshop duration.
Q: What additional resources are required for the workshop?
A: We require a dedicated support team to assist with technical issues and a backup plan in case of unexpected technical issues.
Q: What is the working group affiliation for the workshop?
A: We are affiliated with Working Group 1.
Q: What is the approval process for the workshop?
A: We require approval from the following individuals: [insert names and titles].
Q: Where can I find more information about the workshop and its resources?
A: You can find more information about the workshop and its resources on the following links:
- CIROH-2i2c JHub: JupyterHub Documentation
- NSF ACCESS: ACCESS Resource Allocations
We hope this FAQ article has provided you with the necessary information about the CIROH DevCon2025 workshop. If you have any further questions or concerns, please do not hesitate to contact us.