This repository was archived by the owner on Aug 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
DAWN-664 ⁃ Codify the boot process for dawn 3.x #1614
Comments
pmesnier
added a commit
that referenced
this issue
Mar 15, 2018
…launcher generate a bespoke boot script suitable for registering a set of appointed block producers with the bios note and then have that node delegate responsibility to those ABPs, gh #1614
pmesnier
added a commit
that referenced
this issue
Mar 17, 2018
pmesnier
added a commit
that referenced
this issue
Mar 17, 2018
pmesnier
added a commit
that referenced
this issue
Mar 19, 2018
…ce again be able to stand up a fully producing testnet, #1614
pmesnier
added a commit
that referenced
this issue
Mar 19, 2018
pmesnier
added a commit
that referenced
this issue
Mar 19, 2018
pmesnier
added a commit
that referenced
this issue
Mar 20, 2018
pmesnier
added a commit
that referenced
this issue
Mar 21, 2018
➤ Phil Mesnier commented: getting closer to completion with this ticket. Actually the work now is follow-on to the original problem description. I didn't anticipate the work needed to modify test scripts, nor the degree of difficulty required to properly manage the relationship between the bios node and all the ordinary producer nodes. All of that is sorted out now but the test drivers still need work. I created a new branch last night, merge_664_try_1, into which I merged my changes from my original working branch. Doing this greatly simplified the effort needed to execute the merger. |
pmesnier
added a commit
that referenced
this issue
Mar 22, 2018
pmesnier
added a commit
that referenced
this issue
Mar 23, 2018
…al step to the testnet script template so that when run it will create a testnet with producer accounts containing state. #1614
pmesnier
added a commit
that referenced
this issue
Mar 23, 2018
heifner
pushed a commit
that referenced
this issue
Mar 23, 2018
heifner
pushed a commit
that referenced
this issue
Mar 23, 2018
heifner
added a commit
that referenced
this issue
Mar 23, 2018
Third try at getting a clean commit pushed. #1614
Related PR is #1816 |
ATC passes. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Bart has provided an initial sequence of steps for testnet ignition starting with a single bios node. This ticket is a placeholder for tracking the effort of codifying this into scripts. I'm starting with my manual steps on testnet 2 including some modification to the launcher.
These steps should dovetail with efforts to track the process outlined in Thomas's mainnet ignition sequence document.
Artifacts of this task to include revised launcher app, boot sequence script, configuration file templates, and a document describing the user's responsibility for initializing the necessary inputs.
ATC: Start with a pristine deployment with 0 blocks end with 21 producing nodes all in sync.
The text was updated successfully, but these errors were encountered: