[Deepsea-users] Antw: [ses-users] Deploying on 3 networks with DeepSea
Martin.Weiss at suse.com
Mon Nov 6 14:30:42 MST 2017
Do we know if any SES/ceph service or installation / configuration routine relies on "proper" DNS setup (forward and reverse lookup for public network addresses of all servers in the cluster) or does ceph use IP addresses only for sure?
What can / will / might happen in case the "mon name" resolves via DNS to the admin network address and not the public network address?
does the following scenario ring any alarm bells with anyone?
The cluster has a salt-master, MONs and OSDs. All nodes have 3 networks: a
management network and public- and cluster-network. All nodes have a hostname
that resolves via DNS to the ip on the management network. The ips on cluster-
and public-network don't correspond to DNS names.
The MONs derive their IDs from the short hostname, which would resolve to the ip
addresses on the management network if one would attempt that.
The cluster deployed and operates fine. Is there any conceivable disadvantage
with this setup? For example:
Should there be dns names for the public-network ip addresses?
Does DeepSea have any issue (or will have issues in the future) with running on
the management network (the salt master has access to the public-network)?
Imho this setup should work fine, but I might be missing something.
Engineer Enterprise Storage
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Deepsea-users