Merge Split Branch

preview-update-submodules/fellowships/index.html

@@ -247,14 +247,14 @@ <h2 class="mt-1">Applications are now open!</h2>
 
       <h2 id="featured-fellow">Featured Fellow</h2>
 
-      <div id="pratham-patel" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
+      <div id="ben-staehle" class="bg-white team-card justify-content-center mb-3 flex-grow-1">
     <div class="uw-card-content shadow">
         <div class="row">
             <div class="col-3">
                 <div class="overflow-hidden d-flex justify-content-center">
 
 
-                    <img src="/web-preview/preview-update-submodules/staff-list/images/pratham_patel.jpg" alt="Headshot for Pratham Patel" />
+                    <img src="/web-preview/preview-update-submodules/staff-list/images/ben_staehle.jpg" alt="Headshot for Ben Staehle" />
 
                 </div>
             </div>
@@ -263,27 +263,28 @@ <h2 id="featured-fellow">Featured Fellow</h2>
                     <div>
                         <h2 class="uw-mini-bar mb-0 mt-3">
 
-                            Pratham Patel
+                            Ben Staehle
 
                         </h2>
-                        <div><h6 class="mt-2">Mentor(s):</h6> Brian Lin</div>
+                        <div><h6 class="mt-2">Mentor(s):</h6> Joe Bartowiak</div>
                     </div>
                 </div>
             </div>
             <div class="col-12">
-                <h4 class="mt-3">Enhancing container image build system</h4>
+                <h4 class="mt-3">Tracking server inventory and elevation</h4>
                 <div class="pt-2">
-                    <p>Container images are a widely used technology to package and distribute 
-software and services for use in systems such as Docker or Kubernetes.
-The PATh project builds hundreds of these images on a weekly basis but 
-the build system needs improvement to support more images and additional
-use cases. This project will focus on taking the existing system and 
-adding configurable, per-image build options. After a successful summer,
-the student fellow will gain skills in Docker containers, GitHub actions, and Bash.</p>
+                    <p>The CHTC maintains over 1,000 servers on the UW–Madison campus and 
+across the country. Keeping track of server elevation (datacenter 
+and rack location), serial numbers, asset tags is a challenge that 
+is always in need of improvement. This project will focus on taking 
+existing data from the CHTC hardware monitoring system and automatically 
+exporting it to other systems such as Google spreadsheets or ITAdvisor.
+After a successful summer, the student fellow will gain skills in 
+Python and monitoring and Google Docs APIs.</p>
 
                 </div>
                 <div>
-                    <a class="btn btn-primary" href="./reports/2024/pratham-patel">Read Final Report</a>
+                    <a class="btn btn-primary" href="./reports/2024/ben-staehle">Read Final Report</a>
                 </div>
             </div>
         </div>

preview-update-submodules/people.html

@@ -1404,6 +1404,32 @@ <h2 class="uw-mini-bar">
 </div>
                 </div>
 
+                <div class="col-xl-2 col-md-3 col-sm-4 col-6">
+                    <div class="bg-white team-card justify-content-center mb-3 flex-grow-1">
+    <div class="uw-card-content">
+        <div class="img-container" class="overflow-hidden d-flex justify-content-center">
+
+
+            <img src="/web-preview/preview-update-submodules/staff-list/images/patrick_brophy.jpg" alt="Headshot for Patrick Brophy">
+
+        </div>
+        <div class="uw-card-copy">
+            <div>
+                <h2 class="uw-mini-bar">
+
+                    Patrick Brophy
+
+                </h2>
+                <p>Student Research Software Engineer</p>
+            </div>
+            <div>
+                <span class="institution">Morgridge Institute for Research</span>
+            </div>
+        </div>
+    </div>
+</div>
+                </div>
+
         </div>
         <h2 class="uw-mini-bar">Previous Staff</h2>
         <div class="row gx-1">

preview-update-submodules/staff-list/patrick_brophy_student_role.yml

@@ -0,0 +1,7 @@
+name: Patrick Brophy
+title: Student Research Software Engineer
+institution: Morgridge Institute for Research
+status: Student
+organizations:
+  - chtc
+image: images/patrick_brophy.jpg

