NVIDIA MagLev Deprecation Data Migration Information
MagLev is going away! We'll miss you old buddy. If you are here, it means that you'd like to move some data to the enterprise W&B instance for NVIDIA. Please ensure you've read through what this means and the limitations it entails.
Created on October 3|Last edited on October 7
Comment
Migration Timelines
Weights & Biases will be providing migration services to MagLev users on a case-by-case basis, as migrations are a big lift. We'll be taking in requests through October 15th, 2024. After this date, no migration requests will be considered. We highly discourage self-serving migrations, as they are complex.
Limitations
Migrating from MagLev to NVIDIA's corporate account will require replaying all the data from MagLev, which means the following will be preserved:
- Runs/Associated Metrics, as well as (most) associated metadata
- Artifacts
- A limited amount of Reports
- (Some) stdout/stderr logs
What has limitations:
- **Custom Charts:** No custom charts will be transferred.
- **System Metrics:** System metrics will not be included.
- **Tables:** Tables will not populate in the workspace but will be available as artifacts.
- **Run Ordering:** No "Created At" timestamp is associated with runs; run ordering will not persist (timestamps will correspond to the import date).
- **Author Name:** No author name will be transferred (author name will be set as a service account)
- **Job Type:** Job types will not be transferred.
- **Launch Configuration:** Launch configurations will not be transferred.
- **Sweeps:** Sweep page results will not be migrated, although the runs will be available.
- **Workspace Configurations:**
- Run groups will not be transferred.
- No saved views will be carried over.
10. **Registry:** Registry data will not be migrated.
11. **Reports:** Some Reports aren't able to be migrated.
12. **Automations:** Automations will not be migrated.
13. **Run Colors:** Run colors will not remain the same.
Other Possible Issues
1. **Large Logs:** If a run's output.log exceeds 100k lines, the import process may struggle to move the data.
2. **Incomplete Run Data:** Sometimes, only a fraction of the steps may be visible after importing runs.
3. **Artifacts:** There may be cases where artifacts do not get migrated, without any error notifications.
4. **Dummy Runs:** During migration, dummy runs created to import artifacts may remain in the destination workspace. The migration might not complete, leaving these dummy runs unfinished.
Acknowledgement
If you want to go through with the migration, please fill out this form by October 15th, 2024, and we will be in touch with you ASAP! Your submission of the form is an acknowledgement of these limitations.
Add a comment