d-bis/proxmox
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add MEV CT2421 cutover helper

Browse Source
This commit is contained in:
defiQUG
2026-04-13 16:06:34 -07:00
parent 0c58ccaf6c
commit 309843df95
2 changed files with 252 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
docs/04-configuration/MEV_CONTROL_LAN_BRINGUP_CHECKLIST.md
View File

@@ -15,7 +15,7 @@ It is based on the repo's current assumptions:
Because of that localhost assumption, the cleanest contained split topology for this deployment is:
- **Backend Proxmox host:** `r630-04` at **`192.168.11.14`**
- **Backend CT:** **VMID `2421`** at **`192.168.11.219`**
- **Backend CT:** **VMID `2421`** at **`192.168.11.223`**
- **Public web host:** `info-defi-oracle-web` CT **2410** at **`192.168.11.218`**
## 1. Host choice
@@ -30,7 +30,7 @@ Use the dedicated backend CT for:
Use **CT 2410** only for:
- static GUI files
- nginx reverse proxy `/api` to `192.168.11.219:9090`
- nginx reverse proxy `/api` to `192.168.11.223:9090`
Why this is the recommended topology:
@@ -55,7 +55,7 @@ Default CT identity:
- Proxmox host: `192.168.11.14`
- VMID: `2421`
- CT IP: `192.168.11.219`
- CT IP: `192.168.11.223`
- Hostname: `mev-control-backend`
The provisioner creates an unprivileged Debian 12 CT with:
@@ -313,7 +313,7 @@ Before testing the public site, re-render the MEV nginx vhost so CT `2410` point
```bash
cd /home/intlc/projects/proxmox
MEV_ADMIN_API_HOST=192.168.11.219 bash scripts/deployment/sync-mev-control-gui-defi-oracle.sh
MEV_ADMIN_API_HOST=192.168.11.223 bash scripts/deployment/sync-mev-control-gui-defi-oracle.sh
```
Once the control plane is up inside the backend CT, confirm CT 2410 can reach it through nginx:
@@ -341,7 +341,8 @@ Overview:
- needs `mev-admin-api`
- needs service health ports 8080-8087 on the same host
- infra only reports real Postgres status today; Redis and NATS are still backend TODOs
- infra reports live Postgres, Redis, and NATS status
- backend CT includes `mev-start-all.service` so the worker stack auto-starts after `mev-supervisor` and `mev-admin-api`
Pipeline:
@@ -395,3 +396,32 @@ Even after the stack is running, the following are still known implementation ga
- bundle signing
- inclusion detection
- Uniswap V3 / Curve / multicall / block-subscription gaps tracked in `MEV_Bot/mev-platform/docs/REMAINING_GAPS_IMPLEMENTATION.md`
## 15. Post-deploy cutover for CT 2421
Once the hardened executor and flash-loan provider wrapper are actually broadcast, use the dedicated cutover helper from the repo root:
```bash
bash scripts/deployment/run-mev-post-deploy-cutover-ct2421.sh \
--artifact reports/status/mev_execution_deploy_YYYYMMDD_HHMMSS.json \
--uniswap-v2-router 0x... \
--sushiswap-router 0x... \
--api-key "$MEV_API_KEY"
```
That runs in dry-run mode by default and prints:
- the exact config patch diff for `config.dev.toml`
- the exact `pct exec 2421` copy command
- the exact restart chain for `mev-supervisor`, `mev-admin-api`, and `mev-start-all`
- the exact local CT verification commands
- the exact public verification commands
When the diff and commands look correct, run the same command with `--apply`.
This helper assumes:
- Proxmox host for the backend CT is `192.168.11.14`
- backend CT VMID is `2421`
- target config inside the CT is `/opt/proxmox/MEV_Bot/mev-platform/config.dev.toml`
- backend env file inside the CT is `/etc/mev-platform/backend.env`