Updated hardware documentation and notebook agreement

.dockerignore

@@ -1,2 +1,2 @@
 Dockerfile
-node_modules
+node_modules

Dockerfile

@@ -12,4 +12,7 @@ RUN git submodule update --init && \
 
 FROM nginx:latest
 
-COPY --from=BUILD /home/node/build/dist/ /usr/share/nginx/html/
+COPY nginx.conf /etc/nginx/nginx.conf
+COPY --from=BUILD /home/node/build/dist/ /usr/share/nginx/html/
+
+EXPOSE 80

nginx.conf

@@ -0,0 +1,31 @@
+user  nginx;
+worker_processes  auto;
+
+error_log  /var/log/nginx/error.log notice;
+pid        /var/run/nginx.pid;
+
+events {
+    worker_connections  1024;
+}
+
+http {
+    include       /etc/nginx/mime.types;
+    default_type  application/octet-stream;
+
+    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
+                      '$status $body_bytes_sent "$http_referer" '
+                      '"$http_user_agent" "$http_x_forwarded_for"';
+
+    access_log  /var/log/nginx/access.log  main;
+
+    sendfile        on;
+    #tcp_nopush     on;
+
+    keepalive_timeout  65;
+
+    port_in_redirect on;
+
+    gzip  on;
+
+    include /etc/nginx/conf.d/*.conf;
+}

src/_includes/partials/global-notify.njk

@@ -1,4 +1,4 @@
 <div role="alert" class="alert alert-warning">
   <svg xmlns="http://www.w3.org/2000/svg" class="stroke-current shrink-0 h-6 w-6" fill="none" viewBox="0 0 24 24"><path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 9v2m0 4h.01m-6.938 4h13.856c1.54 0 2.502-1.667 1.732-3L13.732 4c-.77-1.333-2.694-1.333-3.464 0L3.34 16c-.77 1.333.192 3 1.732 3z" /></svg>
-  <span>Warning: This service is BETA TESTING - Hex is currently stable enough for 'real work', but data is not persisted between instances, so back up your work often! No service guarantee is implied.</span>
+  <span>Warning: This service is BETA TESTING - Hex is currently stable enough for 'real work', but currently runs no automated backups. Back up often! No service guarantee is implied.</span>
 </div>

src/_includes/partials/menu.njk

@@ -18,7 +18,6 @@
         <ul class="bg-base-200 rounded-none">
             <li><a href="/pages/projects">Project Catalog</a></li>
             <li><a href="/pages/hardware">Hardware Information</a></li>
-            <li><a href="/pages/status">Development Status</a></li>
             <li><a href="/pages/history">History</a></li>
         </ul>
     </details>

src/index.md

@@ -5,7 +5,7 @@ title: The UCREL-Hex Temporary Landing Page
 
 ## What is 'Hex'?
 Hex is a collection of GPU equipped hosts onto which single- multi- or GPU-processor jobs can be executed.
-Currently 11 of these hosts are continuously available (220 CPU, 11 GPU and 352GiB of RAM) with plans to extend these up to 14 hosts with the inclusion of 3 dedicated GPU carrier hosts and again with a further 160 machines similar to the original 11 available for overnight runs on a <i>best effort</i> basis.
+The current, exact specification of all nodes can be found [on the hardware page](/pages/hardware) and we are actively looking to expand our capabilities overe time to align better with larger HPC systems.
 
 Hex _is not HEC_ - it is not yet another high-performance system, but is rather an modular development system, which attempts to reach feature parity with larger systems to allow students, researchers and staff to design software to run on [HEC](https://lancaster-hec.readthedocs.io/en/latest/index.html), [BEDE](https://n8cir.org.uk/bede/), [AWS](https://aws.amazon.com/), [Google Compute](https://cloud.google.com/products/compute?hl=en), and other systems, but in a much more development-friendly environment.
 

src/pages/history.md

@@ -24,7 +24,7 @@ title: UCREL-Hex History
     <div class="timeline-end mb-10">
       <time class="font-mono italic">January 2023</time>
       <div class="text-lg font-black">First 'Core' Nodes Purchased</div>
-      The first core 11 nodes are provisioned, linked into the swarm and installed into the server room at Infolab21.
+      The first core 11 nodes are provisioned, linked into the cluster and installed into the server room at Infolab21.
       <img class="rounded-lg" src="/assets/img/hex-phase-1.jpg" alt="11 Hex nodes in their rack cabinet">
     </div>
     <hr />
@@ -35,9 +35,9 @@ title: UCREL-Hex History
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor" class="h-5 w-5"><path fill-rule="evenodd" d="M10 18a8 8 0 100-16 8 8 0 000 16zm3.857-9.809a.75.75 0 00-1.214-.882l-3.483 4.79-1.88-1.88a.75.75 0 10-1.06 1.061l2.5 2.5a.75.75 0 001.137-.089l4-5.5z" clip-rule="evenodd" /></svg>
     </div>
     <div class="timeline-start md:text-end mb-10">
-      <time class="font-mono italic">Soon?</time>
+      <time class="font-mono italic">July 2024</time>
       <div class="text-lg font-black">The 'Extended 3' Nodes</div>
-      Stephen Mander transfers control of his triple-GPU hardware over to the Hex swarm.
+      Three new 64 Core Intel Xeon Silver 4216 CPU @ 2.10GHz servers are linked into the cluster, each equipped with three NVIDIA RTX A5000 24GiB GPUs and represents a significant boost in performance for Hex.
     </div>
     <hr/>
   </li>

src/pages/jupyter/index.md

@@ -18,13 +18,13 @@ author: John Vidler
 > The Jupyter Notebook is the original web application for creating and sharing computational documents. It offers a simple, streamlined, document-centric experience.
 
 Primarily this service caters to **Data Scientists** who wish to use **Python-based** or **R-based** environments to process their data.
-Each instance is launched on one of Hex's worker nodes and can use up to 20 CPU cores, and approximately 32GB of RAM; however currently this service has no long-term storage backend, so uses ephemeral storage for short-term data retention. While this can store quite a large amount of data, it will be lost when an instance is restarted or shut down.
+Each instance is launched on one of Hex's worker nodes and can use up to 20 CPU cores, and approximately 32GB of RAM. The storage for notebooks is handled by a centralised VM `ucrel-hex-nas` which provides synchronised storage between instances. It is however somewhat limited in its current configuration, and we are looking to upgrade this to a colocated storage server in the future.
 
-We're working on fixing this in a future release, but for the moment, if you have specific requirements or concerns, please contact us via the links below.
+If you have specific requirements or concerns, please contact us via the links below.
 
 ## User Declaration
 
-I understand that no storage backend is currently configured for this service, so **when an instance is stopped or restarted all data will be lost**.
+I understand that **this is a BETA service**, and while persistent storage between instances is now provided, no backups are currently available so **users are responsible for their own data retention**.
 It is the user's responsibility to ensure a suitable backup strategy is used to prevent unexpected data loss, and it is understood that this service is supplied with no guarantee, implied or otherwise.
 
 <form action="https://hub.ucrel-hex.scc.lancs.ac.uk/" method="get" class="w-full place-content-center grid">