You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/status.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,9 +195,9 @@
195
195
- local cluster, qemu assets, Jepsen harness, and benchmarks: `cargo test -p allocdb-node local_cluster -- --nocapture`, `cargo test -p allocdb-node qemu_testbed -- --nocapture`, `cargo test -p allocdb-node jepsen -- --nocapture`, `cargo test -p allocdb-node --bin allocdb-jepsen -- --nocapture`, `cargo run -p allocdb-node --bin allocdb-jepsen -- plan`, `cargo run -p allocdb-bench -- --scenario all`
196
196
- repo gate: `scripts/preflight.sh`
197
197
## Current Focus
198
-
- PR `#82` merged the `#70` maintainability follow-up, and the closing evidence included the live
199
-
KubeVirt `reservation_contention-control` and full `1800s`
200
-
`reservation_contention-crash-restart`reruns on `allocdb-a` with `blockers=0`
198
+
- PR `#82` merged the `#70` maintainability follow-up, including live KubeVirt
199
+
`reservation_contention-control` and full `1800s``reservation_contention-crash-restart`
200
+
reruns on `allocdb-a` with `blockers=0`
201
201
-`M9-T01` through `M9-T05` are merged on `main` via PR `#81`, and the planning issues are closed
202
202
on the `AllocDB` project
203
203
- PR `#89` merged `M9-T06` on `main`: the trusted core now supports atomic bundle reservation,
@@ -208,13 +208,13 @@
208
208
surfaces expose the current authority token for active reservations
209
209
- PR `#92` merged `M9-T08` on `main`: the trusted core now has explicit `revoke` / `reclaim`
210
210
commands, `revoking` and `revoked` states, and deterministic duplicate/recovery handling
211
-
-issue`#86` /`M9-T09`is the active implementation slice on the current branch: the node API
212
-
and wire codec now expose the approved lease-centric surface with `get_lease`, flattened
213
-
committed results, `current_lease_id`, and ordered `member_resource_ids`, while keeping the
214
-
trusted-core naming and apply path intact
215
-
- targeted validation on the active `#86` branch currently includes
216
-
`cargo test -p allocdb-node api -- --nocapture`
217
-
- the active `#86` branch keeps the `T09` / `T10` boundary explicit: it finishes the lease
218
-
transport/read/recovery surface without adding new replication or view-change behavior
219
-
- the next planned code-bearing slices after `#86` remain `M9-T10` replication preservation and
220
-
`M9-T11` broader regression coverage
211
+
-PR`#93` merged`M9-T09`on `main`: the node API and wire codec now expose the approved
212
+
lease-centric surface with `get_lease`, flattened committed results, `current_lease_id`, and
213
+
ordered `member_resource_ids`, while keeping the trusted-core naming and apply path intact
214
+
- issue `#87` / `M9-T10` is the active implementation slice on the current branch: preserve
215
+
bundle ownership, fencing outcomes, and revoke safety across replication, failover, and replica
216
+
rejoin without introducing a second apply path
217
+
-targeted validation on the active `#87` branch currently centers on `cargo test -p allocdb-node replicated_simulation -- --nocapture`,
218
+
`cargo test -p allocdb-node replica -- --nocapture`, and `./scripts/preflight.sh`
219
+
- the active `#87` branch keeps the `T10` / `T11` boundary explicit: it proves replicated-path preservation for the approved lease primitives, while broader scenario expansion stays in `M9-T11`
220
+
- the next planned code-bearing slice after `#87` remains`M9-T11` broader regression coverage
0 commit comments