v0.6.0 -> v0.7.0 upgrade guide #84
No reviewers
srw
i-norden
Labels
No Label
bug
C:CLI
C:Crypto
C:Encoding
C:Proto
C:Types
dependencies
docker
documentation
duplicate
enhancement
go
good first issue
help wanted
high priority
in progress
invalid
javascript
low priority
medium priority
question
Status: Stale
Type: ADR
Type: Build
Type: CI
Type: Docs
Type: Tests
urgent
wontfix
Copied from Github
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cerc-io/laconicd#84
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "0-7-0-upgrade-guide"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
An upgrade guide from v0.6.0 to v0.7.0
Covers both systemd and docker upgrade paths
I would pin to a specific version like 1.19.4
Would mark it as warning. People might oversee this part
@ -0,0 +56,4 @@```sh# Remove the previous build directorycd ~rm -rf laconicdShould probably be '.laconicd' or the name at the beginning is different intentionally?
@ -0,0 +94,4 @@sudo systemctl status laconicd```---Probably good to verify that service is stopped
@ -0,0 +136,4 @@>***You have ~10 minutes to complete the upgrade procedure before your validator is jailed for downtime. Getting jailed for downtime is not a disaster, however would require manual unjailing.***### Stop running v0.6.0 containerWhy do we stop service first before build?
What if a build time is longer than 10 minutes?
It is 1.19.5 later in the documentation
@ -0,0 +56,4 @@```sh# Remove the previous build directorycd ~rm -rf laconicdNo, this is where you clone the repository and build laconicd. .laconicd is the datadir which must be kept
@ -0,0 +136,4 @@>***You have ~10 minutes to complete the upgrade procedure before your validator is jailed for downtime. Getting jailed for downtime is not a disaster, however would require manual unjailing.***### Stop running v0.6.0 containerWe don't build we just create a container (pulling an image takes only few moments). The reason to remove the previous container is to keep the same container name laconic-testet-5 but with a new version of laconicd.
@ -0,0 +94,4 @@sudo systemctl status laconicd```---will add a command for this
@ -0,0 +56,4 @@```sh# Remove the previous build directorycd ~rm -rf laconicdAdded a warning to not confuse these 2 directories
agree
@ -0,0 +136,4 @@>***You have ~10 minutes to complete the upgrade procedure before your validator is jailed for downtime. Getting jailed for downtime is not a disaster, however would require manual unjailing.***### Stop running v0.6.0 containerThanks!
LGTM, I don't have much to add. Thanks!
@ -0,0 +51,4 @@### Remove old copy of `laconicd` build>Attention should be paid that the directory mentioned below is `~/laconicd` and NOT `~/.laconicd`. The latter is the data directory containing all your node data and configuration and it must be kept during the upgrade.Makes me think we should make the datadir name different from the directory/package/executable name