The FQDN and the "system hostname" in client and servers.

[javiroman]

The deploop system uses the JSON file to indetify the servers in the cluster. Right now the user can use FQDN or unqualified hostnames in this JSON file. Right now, the deploop client is asking for servers using the "unqualified hostname" even the user set up the FQDN in the JSON file.

This behaviour works only if the /etc/hosts file is properly set up with entries like this:

xxx.xxx.xxx.xxx "unqualified hostname" "FQDN"

On the server side, the server self identify using the "system hostname" (the unqualified hostname) so the client in the current configuration is working well.

The server side must be configurated with the system hostname as "unqualified hostname" (-> /etc/sysconfig/network: HOSTNAME=unqualified-host-name).

We have to work in the deploop cli tool in order to avoid miss configuration from the side of the user.

[jfrodriguez]

Note: The /etc/hosts file contains one entry per line, consisting of an IP address, a hostname, and an optional list of aliases for the hostname. Then, the right format would be:

IPAddress Hostname Alias
10.0.0.1 nn1-cluster1.domain.org nn1-cluster1