Connor Couetil graduated with his Bachelor of Science degree in Computer Science in May 2026. Part of the process of earning that degree was completing a capstone project, which he tied to his role as a teaching assistant. Couetil had prior experience as a professional software engineer before attending Purdue. His experience, as well as his interest in teaching students real-world software tools and practices, led him to design the course curriculum for CS 351: Intro to Cloud Computing, taught and developed by Professor George B. Adams, III, Teaching Professor of Computer Science at Purdue. The cloud computing course is relatively new at Purdue. A previous TA had crafted four cloud assignments for an earlier version of the course. Couetil’s goal was to take this work and elevate it, giving students an immersive educational experience that would help them after graduation.

“I approached this with the goal of wanting to teach students something modern,” says Couetil. “Basically, I wanted to give students an experience that will help them land an internship or job, right? Which means teaching modern practices and software tools that professionals in the industry use to this day. It means using conceptual approaches to solving technical problems, which is highly relevant to the types of challenges that professional software engineers work through. Also, the materials need to point towards the future, like where software and systems are going rather than looking to the past, right? Because things are changing very, very rapidly in the field.”

A pedagogical approach

For the Spring 2026 semester, 68 students were enrolled in CS 351. The four cloud assignments that Couetil inherited for the course were functional and highly informative. Each one was very technician-oriented, delivering the information needed to conduct straightforward cloud computing tasks. The problem, Couetil felt, was that this had limited application in the real world.

“So much of software engineering is taking on a problem you need to solve while understanding the constraints. For the application you are going to build, how does your goal inform your method and the final software structure? In order to teach this, I decided to fully re-evaluate each of the four cloud assignments, maintaining the course spirit but implementing real-world learning motivation and a beautiful, engaging reading experience with pedagogical goals in mind.”

The core innovation for the cloud computing coursework was the utilization of auto-grading. The purpose of auto-grading is to provide students with feedback-rich assignments that can scale to large class sizes without placing undue burden on the instructional staff. Each assignment was iterative, allowing students to submit, receive auto-graded feedback, and resubmit until they achieved a satisfactory result. By leveraging auto-grading, the course incorporated a mastery-learning approach to the material. Couetil took this core innovation and redesigned the coursework with updated cloud computing tools, a more appealing visual layout, and a purposeful outline that led students from a Minimum Viable Product to Exit for a fictional startup company.

“I really wanted to take a design-driven approach to the cloud assignments,” says Couetil. “So I really worked on the typography, the layout. I wanted to understand the pedagogical approach. I also wanted there to be a storyline to engage students and motivate them to perform the assignments. So I crafted the story of a startup called Bird AI, helping bring bird detection to the masses.”

Using this layout, Couetil taught students production-level cloud computing architectures, as well as why you would choose them over other options. He added “deep dive” widgets to the course, giving in-depth information on specific technical topics. He also added “food for thought” widgets that forced students to reflect on why they chose a certain software and whether it worked better than a previous option for the assignment. Having the students question the reasons behind their software stack is important because they will constantly be making these decisions throughout their careers as software engineers.

“For the CS 351 course, I introduced students to application architectures that a startup or software company uses in the real-world. The idea was to guide them through technology choices that are robust enough to get them up and running, and then the problem is theirs to solve with their application. But they don’t have to worry about which technology to pick, or whether they are painting themselves into a corner with their choices. I give them robust options and show them the evolution of that technology, then they can make the best decision for solving their individual problem.”

Innovation at Scale

Aside from the auto-grading component of the course, Couetil delivered innovation to teaching and learning in two other forms: student usage and performance metrics and AI discussion board responses.

The first cloud computing assignment sparked Couetil’s curiosity. He realized that he wanted to know how students were doing, how often they were working on things, how long it was taking them, when during the week they started and finished, what their scoring progression was, etc. Couetil felt he could use these metrics to help craft better assignments later in the semester. So, to collect the information, he used an AI coding tool to help build an instructional website that connected to the assignments.

“I developed an instructional site, which was basically a web application attached to a database,” says Couetil, “and started collecting a bunch of data about student engagement with assignments. It would collect student submissions, taking snapshots of their AWS accounts (the cloud provider they used for learning in the course). We kept transaction logs of every single auto-grader attempt, so if a student came to us and said, ‘Hey, why did I get this grade?’ we could point to the exact reason.”

