-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
vspd migration coordination #231
Comments
Updated 2022-06-23. First table tracks legacy dcrstakepools and their replacement vspd instances and versions.
Second table captures how dcrstakepools have been shutdown.
Legend:
Notes:
|
@jholdstock I guess the instances with "pre" in the table above are not building from release branches. |
Correct |
Including a link to the operator guide put together by @degeri https://gist.github.com/degeri/a489b458b1a850ff378914f464f158c6 |
Main checklist updated: decred.org udpates done, linked terminology coordination decred/dcrdocs#1156, added Decrediton bullet to help with vspd choice, tweaks. vspd table updated: stakey.com and stakey.net seem to have deployed from release branches and have proper |
dcrstakepool-vspd mapping table updated: added 123.dcr.rocks and checked all versions. 4 VSPs still run |
A 1.0.1 release will likely be coming up soon to pre-emptively fix some database scaling issues (#223). When that comes I will prompt operators to upgrade, rather than pushing for two updates in quick succession. |
Tracking rollout of vspd 1.1.0 here. I plan to close this issue once the rollout is completed. Some of the points listed in the original post by @xaur are still relevant/useful, so I will open new issues in the relevant repos for those. Communication log:
|
dcrvsp.ubiqsmart.com has been upgraded for the past few days. cheers! |
@xaur please can you update the todos? would love to see what's left. |
@jyap808 I'm still seeing |
Hmm, strange. OK, just pulled and rebuilt: |
The |
@ukane-philemon I updated subtasks and commented on each. |
Updated the legacy shutdown comparison table to see which operators did it the best way (fewer immature/live tickets at the end is better). |
@jholdstock can decide if we can tick this one off the list :). |
I clicked the checkbox just to see if it would update and it did. I didnt know I would have permissions to do that lol. Checked a couple of others too. |
Right, repo admins can edit any issue or PR description. This is great as you can keep your repo/issues/PRs clean and pretty even if the initial submission was poorly formatted. Behind the scenes, "checking" a box does an edit changing |
dcrstakepool is entirely phased out now so I'm closing this issue. Thanks @xaur for opening this and staying on top of the migration process. |
Update 2022-06-23: Things have changed, dcrstakepool is no longer functional and the majority has migrated to vspd. Some of the tasks below may no longer be necessary, while some are still nice to have. To be clear, most of them have never blocked the migration but rather suggested how to make it smoother for operators and users. See this comment for a more recent status.
dcrstakepool
updatesvspd
updatesDiscussions:
The text was updated successfully, but these errors were encountered: