8. Implementation Plans

Detailed implementation plans for in-progress and upcoming features.

• 8.1. Mapping by App Plans
  • 8.1.1. Per-App-Context Mapping Policies
  • 8.1.2. Per-App-Context Mapping: Implementation Plan
  • 8.1.3. Per-App-Context Mapping: Implementation Tasks
• 8.2. Node Reservation and Session Targeting Plans
  • 8.2.1. Node Reservation and Session Targeting: Specification
  • 8.2.2. Node Reservation and Session Targeting
• 8.3. Elastic DVM Plans
  • 8.3.1. Elastic DVM: Specification
  • 8.3.2. Elastic DVM Implementation Plan
  • 8.3.3. DVM Grow-Campaign Fence Tracking
  • 8.3.4. DVM Shrink-Campaign Fence Tracking
  • 8.3.5. Collective Shrink Completion — Repair the Routing Tree Once per Campaign
• 8.4. DVM Bootstrap Plans
  • 8.4.1. DVM Bootstrap: Specification
  • 8.4.2. DVM Bootstrap Implementation Plan
  • 8.4.3. Rewiring a Returned Daemon: the “Unheal” Path
• 8.5. Degraded-mode survival of a group construct on daemon loss
  • 8.5.1. Context
  • 8.5.2. Corrections to earlier premises
  • 8.5.3. Desired behavior
  • 8.5.4. Design: one global epoch, not a per-link round
  • 8.5.5. Commits
  • 8.5.6. Out of scope
  • 8.5.7. Verification
• 8.6. Restructuring the DVM collectives around operations
  • 8.6.1. Context
  • 8.6.2. Status
  • 8.6.3. The operations
  • 8.6.4. Cost model
  • 8.6.5. Design
  • 8.6.6. What the numbers turned out to be
  • 8.6.7. What a client actually asks about a remote peer
  • 8.6.8. What Slurm’s PMI2 does, and what it tells us
  • 8.6.9. Verification
  • 8.6.10. Open questions