You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: upgrade/index.html
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -981,7 +981,7 @@ <h1>Upgrade</h1>
981
981
982
982
<h3id="steps-for-upgrading">Steps for Upgrading<aclass="headerlink" href="#steps-for-upgrading" title="Permanent link">⚓︎</a></h3>
983
983
<divclass="admonition danger">
984
-
<pclass="admonition-title">Change in config & logging starting node 10.5.1</p>
984
+
<pclass="admonition-title">Change in config & logging starting node 10.5.x</p>
985
985
<p>Starting node 10.4.x, new cardano-tracer infrastructure was introduced for node , the use of this was disabled by default and thus - not as visible to users who may have missed the announcement. However, the legacy config/logging format has been said to be deprecated and could be retired in 10.6.x. Thus - we have shifted to minimum viable equivalent for newer config format.
986
986
We are excluding setting up of cardano-tracer, as we feel it's an overkill for an average SPO. Please consult <ahref="https://github.com/intersectmbo/cardano-node/blob/master/cardano-tracer/docs/cardano-tracer.md">official documentation</a> if you'd like to run cardano-tracer.</p>
987
987
<p>What this means, as a SPO:</p>
@@ -993,7 +993,7 @@ <h3 id="steps-for-upgrading">Steps for Upgrading<a class="headerlink" href="#ste
993
993
</ul>
994
994
<p>Lastly, given the changes above, we <strong>strongly</strong> recommend you to make sure you go through upgrade steps for your setup in a non-mainnet environment first!!</p>
995
995
</div>
996
-
<p>While this guide is last updated when adding support for node 10.5.1, it is meant to serve as a generic reference point for typical upgrades.</p>
996
+
<p>While this guide is last updated when adding support for node 10.5.2, it is meant to serve as a generic reference point for typical upgrades.</p>
997
997
<ul>
998
998
<li>Download the latest <code>guild-deploy.sh</code> (always double check syntax of the script with <code>guild-deploy.sh -h</code>). The scripts modified with user content (<code>env</code>, <code>gLiveView.sh</code>, <code>topologyUpdater.sh</code>, <code>cnode.sh</code>, etc) will be backed up before overwriting. More static files (genesis, submitapi, etc or some of the scripts themselves) will not be backed up, as they're not expected to be modified.</li>
999
999
</ul>
@@ -1005,7 +1005,7 @@ <h3 id="steps-for-upgrading">Steps for Upgrading<a class="headerlink" href="#ste
1005
1005
<li>
1006
1006
<p>Depending on node release, you may be able to simply perform an update-in-place of scripts and node, or for some cases, you may need to overwrite configs as well. Some Examples below:</p>
1007
1007
<ul>
1008
-
<li>Consider you're upgrading from 10.1.4 to 10.5.1, where config formats have changed. In this case, you'd want to overwrite your config files as well. You should follow changelog in node release notes to verify if you'd need to overwrite configs. Note that every time you do this, you may need to re-add your customisations - if any - to the relevant config files (typically - almost always, you'd have to update the topology.json when overwriting configs). There are backups created of original file in <code>"${CNODE_HOME}"/files</code> folder if you'd like to compare/reuse previous version.</li>
1008
+
<li>Consider you're upgrading from 10.1.4 to 10.5.2, where config formats have changed. In this case, you'd want to overwrite your config files as well. You should follow changelog in node release notes to verify if you'd need to overwrite configs. Note that every time you do this, you may need to re-add your customisations - if any - to the relevant config files (typically - almost always, you'd have to update the topology.json when overwriting configs). There are backups created of original file in <code>"${CNODE_HOME}"/files</code> folder if you'd like to compare/reuse previous version.</li>
0 commit comments