Updated NVMe oF Persistent Discovery Controllers (markdown)
wiki: cover nvme-stas in the PDC page Add a section explaining where nvme-stas (stafd/stacd) fits alongside nvme-cli's own two PDC mechanisms: why it exists (TP8009 zeroconf, TP8010 CDC/fabric zoning, which a stateless CLI can't do), its own config file and why it's separate, and stafd's PDC handling -- same EPCSD/referral-fallback algorithm and epcsd-poll-interval-minutes knob as nvme-discoverd, but a different default (auto, not no) and, currently, the only one of the two daemons that honors a per-DC persistent=force override. Verified against the local ~/nvme-stas checkout (staslib/ctrl.py, staslib/conf.py, etc/nvme/*.conf) rather than assumed from nvme-cli's side alone. Signed-off-by: Daniel Wagner <wagi@monom.org>
wiki: document NVMe-oF Persistent Discovery Controllers (PDC) Explain EPCSD, DUPRETINFO, and how nvme-cli 3.0's --persistent[=no|auto |force] on discover/connect-all/config-create decides whether to keep a discovery controller connected, how that's made permanent in nvme-fabrics.conf, how a discovery-log-page-change AEN reaches a running host (udev autoconnect vs. nvme-discoverd), how to verify it, and how it differs from 2.x's unconditional --persistent. Also notes that automatic PDC-by-default-per-port is not implemented yet (upstream nvme-cli#3112). Link the new page from the sidebar, Home, and the autoconnect how-to. Signed-off-by: Daniel Wagner <wagi@monom.org>