Not stupid — I think it's genuinely useful. nvme discover today fetches one level and prints it; a recursive variant would follow referral DCs and print the whole reachable tree without connecting anything — the read-only mirror of what connect-all already does, and a handy "show me everything this fabric exposes" diagnostic.
I'd keep it as its own nvme-cli enhancement rather than fold it into this RFC, since it is independent of the daemon. Two things it would need: referral-loop detection (a misconfigured fabric can have cyclic referrals) and a way to present the tree (indent per level, or flatten with a "via" column). I'm happy to file a separate issue/RFC for it; it doesn't block discoverd either way.
Originally posted by @martin-belanger in #3442 (comment)
Not stupid — I think it's genuinely useful.
nvme discovertoday fetches one level and prints it; a recursive variant would follow referral DCs and print the whole reachable tree without connecting anything — the read-only mirror of whatconnect-allalready does, and a handy "show me everything this fabric exposes" diagnostic.I'd keep it as its own nvme-cli enhancement rather than fold it into this RFC, since it is independent of the daemon. Two things it would need: referral-loop detection (a misconfigured fabric can have cyclic referrals) and a way to present the tree (indent per level, or flatten with a "via" column). I'm happy to file a separate issue/RFC for it; it doesn't block discoverd either way.
Originally posted by @martin-belanger in #3442 (comment)