Skip to content
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

fix: remove sector indexing from guided-setup #110

Merged
merged 3 commits into from
Jul 19, 2024
Merged

Conversation

LexLuthr
Copy link
Contributor

@LexLuthr LexLuthr commented Jul 19, 2024

This PR does the following:

  1. Removes waiting for sector indexes and addition of storage path in DB by lotus-miner. This removes the requirement to start lotus-miner during start up and backup the config.toml file.
  2. This PR removes the fsjournal library copied over from Lotus as it was not being used and is replaced by new alerting mechanism created in no more lotus build #63
  3. This PR updates the storage-json location to be inside the CURIO_REPO_PATH as CURIO_REPO_PATH/storage.json. This is more intuitive then having a separate path for just 1 file. Without journal gone, CURIO_REPO_PATH will contain only 1 file.
  4. This PR removed journal and storage-json flags from the run command.
  • Test in devnet - DO NOT MERGE till tested
% ./curio guided-setup
Defaulting to English. Please reach out to the Curio team if you would like to have additional language support.
✔ Migrate from existing Lotus-Miner
                                                                
 ┌────────────────────────────────────────────────────────────┐ 
 │This interactive tool migrates lotus-miner to Curio in 5    │ 
 │minutes.                                                    │ 
 └────────────────────────────────────────────────────────────┘ 
                                                                
Each step needs your confirmation and can be reversed. Press Ctrl+C to exit at any time.
                                                                                        
To start, ensure your sealing pipeline is drained and shut-down lotus-miner.
✔ Other
Enter the path to the configuration directory used by lotus-miner: /Users/lexluthr/github/filecoin-project/curio/docker/data/lotus-miner
✔ Step Complete: Read Miner Config
                                
Connected to Yugabyte. Schema is current.
✔ Step Complete: Connected to Yugabyte
                                    
Migrating lotus-miner config.toml to Curio in-database configuration.
Migrating metadata for 10 sectors.
The following sector states are not migratable:
  Terminating: 1
✔ Yes, continue
Configuration 'base' was updated to include this miner's address (t01000) and its wallet setup.
Compare the configurations base to mig-t01000. Changes between the miner IDs other than wallet addreses should be a new, minimal layer for runners that need it.
Layer mig-t01000 created. 
To work with the config: 
curio  config edit base
To run Curio: With machine or cgroup isolation, use the command (with example layer selection):
curio  run --layer=post
Documentation: 
The 'base' layer stores common configuration. All curio instances can include it in their --layers argument.
You can add other layers for per-machine configuration changes.
Filecoin Slack channels: #fil-curio-help and #fil-curio-dev
Increase reliability using redundancy: start multiple machines with at-least the post layer: 'curio run --layers=post'
One database can serve multiple miner IDs: Run a migration for each lotus-miner.
The Curio team wants to improve the software you use. Tell the team you're using `curio`.
✔ Nothing.
✔ Step Complete: Lotus-Miner to Curio Migration.
                                              
✔ /tmp/curio.env
Try the web interface with curio run --layers=gui 
For more servers, make /etc/curio.env with the curio.env database env and add the CURIO_LAYERS env to assign purposes.
You can now migrate your market node (Boost), if applicable.
Additional info is at http://docs.curiostorage.org

@LexLuthr LexLuthr requested review from snadrus and magik6k July 19, 2024 14:00
@snadrus snadrus merged commit 46a8342 into main Jul 19, 2024
8 checks passed
@snadrus snadrus deleted the fix/improve-setup branch July 19, 2024 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants