v0.6.0 -> v0.7.0 upgrade guide #84

Merged
iszubok merged 2 commits from 0-7-0-upgrade-guide into main 2023-01-20 07:25:25 +00:00
iszubok commented 2023-01-18 17:21:42 +00:00 (Migrated from github.com)

An upgrade guide from v0.6.0 to v0.7.0
Covers both systemd and docker upgrade paths

An upgrade guide from v0.6.0 to v0.7.0 Covers both systemd and docker upgrade paths
sjors-lemniscap (Migrated from github.com) reviewed 2023-01-18 17:21:42 +00:00
srw reviewed 2023-01-18 17:21:42 +00:00
sibuser (Migrated from github.com) reviewed 2023-01-18 18:13:57 +00:00
sibuser (Migrated from github.com) commented 2023-01-18 18:13:51 +00:00

I would pin to a specific version like 1.19.4

I would pin to a specific version like 1.19.4
sibuser (Migrated from github.com) reviewed 2023-01-18 18:14:59 +00:00
sibuser (Migrated from github.com) commented 2023-01-18 18:14:54 +00:00

Would mark it as warning. People might oversee this part

Would mark it as warning. People might oversee this part
sibuser (Migrated from github.com) reviewed 2023-01-18 18:18:13 +00:00
@ -0,0 +56,4 @@
```sh
# Remove the previous build directory
cd ~
rm -rf laconicd
sibuser (Migrated from github.com) commented 2023-01-18 18:15:53 +00:00

Should probably be '.laconicd' or the name at the beginning is different intentionally?

Should probably be '.laconicd' or the name at the beginning is different intentionally?
@ -0,0 +94,4 @@
sudo systemctl status laconicd
```
---
sibuser (Migrated from github.com) commented 2023-01-18 18:16:57 +00:00

Probably good to verify that service is stopped

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 container
sibuser (Migrated from github.com) commented 2023-01-18 18:18:09 +00:00

Why do we stop service first before build?
What if a build time is longer than 10 minutes?

Why do we stop service first before build? What if a build time is longer than 10 minutes?
iszubok (Migrated from github.com) reviewed 2023-01-18 18:28:47 +00:00
iszubok (Migrated from github.com) commented 2023-01-18 18:28:47 +00:00

It is 1.19.5 later in the documentation

It is 1.19.5 later in the documentation
iszubok (Migrated from github.com) reviewed 2023-01-18 18:30:19 +00:00
@ -0,0 +56,4 @@
```sh
# Remove the previous build directory
cd ~
rm -rf laconicd
iszubok (Migrated from github.com) commented 2023-01-18 18:30:19 +00:00

No, this is where you clone the repository and build laconicd. .laconicd is the datadir which must be kept

No, this is where you clone the repository and build laconicd. .laconicd is the datadir which must be kept
iszubok (Migrated from github.com) reviewed 2023-01-18 18:32:24 +00:00
@ -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 container
iszubok (Migrated from github.com) commented 2023-01-18 18:32:24 +00:00

We 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.

We 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.
iszubok (Migrated from github.com) reviewed 2023-01-18 18:42:59 +00:00
@ -0,0 +94,4 @@
sudo systemctl status laconicd
```
---
iszubok (Migrated from github.com) commented 2023-01-18 18:42:58 +00:00

will add a command for this

will add a command for this
iszubok (Migrated from github.com) reviewed 2023-01-18 18:46:46 +00:00
@ -0,0 +56,4 @@
```sh
# Remove the previous build directory
cd ~
rm -rf laconicd
iszubok (Migrated from github.com) commented 2023-01-18 18:46:45 +00:00

Added a warning to not confuse these 2 directories

Added a warning to not confuse these 2 directories
iszubok (Migrated from github.com) reviewed 2023-01-18 18:46:58 +00:00
iszubok (Migrated from github.com) commented 2023-01-18 18:46:57 +00:00

agree

agree
sibuser (Migrated from github.com) reviewed 2023-01-18 19:18:24 +00:00
@ -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 container
sibuser (Migrated from github.com) commented 2023-01-18 19:18:24 +00:00

Thanks!

Thanks!
i-norden approved these changes 2023-01-18 21:07:11 +00:00
i-norden left a comment
Member

LGTM, I don't have much to add. Thanks!

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.
Member

Makes me think we should make the datadir name different from the directory/package/executable name

Makes me think we should make the datadir name different from the directory/package/executable name
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconicd-deprecated#84
No description provided.