Reconfigure Ceph MONs to also listen on vlan35 (dedicated Ceph client network) #10
Labels
No labels
blocked
borg-backup
ceph
forgejo
in-progress
infra
netdata
nextcloud
p:high
p:low
p:medium
searxng
service-onboard
swarm-nodes
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
copper/ccnet-prod-devops#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The vmbr1/vlan35 NIC was built specifically for Ceph client traffic, but
ceph mon dumpshows all three MONs bind only to 10.10.10.20x (vlan10, mgmt) -- vlan35 is genuinely cluster-network-only (OSD-to-OSD replication/heartbeat), so the dedicated client NIC isn't usable for that purpose as-is. CephFS mounts (including the swarm managers) currently target the mgmt-network mon addresses instead.Making MONs additionally listen on vlan35 is a legitimate option but requires a separate, deliberate, quorum-safe reconfiguration of
public_network-- not a quick fix. Deferred since the mgmt-network path works fine today.See docs/swarm-build-narrative.md.