8.3. Elastic DVM Plans

Implementation plans for dynamic DVM grow/shrink support.

• 8.3.1. Elastic DVM: Specification
  • 8.3.1.1. Purpose
  • 8.3.1.2. Scope
  • 8.3.1.3. Definitions
  • 8.3.1.4. Admission contract
  • 8.3.1.5. Concurrency
  • 8.3.1.6. Asynchronous size-change completion
  • 8.3.1.7. Failure semantics
  • 8.3.1.8. Observability
  • 8.3.1.9. Backward compatibility and transparency
  • 8.3.1.10. Conformance summary
• 8.3.2. Elastic DVM Implementation Plan
  • 8.3.2.1. Step 1 — New state constant
  • 8.3.2.2. Step 2 — New global fence and held-job arrays
  • 8.3.2.3. Step 3 — Park jobs at the VM_READY → MAP boundary
  • 8.3.2.4. Step 4 — Held-job release helpers
  • 8.3.2.5. Step 5 — Completion-event emission (shared helper)
  • 8.3.2.6. Summary of Files Changed (Shared Fence Infrastructure)
  • 8.3.2.7. Design Invariants
• 8.3.3. DVM Grow-Campaign Fence Tracking
  • 8.3.3.1. Motivation
  • 8.3.3.2. Design
  • 8.3.3.3. Why this is correct
  • 8.3.3.4. Touched files
  • 8.3.3.5. Follow-up
• 8.3.4. DVM Shrink-Campaign Fence Tracking
  • 8.3.4.1. Background
  • 8.3.4.2. Design Decision — Complete on Death, Not on Acknowledgement
  • 8.3.4.3. Step 1 — Shrink campaign type, list, and fence increment
  • 8.3.4.4. Step 2 — Daemon exit (no acknowledgement)
  • 8.3.4.5. Step 3 — Second hold point at LAUNCH_APPS
  • 8.3.4.6. Step 4 — Remap helpers
  • 8.3.4.7. Step 5 — Detect target departure in the errmgr and notify completion
  • 8.3.4.8. Summary of Files Changed (Shrink Fence)
  • 8.3.4.9. Design Invariants
  • 8.3.4.10. Follow-up — collective shrink completion