{"push_id":593840782,"size":1,"distinct_size":1,"ref":"refs/heads/fix_issue_9","head":"e8c61744e5ba6b0d4fb856b9b53beb44d1b87702","before":"c653ecf7990aeedd26cacb0ca6cdab861f61e59b","commits":[{"sha":"e8c61744e5ba6b0d4fb856b9b53beb44d1b87702","author":{"email":"81d2d8bfc68ffe7440a12e14cbafcbd58909d086@defunct.ca","name":"Matt Thompson"},"message":"Dynamically determine hostname\n\nCurrently, we assume hosts returned from a `nova service-list` and\n`neutron agent-list` are FQDNs which is an incorrect assumption. The\noriginal change was made as we ran these MaaS-related playbooks/roles\non hosts w/ incorrectly configured hostnames (meaning a `hostname -s`\nwould still return the FQDN), and therefore the hosts being returned\nfrom the above two commands were FQDNs.\n\nThis change first loops through the physical hosts and runs a `python\n-c \"import socket; print socket.gethostname()\"` and then saves that\nvalue in maas_gethostname.  For the two checks that are run against\nphysical nodes (`neutron_linuxbridge_agent_check` and\n`nova_compute_check`), we use maas_gethostname from the physical node\nand replace all remaining references of `ansible_fqdn` to\n`ansible_hostname`.","distinct":true,"url":"https://api.github.com/repos/mattt416/rpc-extras/commits/e8c61744e5ba6b0d4fb856b9b53beb44d1b87702"}]}