pdurlej/platform

Fork 0

ops(rs2000-legacy): migrate OpenClaw mail config bind mounts #544

New issue

Closed

opened 2026-05-28 01:37:52 +02:00 by codex · 2 comments

codex commented

2026-05-28 01:37:52 +02:00

Collaborator

Scope

Move OpenClaw mail infra config bind mounts off legacy path into canonical runtime import path, then update compose references.

Observed legacy mounts

home-platform-openclaw-mail-gateway-1: /opt/vps-home-platform-infra/products/openclaw-mail-infra/config -> /config ro
home-platform-openclaw-mail-worker-1: /opt/vps-home-platform-infra/products/openclaw-mail-infra/config -> /config ro

Target shape

Copy config as-is under /opt/pdurlej-platform/runtime/legacy-import/products/openclaw-mail-infra/config or a more specific canonical path if already established.
Update compose/module docs to reference the new path.

Acceptance criteria

Dry-run copy plan records source, target, owner/mode preservation, and rollback.
PR updates only OpenClaw mail gateway/worker bind paths and relevant docs.
Runtime recreate is limited to gateway + worker after explicit approval.
Smoke verifies gateway/worker health and no new mail route regression.
Legacy mount count decreases for these two containers.

Out of scope

Changing mail gateway app behavior.
Editing secrets inside config.
Changing public ingress.

Common safety rules

Recommended executor: Gemini 3.5 Flash local for repo/doc/plan work.
Do not delete, rename, prune, or edit /opt/vps-home-platform-infra in this issue.
Do not print secrets, env values, private messages, emails, or Iskra memory.
Runtime execution requires a separate explicit operator approval in the PR/issue thread.
First step is always read-only evidence refresh.
Preserve ownership, modes, symlinks, and timestamps when copying data/config.
Update compose/module docs through a PR before recreating affected services.
Recreate only affected service(s), never the whole platform, unless a later operator gate says otherwise.

## Scope Move OpenClaw mail infra config bind mounts off legacy path into canonical runtime import path, then update compose references. ## Observed legacy mounts - `home-platform-openclaw-mail-gateway-1`: `/opt/vps-home-platform-infra/products/openclaw-mail-infra/config` -> `/config` ro - `home-platform-openclaw-mail-worker-1`: `/opt/vps-home-platform-infra/products/openclaw-mail-infra/config` -> `/config` ro ## Target shape - Copy config as-is under `/opt/pdurlej-platform/runtime/legacy-import/products/openclaw-mail-infra/config` or a more specific canonical path if already established. - Update compose/module docs to reference the new path. ## Acceptance criteria - Dry-run copy plan records source, target, owner/mode preservation, and rollback. - PR updates only OpenClaw mail gateway/worker bind paths and relevant docs. - Runtime recreate is limited to gateway + worker after explicit approval. - Smoke verifies gateway/worker health and no new mail route regression. - Legacy mount count decreases for these two containers. ## Out of scope - Changing mail gateway app behavior. - Editing secrets inside config. - Changing public ingress. ## Common safety rules - Recommended executor: Gemini 3.5 Flash local for repo/doc/plan work. - Do not delete, rename, prune, or edit `/opt/vps-home-platform-infra` in this issue. - Do not print secrets, env values, private messages, emails, or Iskra memory. - Runtime execution requires a separate explicit operator approval in the PR/issue thread. - First step is always read-only evidence refresh. - Preserve ownership, modes, symlinks, and timestamps when copying data/config. - Update compose/module docs through a PR before recreating affected services. - Recreate only affected service(s), never the whole platform, unless a later operator gate says otherwise.

codex added this to the 01 - RS2000 closeout and legacy cleanup milestone

2026-05-28 01:37:52 +02:00

codex added the

ready-for-agent

risk/runtime

class/security-sensitive

labels

2026-05-28 01:37:52 +02:00

codex referenced this issue

2026-05-29 01:04:22 +02:00

ops(rs2000-legacy): refresh live bind-mount inventory before migration batches #543

codex commented

2026-05-29 01:05:24 +02:00

Author

Collaborator

Current evidence after PRs #583-#593:

running containers: home-platform-openclaw-mail-gateway-1, home-platform-openclaw-mail-worker-1
compose origin label: /tmp/openclaw-mail-phase2.compose.yaml
env_file label/source: /root/openclaw-mail-phase2.env (do not print values)
both mount /opt/vps-home-platform-infra/products/openclaw-mail-infra/config -> /config:ro
image: home-platform-openclaw-mail-gateway:0.2.0
gateway networks: hp_internal, hp_proxy; worker network: hp_internal

Important drift: modules/openclaw-mail-gateway/module.yaml currently describes vps1000/systemd/public gateway, while live RS2000 Docker containers exist. Next PR must first reconcile owner/source boundary, then remount config. Do not blindly recreate from repo compose because no repo compose definition currently owns these containers.

Current evidence after PRs #583-#593: - running containers: `home-platform-openclaw-mail-gateway-1`, `home-platform-openclaw-mail-worker-1` - compose origin label: `/tmp/openclaw-mail-phase2.compose.yaml` - env_file label/source: `/root/openclaw-mail-phase2.env` (do not print values) - both mount `/opt/vps-home-platform-infra/products/openclaw-mail-infra/config` -> `/config:ro` - image: `home-platform-openclaw-mail-gateway:0.2.0` - gateway networks: `hp_internal`, `hp_proxy`; worker network: `hp_internal` Important drift: `modules/openclaw-mail-gateway/module.yaml` currently describes vps1000/systemd/public gateway, while live RS2000 Docker containers exist. Next PR must first reconcile owner/source boundary, then remount config. Do not blindly recreate from repo compose because no repo compose definition currently owns these containers.

codex referenced this issue

2026-05-29 01:05:26 +02:00

ops(rs2000-legacy): validate zero legacy bind mounts and green smokes #556

codex commented

2026-05-29 01:48:37 +02:00

Author

Collaborator

Completed in the M01 orphan remount pass.

Runtime evidence:

home-platform-openclaw-mail-gateway-1 remapped /config to /opt/pdurlej-platform/runtime/legacy-import/products/openclaw-mail-infra/config.
home-platform-openclaw-mail-worker-1 remapped /config to the same legacy-import target.
Both containers recreated from Docker inspect snapshot via Docker API; old env values were preserved in-memory and not printed.
Both containers ended running / healthy.
Rollback snapshots stored under /opt/pdurlej-platform/runtime/m01-container-snapshots mode 0600.

No source data/config was deleted.

Completed in the M01 orphan remount pass. Runtime evidence: - `home-platform-openclaw-mail-gateway-1` remapped `/config` to `/opt/pdurlej-platform/runtime/legacy-import/products/openclaw-mail-infra/config`. - `home-platform-openclaw-mail-worker-1` remapped `/config` to the same legacy-import target. - Both containers recreated from Docker inspect snapshot via Docker API; old env values were preserved in-memory and not printed. - Both containers ended `running` / `healthy`. - Rollback snapshots stored under `/opt/pdurlej-platform/runtime/m01-container-snapshots` mode 0600. No source data/config was deleted.

codex closed this issue

2026-05-29 01:48:38 +02:00