In this article



Help us make these docs great!

All rapyuta.io docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Migrating a Device Across Projects

This feature allows administrators to migrate online devices from one project to another using the Command Line Interface (CLI). This is useful for reallocating devices quickly without the need for re-onboarding.

Use Cases

Production Environment

Several R-AFL devices will be placed in a warehouse for calibration and trial runs before being shipped to customers. Once an R-AFL device is ready to be shipped, it can be moved to another project without re-onboarding. This streamlines the workflow, making the transition faster and more efficient.

Staging Environment

In a staging environment, devices may be used across multiple staging projects for testing purposes. Devices can be migrated between different staging projects without re-onboarding, allowing for flexible and efficient testing across various environments.

Migrating a Device

Before starting the device migration process, make sure to consider the following constraints:

  • Device Status: Ensure that the device is online before initiating the migration process.
  • Active Deployments: Ensure there are no active deployments on the device during migration to avoid conflicts.
  • Unique Device Names: Verify that the target project does not contain a device with the same name as the one being migrated.

VPN Enablement: After migration, administrators have the option to enable VPN on the device for enhanced security. Include the --enable-vpn flag in the migration command if VPN is required.

To migrate a device from Project A to Project B, use the following CLI command:

rio device migrate <device-name> Project_B --enable-vpn

Still need help

Ask the community Contact support