<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sovereignty | 2i2c</title><link>https://deploy-preview-614--2i2c-org.netlify.app/tag/sovereignty/</link><atom:link href="https://deploy-preview-614--2i2c-org.netlify.app/tag/sovereignty/index.xml" rel="self" type="application/rss+xml"/><description>Sovereignty</description><generator>Hugo Blox Builder (https://hugoblox.com)</generator><language>en-us</language><lastBuildDate>Tue, 20 Jan 2026 00:00:00 +0000</lastBuildDate><image><url>https://deploy-preview-614--2i2c-org.netlify.app/media/sharing.png</url><title>Sovereignty</title><link>https://deploy-preview-614--2i2c-org.netlify.app/tag/sovereignty/</link></image><item><title>Enabling CloudBank to safely manage their own cluster infrastructure</title><link>https://deploy-preview-614--2i2c-org.netlify.app/blog/cloudbank-self-service/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://deploy-preview-614--2i2c-org.netlify.app/blog/cloudbank-self-service/</guid><description>&lt;p>We recently enabled
&lt;a href="https://deploy-preview-614--2i2c-org.netlify.app/collaborators/cloudbank/" >CloudBank&lt;/a> to run Terraform changes for their cluster without needing to wait on 2i2c engineers for each request. They run 50+ hubs for various community colleges, and we want to enable them to self serve as much of that as possible. When we introduced home directory quotas, they were no longer able to set up hubs by themselves without help from 2i2c engineers. Our goal was to empower them to be able to set up new hubs in a safe way while still benefiting from the home directory limits work.&lt;/p>
&lt;figure id="figure-cloudbank-simplifies-cloud-access-for-computer-science-research-and-education">
&lt;div class="d-flex justify-content-center">
&lt;div class="w-100" >&lt;img alt="CloudBank simplifies cloud access for computer science research and education." srcset="
/blog/cloudbank-self-service/featured_hu47b0024f802a2569dc8459bb45285f77_14544_3e2af71d895a3af46826ba1d224a2bf2.webp 400w,
/blog/cloudbank-self-service/featured_hu47b0024f802a2569dc8459bb45285f77_14544_d054f36eb6161bf5a999ff8a409ac162.webp 760w,
/blog/cloudbank-self-service/featured_hu47b0024f802a2569dc8459bb45285f77_14544_1200x1200_fit_q75_h2_lanczos_3.webp 1200w"
src="https://deploy-preview-614--2i2c-org.netlify.app/blog/cloudbank-self-service/featured_hu47b0024f802a2569dc8459bb45285f77_14544_3e2af71d895a3af46826ba1d224a2bf2.webp"
width="411"
height="88"
loading="lazy" data-zoomable />&lt;/div>
&lt;/div>&lt;figcaption>
CloudBank simplifies cloud access for computer science research and education.
&lt;/figcaption>&lt;/figure>
&lt;p>To do this safely, we needed to avoid granting access to shared Terraform state that could impact other communities. Following
&lt;a href="https://github.com/2i2c-org/infrastructure/pull/6797#pullrequestreview-3246004031" target="_blank" rel="noopener" >Yuvi&amp;rsquo;s suggestion&lt;/a>, we migrated CloudBank&amp;rsquo;s Terraform state to CloudBank’s own GCP project so that infrastructure changes from the CloudBank team are isolated to their cluster only, making this safe to try. This unblocks CloudBank to run changes like &lt;code>terraform plan&lt;/code> and &lt;code>terraform apply&lt;/code> themselves, meaning that CloudBank can deploy and update a hub without 2i2c engineers in the loop.&lt;/p>
&lt;p>This is a good example of how we aim to balance &lt;strong>community autonomy&lt;/strong> with &lt;strong>infrastructure safety&lt;/strong>. CloudBank can now self-serve routine operations while our broader infrastructure remains protected.&lt;/p>
&lt;h2 id="learn-more">
Learn more
&lt;a class="header-anchor" href="#learn-more">#&lt;/a>
&lt;/h2>&lt;ul>
&lt;li>
&lt;a href="https://github.com/2i2c-org/infrastructure/issues/6795" target="_blank" rel="noopener" >The infrastructure issue describing this work&lt;/a>&lt;/li>
&lt;li>
&lt;a href="https://github.com/2i2c-org/infrastructure/pull/7339" target="_blank" rel="noopener" >A hub deployed by CloudBank using this workflow&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="acknowledgements">
Acknowledgements
&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
&lt;/h2>&lt;ul>
&lt;li>Thanks to Sean Morris and the
&lt;a href="https://deploy-preview-614--2i2c-org.netlify.app/collaborators/cloudbank/" >CloudBank&lt;/a> team at
&lt;a href="https://deploy-preview-614--2i2c-org.netlify.app/collaborators/bids/" >UC Berkeley&lt;/a> for collaborating on this workflow.&lt;/li>
&lt;/ul></description></item><item><title>Giving CCAD more control over data science infrastructure via a Catalyst Project hardware exchange</title><link>https://deploy-preview-614--2i2c-org.netlify.app/blog/catalyst-hardware-exchange/</link><pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate><guid>https://deploy-preview-614--2i2c-org.netlify.app/blog/catalyst-hardware-exchange/</guid><description>&lt;p>2i2c has successfully completed a hardware exchange with Universidad Nacional de Córdoba&amp;rsquo;s
&lt;a href="https://supercomputo.unc.edu.ar/" target="_blank" rel="noopener" >Centro de Computación de Alto Desempeño (CCAD)&lt;/a> through funding from the
&lt;a href="https://catalystproject.cloud/" target="_blank" rel="noopener" >Catalyst Project&lt;/a>. CCAD used funding to purchase new on-prem computing infrastructure, significantly expanding their computing capabilities.&lt;/p>
&lt;p>This exchange reduces CCAD&amp;rsquo;s reliance on ongoing cloud funding while giving them direct control over their infrastructure. The new hardware will support a scalable JupyterHub deployment and provide valuable training opportunities for researchers who may work with local computing resources.&lt;/p>
&lt;h2 id="learn-more">
Learn more
&lt;a class="header-anchor" href="#learn-more">#&lt;/a>
&lt;/h2>&lt;ul>
&lt;li>
&lt;a href="https://supercomputo.unc.edu.ar/2025/09/02/colgando-a-boogie/" target="_blank" rel="noopener" >CCAD&amp;rsquo;s blog post about the hardware deployment&lt;/a>&lt;/li>
&lt;li>
&lt;a href="https://catalystproject.cloud/" target="_blank" rel="noopener" >The Catalyst Project&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="acknowledgements">
Acknowledgements
&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
&lt;/h2>&lt;ul>
&lt;li>
&lt;a href="https://deploy-preview-614--2i2c-org.netlify.app/collaborators/czi/" >Chan Zuckerberg Initiative&lt;/a> for their
&lt;a href="https://deploy-preview-614--2i2c-org.netlify.app/collaborators/catalyst/" >Catalyst Project award&lt;/a>&lt;/li>
&lt;li>
&lt;a href="https://supercomputo.unc.edu.ar/" target="_blank" rel="noopener" >CCAD&lt;/a> for their collaboration on this hardware exchange&lt;/li>
&lt;/ul></description></item></channel></rss>