Deployed c44738a with MkDocs version: 1.1.2

misc/pelican/index.html

@@ -451,16 +451,16 @@
 </li>
 
         <li class="md-nav__item">
-  <a href="#htcondor-plugin-users-no-changes-are-needed-in-your-submission-scripts" class="md-nav__link">
-    HTCondor Plugin Users: No changes are needed in your submission scripts.
+  <a href="#htcondor-plugin-users" class="md-nav__link">
+    HTCondor Plugin Users:
   </a>
 
-    <nav class="md-nav" aria-label="HTCondor Plugin Users: No changes are needed in your submission scripts.">
+    <nav class="md-nav" aria-label="HTCondor Plugin Users:">
       <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 href="#client-tool-users-transition-from-stashcp-to-pelican" class="md-nav__link">
+    Client tool Users - Transition from Stashcp to Pelican
   </a>
 
 </li>
@@ -496,8 +496,8 @@ <h2 id="upgrade-of-the-osdf-origin-to-pelican-for-collaborations">Upgrade of the
 <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 was designed to be transparent to users of the OSG Collab AP.</p>
-<h2 id="htcondor-plugin-users-no-changes-are-needed-in-your-submission-scripts">HTCondor Plugin Users: No changes are needed in your submission scripts.<a class="headerlink" href="#htcondor-plugin-users-no-changes-are-needed-in-your-submission-scripts" title="Permanent link">&para;</a></h2>
-<p>The <a href="https://portal.osg-htc.org/documentation/htc_workloads/managing_data/osdf/">OSDF documentation</a> remains applicable and describes how to use the HTCondor plugin to move data to and from the OSDF/Pelican origin.</p>
+<h2 id="htcondor-plugin-users">HTCondor Plugin Users:<a class="headerlink" href="#htcondor-plugin-users" title="Permanent link">&para;</a></h2>
+<p>No changes are needed in your submission scripts. The <a href="https://portal.osg-htc.org/documentation/htc_workloads/managing_data/osdf/">OSDF documentation</a> remains applicable and describes how to use the HTCondor plugin to move data to and from the OSDF/Pelican origin.</p>
 <p>Here are key examples for transferring files using the HTCondor plugin:</p>
 <ol>
 <li>
@@ -509,7 +509,7 @@ <h2 id="htcondor-plugin-users-no-changes-are-needed-in-your-submission-scripts">
 </li>
 </ol>
 <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>
-<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>
+<h3 id="client-tool-users-transition-from-stashcp-to-pelican">Client tool Users - Transition from Stashcp to Pelican<a class="headerlink" href="#client-tool-users-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>