9. Implementation Plans

Detailed implementation plans for in-progress and upcoming features.

• 9.1. Mapping by App Plans
  • 9.1.1. Per-App-Context Mapping Policies
  • 9.1.2. Per-App-Context Mapping: Implementation Plan
  • 9.1.3. Per-App-Context Mapping: Implementation Tasks
• 9.2. Mapping by Device Plans
  • 9.2.1. Mapping and binding by device
  • 9.2.2. Device mapping: implementation plan
• 9.3. Node Reservation and Session Targeting Plans
  • 9.3.1. Node Reservation and Session Targeting: Specification
  • 9.3.2. Node Reservation and Session Targeting
• 9.4. Elastic DVM Plans
  • 9.4.1. Elastic DVM: Specification
  • 9.4.2. Elastic DVM Implementation Plan
  • 9.4.3. DVM Grow-Campaign Fence Tracking
  • 9.4.4. DVM Shrink-Campaign Fence Tracking
  • 9.4.5. Collective Shrink Completion — Repair the Routing Tree Once per Campaign
• 9.5. DVM Bootstrap Plans
  • 9.5.1. DVM Bootstrap: Specification
  • 9.5.2. DVM Bootstrap Implementation Plan
  • 9.5.3. Rewiring a Returned Daemon: the “Unheal” Path
• 9.6. Group Fault-Tolerance Plans
  • 9.6.1. Degraded-mode survival of a group construct on daemon loss
• 9.7. Scalable Collectives Plans
  • 9.7.1. Restructuring the DVM collectives around operations
  • 9.7.2. Two trees: a low-radix release beside the high-radix rollup
• 9.8. Cross-DVM Data Server Plans
  • 9.8.1. Reaching a data server in another DVM
• 9.9. Data Store Retention Plans
  • 9.9.1. Data Store Retention: Specification
  • 9.9.2. Data Store Retention: Design
  • 9.9.3. Data Store Retention: Implementation Plan