nettest does not take ceph.conf into account about deepsea HOT 4 CLOSED

Question : do we expect this test to run only after deepsea has run stage 3 successfully?

from deepsea.

I am very keen to reduce the combinatorial explosion with ipv4 addresses. So advice guidance here would be very useful.

from deepsea.

We could also use traceroute, this would highlight any issues and is easy to implement.

This might help also diagnose other issues?

from deepsea.

I believe this issue is addressed now. The default command will try all addresses in the Salt cluster. When a cluster name is supplied, only the public and cluster networks are used. For example,

salt-run net.ping
salt-run net.ping ceph OR salt-run net.ping cluster=ceph

However, there may be addresses that an admin wishes to exclude such as those dedicated to gateways. Add an exclude parameter with or without the Salt modifiers and the related minions or addresses will be removed from the list. For example,

salt-run net.ping exclude=igw2.ceph
salt-run net.ping exclude=[email protected]

salt-run net.ping exclude=192.168.21.6
salt-run net.ping [email protected]

salt-run net.ping exclude=192.168.21.0/28
salt-run net.ping [email protected]/28

And both parameters can be specified in multiple ways.

salt-run net.ping cluster=ceph exclude=mon2.ceph,mon3.ceph
salt-run net.ping ceph mon2.ceph,mon3.ceph
salt-run net.ping ceph [email protected],mon3.ceph

from deepsea.