Migration Guide (On Pillar)

This guide outlines the steps to migrate an existing orchestrator from one Pillar virtual machine (VM) to another, preserving its ability to participate in the HyperCore bridge’s Threshold Signature Scheme (TSS) signer set. It builds on the Orchestrator Setup Guide on Pillar.

Table of Contents

1. Prerequisites

2. Set Up the Orchestrator on the New VM

3. Transfer the Orchestrator Configuration

4. Set Up and Start the Orchestrator Service

5. Verify Migration

---

1) Prerequisites

• Old VM Access: Ensure the original VM (old Pillar) is still accessible and running the orchestrator.

• New VM Setup: The new VM should have a working Pillar node synced with the Zenon Network of Momentum (NoM), as per the Pillar setup guide.

• Backup: Back up the old VM’s orchestrator directory (/root/.orchestrator) and producer keystore before proceeding.

• SSH Access: You need SSH access to both the old and new VMs with sufficient permissions (e.g., root or sudo).

---

2) Set Up the Orchestrator on the New VM

If the orchestrator isn’t already installed on the new VM, follow the initial setup steps from the Orchestrator Setup Guide first.

---

3) Transfer the Orchestrator Configuration

Copy the entire .orchestrator folder from the old VM to the new VM. This includes the old /producer folder and old config.json:

scp -r root@<old-vm-ip>:/root/.orchestrator /root/

---

4) Set Up and Start the Orchestrator Service

Follow step 6 of the Setup Guide.

---

5) Verify Migration

Confirm the orchestrator is functioning and recognized by the bridge.

a) Check Logs:

View recent logs for errors:

journalctl -u orchestrator -n 50

b) Test Health Check:

Query the orchestrator’s API:

curl -X POST -d '{"method":"getBuildInfo", "params":[]}' -H "Content-Type: application/json" http://localhost:55000

Expected output includes version info, e.g.,

{"result":{"version":"v0.0.9a","gitCommit":"edf58a929989e70656a5f04501b25fb918f6ef71","goVersion":"go1.22.1"},"error":""}.