[Feature] V2P: Wait for confirmation before switchover

[ajoergensen]

Got an idea? Nice! 💡 We love hearing what features would make PegaProx better for you.

A friendly reminder: PegaProx is built by volunteers in our spare time. We can't promise timelines or guarantee every feature will be implemented — but every suggestion helps shape the roadmap!

Want to help move things faster?

• 💖 Become a Sponsor — sponsored features get prioritized
• ⭐ Star the project — helps with visibility
• 🤝 Even better: submit a PR with your idea!

---

Describe the feature

During migration from ESXi to Proxmox, wait for confirmation before doing the switch-over.

Obviously this can/should be a parameter in the migration wizerd

Use Case

Even if the the switchover itself is only a few seconds, the downtime for applications may be a lot longer, so the ability to control when the switchover happens, allows the user to handle outage in their monitoring systems, etc.

Alternatives considered

Leave it as is.

How important is this for you?

Would improve my workflow

Checklist

• [ X] I have searched existing issues and discussions to make sure this hasn't been requested before

[mkellermann97]

Good call, @ajoergensen — and it slots in cleanly: the clone + disk copy already finish as a discrete phase before the final cutover, so a "pause here, wait for me to confirm" gate in the wizard is a natural seam rather than a rewrite. Your point that app-level downtime ≠ the cutover seconds is exactly right — drain monitoring, flip DNS/whatever, then commit. I've noted it against the V2P rework that's already in flight; no timeline promise, but it's sensible and the plumbing's mostly there for it. If you hit a specific cutover-timing pain before it lands, drop it on the thread. opencollective.com/pegaprox keeps the migration work moving 🙏 — Marcus