preview-update-submodules/uw-research-computing/data-recovery-fall2024.html

@@ -235,30 +235,6 @@ <h1 class="uw-mini-bar mb-4">
 
 <p>We recognize that this ongoing outage and accompanying data loss is disruptive to important work. Our plan to bring systems and data back online is outlined below.</p>
 
-<h2 id="chtc-next-steps-and-timeline">CHTC Next Steps and Timeline</h2>
-
-<ul>
-  <li>Nov 25 - 27: New data backend for /staging and /projects
-    <ul>
-      <li>This week (Nov 25-27), we will create a new data store to serve the <code>/staging</code> and <code>/projects</code> directories. Initially, <em>there will be no data inside these directories.</em> This new data backend for the <code>/staging</code> and <code>/projects</code> directories will be used for CHTC data storage moving forward and will be usable in jobs <em>immediately</em> once it is available.</li>
-    </ul>
-  </li>
-  <li>Nov 25 - Dec 9: Recovering data from <code>/staging</code> directories
-    <ul>
-      <li>We will run multiple recovery processes on the old data store over the next 1-2 weeks. Once each recovery process is complete, CHTC users will be able to access recovered data and copy it to the new data store. CHTC will not overwrite or replace data created in the meantime.  <em>We are still developing the mechanism for this process and will provide more information as it becomes available.</em></li>
-    </ul>
-  </li>
-  <li>Dec 9 onward: Recovering data from <code>/projects</code>
-    <ul>
-      <li>This will be the same process as recovering data from <code>/staging</code>.</li>
-    </ul>
-  </li>
-</ul>
-
-<p><strong>Note that this timeline means that you will not know how much of your data from the previous data store was lost or recovered until after Dec 2, at the earliest.</strong>  Consider re-transferring or reproducing the data instead of waiting for potential recovery.</p>
-
-<p>Evaluation and restoration of HTC <code>/software</code> directories will happen after the process above is complete.</p>
-
 <h2 id="user-next-steps">User Next Steps</h2>
 
 <h3 id="resume-running-jobs">Resume Running Jobs</h3>
@@ -281,7 +257,31 @@ <h3 id="resume-running-jobs">Resume Running Jobs</h3>
 
 <h3 id="access-recovered-data">Access Recovered Data</h3>
 
-<p>Instructions coming the week of Dec 2 or Dec 9.</p>
+<h4 id="recover-staging-and-software-data">Recover <code>/staging</code> and <code>/software</code> data</h4>
+
+<p>We are in the final stages of getting the recovered /staging data ready to share. There should be an update 12/11 with details about accessing recovered /staging data as well as an updated timeline for the rest of the recovery process.</p>
+
+<h2 id="chtc-next-steps-and-timeline">CHTC Next Steps and Timeline</h2>
+
+<ul>
+  <li>Nov 25 - 27: New data backend for /staging and /projects
+    <ul>
+      <li>During the week of Nov 25-27, we created a new data store to serve the <code>/staging</code> and <code>/projects</code> directories. Initially, <em>there is no data inside these directories.</em> This new data backend for the <code>/staging</code> and <code>/projects</code> directories will be used for CHTC data storage moving forward and is usable in jobs <em>immediately</em>.</li>
+    </ul>
+  </li>
+  <li>Nov 25 - Dec 10: Recovering data from <code>/staging</code> directories
+    <ul>
+      <li>We have run multiple recovery processes on the old data store. Once each recovery process is complete, CHTC users will be able to access recovered data and copy it to the new data store. CHTC will not overwrite or replace data created in the meantime.  <em>We are still developing the mechanism for this process and will provide more information as it becomes available.</em></li>
+    </ul>
+  </li>
+  <li>Dec 11 onward: Recovering data from <code>/projects</code>
+    <ul>
+      <li>This will be the same process as recovering data from <code>/staging</code>.</li>
+    </ul>
+  </li>
+</ul>
+
+<p><strong>Note that this timeline means that you will not know how much of your data from the previous data store was lost or recovered until after Dec 2, at the earliest.</strong>  Consider re-transferring or reproducing the data instead of waiting for potential recovery.</p>
 
 <h2 id="stay-informed">Stay Informed</h2>