Analysis of the Datum Cloud DNS service (dns-operator) for production readiness, combining an infra-deployment survey, peer service comparison within the platform, and Google SRE production-readiness standards from the SRE books and CRE launch checklist.
The DNS operator has:
Service resource published, ServiceConfiguration planned (Phase 2, issue #44)
The project already has macOS rendering (Metal), font (CoreText), and platform
(Cocoa/AppKit via plt) support in the C++ source and build.py. The Nix
expression is the only blocker — it currently hardcodes Linux-only deps and
marks badPlatforms = lib.platforms.darwin.
Review of global-server-load-balancing/README.md on branch gslb-design,
cross-checked against issue #833 and the working context doc.
The context doc (section 8) records an architectural position: "Both PoP
Time range: 30-day average (increase[30d] / 2,592,000s)
Data source: Victoria Metrics via MCP — pdns_auth_*_queries counters on datum-managed-auth-dns
Timestamp: 2026-07-13T20:15 UTC
PowerDNS auth exposes four cumulative COUNTER metrics:
Date: 2026-07-09
All checks pass. The containerlab deploy is fully operational with transit underlay, fabric eBGP, tenant iBGP with route reflector, SRv6 EVPN route distribution, cross-site connectivity, and VPC isolation all working correctly.
| #!/usr/bin/env bash | |
| set -euo pipefail | |
| # transfer-issue.sh — Transfer a GitHub issue across repos and organizations. | |
| # | |
| # Usage: ./transfer-issue.sh [--force-public] <source-issue-url> <dest-org/repo> | |
| # | |
| # Example: | |
| # ./transfer-issue.sh https://github.com/srcorg/srcrepo/issues/42 destorg/destrepo |
Milestone status: Overdue (due Jun 26, 2026), 10% complete, last updated Jun 24, 2026. 9 open issues, 1 closed.
| # | Issue | Assignee | Sub-tasks | Labels | Stuck Because |
|---|---|---|---|---|---|
| #682 | Launch Datum Compute | @privateip | 3/14 done | off-track | No branches or PRs. Massive scope. Sub-issues updated Jul 1 but no code. |
| #713 | Physical inventory for Milo | @ecv | 6/10 done | — | Sub-issues last updated Jun 11–17. No branches/PRs. |
| #391 | Envoy AI Gateway Enablement | @savme | — | — | No branches, PRs, project board, or sub-tasks. Oldest issue (Oct 2025). |
| #594 | Galactic VPC + Datum Compute | @privateip | 4/5 done | off-track | Sub-issues last upda |
Yes — JumpCloud can model the same identity map, though most of the cross-platform handles would live in custom attributes rather than native fields.
team.toml field |
JumpCloud equivalent |
|---|---|
name |
firstName + lastName (native) |
datum |
email (native) |
| Takes up 30G across the two GPUs: | |
| Sat May 23 16:19:22 2026 | |
| +-----------------------------------------------------------------------------------------+ | |
| | NVIDIA-SMI 595.58.03 Driver Version: 595.58.03 CUDA Version: 13.2 | | |
| +-----------------------------------------+------------------------+----------------------+ | |
| | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | |
| | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | |
| | | | MIG M. | |
| Component | Details |
|---|---|
| Host type | QEMU/KVM virtual machine |
| CPU | Intel Core (Broadwell, no TSX, IBRS) — 8 vCPUs (8 sockets × 1 core × 1 thread) |
| RAM | 31 GB total, ~10 GB available |
| GPU | Cirrus Logic GD 5446 (emulated VGA — no CUDA, no GPU inference) |