Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

upgrades: create a template guide #1812

Closed
Tracked by #1804
erwanor opened this issue Jan 6, 2023 · 5 comments · Fixed by #4245
Closed
Tracked by #1804

upgrades: create a template guide #1812

erwanor opened this issue Jan 6, 2023 · 5 comments · Fixed by #4245
Assignees
@conorsch
Labels
A-governance Area: Governance A-upgrades Area: Relates to chain upgrades _P-medium Medium priority
Milestone
Sprint 5

Comments

@erwanor
Copy link
Member

erwanor commented Jan 6, 2023 •
edited
Loading

We should create a template that specifies the different steps that one has to take in order to upgrade their full node. This document should recommend best practices such as creating multiple backups, checking the hash of migrated state, handling common setups (e.g. systemd etc.)
@erwanor erwanor mentioned this issue Jan 6, 2023
Open
19 tasks
@erwanor erwanor added the A-governance Area: Governance label Jan 6, 2023
@erwanor erwanor added this to Testnets Jan 6, 2023
@erwanor erwanor added this to the Network upgrades milestone Feb 8, 2023
@erwanor erwanor mentioned this issue Feb 8, 2023
Closed
@erwanor erwanor added help wanted Help on this issue is welcomed! good first issue A good issue for people without existing context on the project. on hold labels Feb 8, 2023
@erwanor
Copy link
Member Author

erwanor commented Feb 8, 2023

This is not immediately actionable since we have yet to begin work on #1804, but this could be a good first issue once the on-hold tag is removed, maybe worth bookmarking if that's interesting for you!

@zbuc zbuc moved this to Future in Testnets Mar 24, 2023
@erwanor erwanor changed the title Sketch out an upgrade document template upgrades: create a template guide Sep 11, 2023
@erwanor erwanor self-assigned this Sep 26, 2023
@aubrika aubrika added this to Penumbra Oct 30, 2023
@github-project-automation github-project-automation bot moved this to 🗄️ Backlog in Penumbra Oct 30, 2023
@hdevalence hdevalence removed help wanted Help on this issue is welcomed! good first issue A good issue for people without existing context on the project. on hold labels Feb 9, 2024
@aubrika aubrika added the on hold label Feb 9, 2024
@hdevalence hdevalence added the _P-medium Medium priority label Feb 9, 2024
@aubrika aubrika modified the milestones: Upgrades, Sprint 2 Mar 6, 2024
@cratelyn cratelyn added the A-upgrades Area: Relates to chain upgrades label Mar 12, 2024
@cratelyn cratelyn modified the milestones: Sprint 2, Sprint 3 Mar 18, 2024
@cratelyn cratelyn modified the milestones: Sprint 3, Sprint 2 Mar 18, 2024
@cratelyn cratelyn moved this from 🗄️ Backlog to Todo in Penumbra Mar 21, 2024
@erwanor erwanor assigned conorsch and unassigned erwanor Mar 22, 2024
@erwanor
Copy link
Member Author

erwanor commented Mar 22, 2024

@conorsch has been leading/driving the work on this front with the wiki entry

@erwanor erwanor moved this from Todo to In progress in Penumbra Mar 22, 2024
@aubrika aubrika modified the milestones: Sprint 2, Sprint 3 Mar 25, 2024
@conorsch
Copy link
Contributor

Was tracking this work as part of #3841, see details there. This will be resolved as soon as #4097 lands.

@conorsch conorsch mentioned this issue Mar 25, 2024
Merged
@cratelyn cratelyn modified the milestones: Sprint 3, Sprint 4 Apr 8, 2024
@conorsch
Copy link
Contributor

conorsch commented Apr 8, 2024

This is done, BUT we have changes to make as a result of feedback. Will close when those additions lands.

@conorsch conorsch moved this from In progress to Todo in Penumbra Apr 11, 2024
@conorsch
Copy link
Contributor

This is done, BUT we have changes to make as a result of feedback. Will close when those additions lands.

Picking this up, will have a revised version of the docs up by tomorrow.

@conorsch conorsch moved this from Todo to In progress in Penumbra Apr 18, 2024
conorsch added a commit that referenced this issue Apr 19, 2024
@conorsch
docs: clarify chain upgrade procedure
21af024 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * do not delete historical cometbft state data

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
@conorsch conorsch mentioned this issue Apr 19, 2024
Merged
1 task
conorsch added a commit that referenced this issue Apr 19, 2024
@conorsch
docs: clarify chain upgrade procedure
dbc9ea3 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
conorsch added a commit that referenced this issue Apr 19, 2024
@conorsch
docs: clarify chain upgrade procedure
38d2359 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * use `cometbft reset-state` rather than a custom find command

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
conorsch added a commit that referenced this issue Apr 22, 2024
@conorsch
docs: clarify chain upgrade procedure
6f6ba68 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * amend custom find command to preserve `tx_index.db`

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
conorsch added a commit that referenced this issue Apr 22, 2024
@conorsch
docs: clarify chain upgrade procedure
9621537 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * amend custom find command to preserve `tx_index.db`

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
@cratelyn cratelyn modified the milestones: Sprint 4, Sprint 5 Apr 22, 2024
conorsch added a commit that referenced this issue Apr 22, 2024
@conorsch
docs: clarify chain upgrade procedure
ac3217b 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * amend custom find command to preserve `tx_index.db`

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
@github-project-automation github-project-automation bot moved this from In progress to Done in Penumbra Apr 22, 2024
erwanor pushed a commit that referenced this issue Apr 24, 2024
@conorsch @erwanor
docs: clarify chain upgrade procedure
077725e 
Follow-up to #4097. We performed a chain upgrade on Penumbra
for v0.71.0. Based on feedback from the community validators, we've
refined the procedure somewhat. Substantive changes to the docs are as
follows:

  * backup the entire pd & cometbft data dirs, as a precaution
  * upgrade to new pd early, prior to running export, for simplicity's
    sake
  * only move the exported rocksdb directory, which allows preservation
    of other dirs in pd state, e.g. acme tls info
  * do not reset priv validator state
  * amend custom find command to preserve `tx_index.db`

Not yet included in these docs are specifics about the upcoming release;
we'll add those soon.

Finishes and therefore closes #1812.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@conorsch conorsch

Labels
A-governance Area: Governance A-upgrades Area: Relates to chain upgrades _P-medium Medium priority
Projects
Penumbra
Archived in project
Testnets
Status: Future
Milestone
Sprint 5
Development

Successfully merging a pull request may close this issue.

docs: clarify chain upgrade procedure penumbra-zone/penumbra
5 participants
@hdevalence @conorsch @erwanor @cratelyn @aubrika