Migrate SP from one Curio Node to another Curio Node

[amughal]

Checklist

• This is not a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
• This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the Curio forum and select the category as Ideas.
• I have a specific, actionable, and well motivated feature request to propose.

Curio component

• PoRep Pipeline
• Snap Deals
• Market
• IPNI provider
• Curio UI
• Other

What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.

I need to move out a miner from one Curio node to a remote Curio node managed by another entity.

Describe the solution you'd like

Once sectors and cache files are copied from one Curio deployment to another, then:

1. What is needed for the DB to export on and import at the new Curio node.
2. What is needed during the migration (stop windowPost for the miner)
3. Once migration is complete what cleanups are needed on the first Curio node

Describe alternatives you've considered

No response

Additional context

No response

[nathandragun]

I second the request for this feature.

Also, we need to track market data.

While this will undoubtedly need some back-end command execution, adding an export/import feature via the UI would streamline the process for operators.

[LexLuthr]

Table list:

1. market_direct_deals
2. market_legacy_deals (if not empty)
3. market_mk12_deals
4. market_mk12_deal_pipeline_migration (must be empty)
5. market_mk12_deals
6. market_mk12_storage_ask
7. market_piece_deal
8. market_piece_metadata
9. sectors_meta (fix snap bug during migration if needed)
10. sectors_meta_pieces

Other considerations:

1. Indexing will happen again
2. IPNI ads will be generated again
3. IPNI should use a new peerID

[nathandragun]

When migrating from location A to location B, there may be times when the miner needs to be enabled on B and disabled on A, then quickly disabled on B and enabled on A if an error is detected. A "toggle" feature to enable/disable a minerID for a given curio stack would mitigate this.

[amughal]

Hello @LexLuthr, If possible we like this migration to be completed in this month of May. Thank you

[LexLuthr]

We have full dev schedule and probably won't get to it for next couple of months at least. Might even be longer.
If this is urgent then you can use the above info to extract the data filtering by sp_id and then inserting it into the destination tables. Then remove from old DB.