Couetil continues, “Using this data, I would craft visualizations, summaries, and course management tools. It was very helpful to track student results over time—you know, students submitted once, they got a 50%; students submitted twice, they made it to 60. 8 submissions later, they finally made it to 100—that kind of information. And with that data, I started deriving a lot of metrics. From there, it was really easy to estimate how much time a student spends on an assignment once they start submitting things, because you can kind of judge and guess working sessions.”

Those metrics then allowed Couetil to develop better course materials throughout the semester. The data also lent itself unexpectedly to the second innovation Couetil introduced to the course.

The CS 351 class had a discussion board where students could ask questions or communicate issues they may be having with their assignments. As the TA, part of Couetil’s job was to monitor the discussion board and assist students with their problems. Anyone who has taken a course involving online discussion boards knows that response times are iffy. Sometimes you may get an answer immediately; other times it could take days. Couetil wanted to solve that problem by adding an AI reply bot to the discussion board. For that, he turned to RCAC’s Purdue GenAI Studio.

Purdue GenAI Studio is a large language model (LLM) service that makes open-source LLM models like LLaMA accessible to anyone at Purdue. Unlike other LLM services, Purdue GenAI Studio is hosted entirely on-premises using resources within Purdue’s community cluster supercomputers, giving researchers more democratized access to LLMs, as well as more control.

“I had been playing around with Purdue Gen AI Studio, which I thought was really, really cool,” says Couetil. “It was really easy for me to log in, get an API key, and start playing around with discussion board summaries. But next, I realized that because I had all this data on what students are trying to achieve, the assignment documents, their progress towards that goal, and their submission attempts, Purdue GenAI Studio could actually be really useful for debugging.”

Couetil used Claude Code to scrape the entire discussion board and create a clone that would sync every 5 minutes. When a student posted a question in an assignment category, the system pulled their latest submission data, the assignment text, and the starter code and fed them into the LLM model of choice. This ensured the AI reply bot had the full context required to answer the student’s question. Couetil also evaluated multiple models to determine which worked best for this application, thanks to Purdue GenAI Studio’s robust selection of models.

“Purdue GenAI Studio was really nice to work with because it has a lot of different model types available. So I could spin off parallel jobs and then evaluate the responses from multiple models at once to determine what was the best one in terms of latency, in terms of quality response, and in terms of ability to actually identify the core problem that the student was experiencing.”

Adding in the AI discussion board responses was a boon to the course. Students could quickly receive answers to their questions, helping to problem-solve simpler issues they were having on assignments. This let them focus on system implementation and engineering decision-making rather than debugging one-off software errors. Couetil still checked and responded to the discussion board requests, but the AI reply bot enabled faster, more efficient workflows for the students, while allowing tougher questions to be addressed by Couetil himself.

The CS 351 course was a success, both for the 68 students who took the class and for Couetil. While completing his senior capstone project, Couetil developed four cloud computing assignments, wrote 16 weekly reports, and shed light on innovative ways that AI can support teaching and learning. He has since gone on to graduate from Purdue and start a new role as a Solutions Engineer Intern at Cloudflare. To learn more about Couetil’s project, please visit: Senior Project in Cloud Computing

If you are interested in learning more about how RCAC can help you utilize AI in the classroom, please connect with our Research Software Engineering Center.

RCAC operates the centrally-maintained research computing resources at Purdue University, providing access to leading-edge computational and data storage systems as well as expertise and support to Purdue faculty, staff, and student researchers. To learn more about HPC and how RCAC can help you, please visit: https://www.rcac.purdue.edu/ or reach out to rcac-help@purdue.edu to request consultation.

Written by: Jonathan Poole, poole43@purdue.edu

As the renovation and capacity improvement project in the MATH datacenter moves into its final stages, a planned maintenance outage is required to continue bringing the newly installed power and cooling infrastructure online. This work is part of a broader renovation that will result in a 32% increase in floor space, a 60% increase in usable power, and a two-fold increase in cooling capacity — all crucial facility ingredients needed to continue providing world-class high-performance computing resources to Purdue faculty and the nation.

**Outage Window: **Saturday, September 19, 2026, 12:00 AM – Sunday, September 20, 2026, 6:00 PM

What will remain online

The following resources are not affected by this power work and will remain available throughout the maintenance window:

• Data Depot and Data Depot Object
• ScienceDMZ
• Scholar
• Fortress
• HubZero
• Hammer
• Weber

What will go offline

The following resources, including their associated Data Depot storage and Data Depot Object allocations, will be unavailable during the outage window and will return to service gradually once the power work is complete:

• GenAI Studio
• Geddes
• Anvil
• Gautschi
• Gilbreth
• Bell
• Negishi
• Rowdy
• Rossmann

How does this affect you?

Jobs on the affected clusters will not run, and new jobs will not start during this window. Jobs that are expected to not complete before the maintenance begins will not start until after the maintenance window ends. Resources listed above as remaining online will continue to operate normally throughout.

Questions

If you have questions about this outage or need help from our support staff, please contact rcac-help@purdue.edu.

Best, RCAC

As of 3:30PM on August 16th 2026, all clusters with the exception of Gilbreth have been brought back online.

As the renovation and capacity improvement project in the MATH datacenter moves into its final stages, two planned maintenance outages are required to begin to utilize the newly installed power and cooling infrastructure. The MATH renovation will result in a 32% increase in floor space, a 60% increase in usable power, and a two-fold increase in cooling capacity, all of which are crucial facility ingredients needed to continue to provide world-class high-performance computing resources to Purdue faculty and the nation.

Here you can see the project’s progress with newly added floor space to accommodate our next HPC investment, though the new showcase window.

The first power outage is planned for Saturday, August 15, 2026, 12 AM through Sunday August 16, 2026, 6 PM. All clusters, storage, and gateway services such as GenAI Studio will be unavailable during this window and will return to service gradually once the power work is complete:

Data Depot, Geddes. and GenAI studio will return online as soon as power is available Sunday evening and will be ready for the work week.

All other HPC resources will return to service throughout the day and evening starting Monday.

Gilbreth cluster is scheduled for regular maintenance, including operating system patches, on August 18 and will return to service by 8 PM on that day.

The second power outage is planned for Saturday, September 19, 2026, 12 AM through Sunday, September 20, 2026, 6 PM. Additional details for the September maintenance will be shared at a later date.

How does this affect you?

All clusters, storage systems, and gateways will be unavailable during the power outage. Jobs will not run and new jobs will not start during this window. Jobs that are expected to not complete by the start of the maintenance will not start until after the maintenance window.

Questions

If you have questions about this outage or need help from our support staff, please contact rcac-help@purdue.edu.

**Issue: **Some users may not see Microsoft Authenticator push prompts unless they manually open the app. This can cause sign-ins to time out.

Workaround: If you do not see a push notification, open the Microsoft Authenticator app and approve the pending request. Also, please verify that your default sign-in method is set to ‘App based Authentication – notification’ You can follow the steps in this Knowledge Base article to check and update your settings: https://service.purdue.edu/TDClient/32/Purdue/KB/ArticleDet?ID=1788

Still Need Help? - Contact us at rcac-help@purdue.edu

Beginning May 11, 2026, RCAC will move from Duo Mobile to Microsoft Authenticator for logging in to Purdue’s research computing and supercomputing systems.

To ensure uninterrupted access, please complete the steps below before May 11.

What you need to do:

Enroll in Microsoft Multi-Factor Authentication (MFA) using the Microsoft Authenticator app (if you have not already)

Set your default sign-in method in Microsoft MFA to your preferred method

After May 11, Duo Mobile will no longer work for accessing RCAC systems.

Please contact rcac-help@purdue.edu If you have any questions or need help.

All RCAC systems and Research Network services will remain unavailable during this extended window.

We appreciate your continued patience as we complete these critical upgrades to improve RCAC infrastructure reliability and performance.

For assistance, questions, or concerns, please contact rcac-help@purdue.edu.

Impact To You: At this time, you may notice latency or brief disruptions when accessing certain on-campus or external resources, especially during peak usage periods.

We appreciate your patience while we work to fully resolve the underlying problem and restore normal network performance. We will provide an update by 5:00PM EST today or sooner.

Research Computing staff members will monitor the status of all computing and data resources in an effort to ensure continuous availability.

Research Computing staff members will monitor the ticketing system throughout the holiday period and answer critical issues and problems. Non-critical user issues and questions will be addressed beginning January 5th, 2026. There will also be no coffee hour consultations during this break.

Scratch file purging (on community clusters with scratch space) will continue as normal during the break, so be sure to archive your files in scratch storage. This does not apply to Data Depot or home directories -- only scratch storage.

Have a wonderful break, everyone, and we look forward to great things in the new year!