Deployed 1b86a14 with MkDocs version: 1.1.2

misc/pelican/index.html

@@ -61,7 +61,7 @@
     <div data-md-component="skip">
 
 
-        <a href="#uprade-of-the-osdf-origin-to-pelican-for-collaborations" class="md-skip">
+        <a href="#upgrade-of-the-osdf-origin-to-pelican-for-collaborations" class="md-skip">
           Skip to content
         </a>
 
@@ -444,10 +444,23 @@
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
 
         <li class="md-nav__item">
-  <a href="#uprade-of-the-osdf-origin-to-pelican-for-collaborations" class="md-nav__link">
-    Uprade of the OSDF origin to Pelican for Collaborations
+  <a href="#upgrade-of-the-osdf-origin-to-pelican-for-collaborations" class="md-nav__link">
+    Upgrade of the OSDF origin to Pelican for Collaborations
   </a>
 
+    <nav class="md-nav" aria-label="Upgrade of the OSDF origin to Pelican for Collaborations">
+      <ul class="md-nav__list">
+
+          <li class="md-nav__item">
+  <a href="#transition-from-stashcp-to-pelican" class="md-nav__link">
+    Transition from Stashcp to Pelican
+  </a>
+
+</li>
+
+      </ul>
+    </nav>
+
 </li>
 
     </ul>
@@ -465,7 +478,7 @@
 
                   <h1>Pelican</h1>
 
-                <h2 id="uprade-of-the-osdf-origin-to-pelican-for-collaborations">Uprade of the OSDF origin to Pelican for Collaborations<a class="headerlink" href="#uprade-of-the-osdf-origin-to-pelican-for-collaborations" title="Permanent link">&para;</a></h2>
+                <h2 id="upgrade-of-the-osdf-origin-to-pelican-for-collaborations">Upgrade of the OSDF origin to Pelican for Collaborations<a class="headerlink" href="#upgrade-of-the-osdf-origin-to-pelican-for-collaborations" title="Permanent link">&para;</a></h2>
 <p>The OSG Collab AP had an <strong>OSDF</strong> door deployed on the access point (ap23.uc.osg-htc.org) that provided users with authenticated access to a Ceph cluster, that provides high capacity storage to shared project directories. HTCondor jobs running in the OSPool at remote <strong>Execution Points (EPs)</strong> (remote worker nodes) can access the filesystem either via a client tool or via an HTCondor plugin that is invoked in their submit scripts. The storage is also mounted on the AP at /ospool/uc-shared/project. </p>
 <p>On <strong>11/21/2024</strong>, OSG/PATh staff migrated the OSDF door from the OSG Collab AP to a separate infrastructure to allow upgrading the origin to the Pelican Platform (https://pelicanplatform.org/) and provide shared project access to users at other APs (ap20.uc.osg-htc.org and ap21.uc.osg-htc.org).</p>
 <p>The migration should have been transparent to the OSG Collab AP. If using the HTCondor plugin, no changes are needed in your submission scripts. For reference, the general purpose documentation found here (https://portal.osg-htc.org/documentation/htc_workloads/managing_data/osdf/) is also applicable to the users of the OSG Collab AP. It describes using the HTCondor plugin to move data to and from the OSDF/Pelican Origin. </p>
@@ -479,15 +492,17 @@ <h2 id="uprade-of-the-osdf-origin-to-pelican-for-collaborations">Uprade of the O
 <p>Include the following in your submit script for an OSPool job to transfer a file to your project directory at the origin from an EP enviroment:</p>
 <p>OSDF_LOCATION = osdf:///ospool/uc-shared/project/<your_project>/<file>
 transfer_input_files = $(OSDF_LOCATION)/<file>
-The upgrade to the Pelican platform, which uses federated urls for the origin, still keeps the same prefix <em>osdf://</em>. After the upgrade, <em>osdf://</em> simply points to <em>pelican://osg-htc.org/</em> </p>
+Note: The Pelican platform uses federated URLs for the origin, but the prefix osdf:// remains unchanged. After the upgrade, osdf:// maps to pelican://osg-htc.org/.</p>
 </li>
 </ol>
-<p>If you are using a client in your runtime script at the EP, then the previous tool, <strong>stashcp</strong>, will continue to work as long as the version is &gt; 6.12 except recursive access (<em>-r</em> flag). Thefore, we recommend that groups migrate to using the pelican client instead. </p>
+<h3 id="transition-from-stashcp-to-pelican">Transition from Stashcp to Pelican<a class="headerlink" href="#transition-from-stashcp-to-pelican" title="Permanent link">&para;</a></h3>
+<p>If your runtime scripts at the EP rely on the stashcp tool, it will continue to work (version 6.12 or higher), except for recursive access (-r flag). However, we recommend transitioning to the Pelican client for improved compatibility and features.</p>
+<p>Command Comparison</p>
 <table>
 <thead>
 <tr>
-<th>stashcp</th>
-<th>pelican</th>
+<th>Stashcp Command</th>
+<th>Pelican equivalent</th>
 </tr>
 </thead>
 <tbody>