avalancheup-aws: Document state management for spot instances.
Opened this issue · 2 comments
First of all avalancheup-aws is a nice tool it helped me quickly setup nodes on AWS. While working on creating a new subnet and blockchain I noticed that the AvalancheGo version that was installed 1.10.0 was less than the version I needed 1.10,2. Once I pulled in a new binary and installed it things worked fine. Also during debug I updated the system unit file for AvalancheGo.
The issue is when the system gets migrated I assume due to spot workflow.
- I no longer have a systemd unit file for
AvalancheGo - The binary returns to the old version
I have not dug into this much but I assume this is related to how the state is managed in the spot instances. When a new VM is started it pulls the binary from s3 and probably the unit file as well.
A short section in the docs would be useful describing.
- how to upgrade
AvalancheGo - how to update managed files
- brief description of how spot works in this context.
I no longer have a systemd unit file for AvalancheGo
On restart, the init script will rewrite the avalanchego systemd file (done by avalanched).
Yes, we need documentation.
@gyuho Can I work on this issue ?