Use FQDNs when referencing cluster machines.

The following points are worth recording for future reference:

* To make sure ansible reports the correct FQDN for each machine, the
  FQDN needs to be present in the /etc/hosts file. Even if the hostname
  of a machine is set to the FQDN, ansible cuts it short at the first
  period. I'm not sure I like this, but that's how it is even, after a
  fair amount of discussion on ansible's devel list and github issues;
* The rsyslog.conf files also change to look for files with the FQDN in
  them because the behaviour of the hadoop ecosystem tools is to use the
  full hostname (not truncated) output of the 'hostname' command to
  determine the name of the log files.

Conflicts (due to cherry-picking, all in files that don't exist in
master any longer):

	roles/cdh_hadoop_config/templates/mapred-site.xml
	roles/cdh_oozie/templates/oozie-site.xml
	roles/logstash_index_cleaner/templates/logstash-index-cleaner.cron.d
Fix #8: the handler "reload apache2" should be in the apache2 role. [ci skip]
Merge pull request #10 from amirhhz/fqdns-everywhere

Use FQDNs when referencing cluster machines
Fix that belongs to #10.