)]}'
{"lib/facter/alt_fqdns.rb":[{"author":{"_account_id":8042,"name":"Jiří Stránský","email":"jistr@redhat.com","username":"jistr"},"change_message_id":"6a459df137d8fe42d7685e78264a91288a3b8ab4","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    end"},{"line_number":32,"context_line":"  end"},{"line_number":33,"context_line":"end"},{"line_number":34,"context_line":"# Ctlplane fqdn is an alias for just the fqdn. But we enable it here so we can"},{"line_number":35,"context_line":"# use it\u0027s value using the network name in t-h-t."},{"line_number":36,"context_line":"Facter.add(\u0027fqdn_ctlplane\u0027) do"},{"line_number":37,"context_line":"  setcode do"}],"source_content_type":"text/x-ruby","patch_set":2,"id":"9a89bdaa_90b939ce","line":34,"updated":"2016-09-12 09:46:49.000000000","message":"I think what we\u0027ve historically been referring to as \"ctlplane\" was the management network (IIUC to this date the management network is called \"ctlplane\" in Neutron). The FQDN is by default mapped to internal_api/storage network in network isolation scenarios (via *HostnameResolveNetwork params), that\u0027s probably not where we want to point fqdn_ctlplane fact, as would create a confusing situation.\n\nShould we just remove this fact? I can\u0027t see it being used from anywhere. Can\u0027t we use `fqdn` fact directly instead of aliasing `fqdn` as `fqdn_ctlplane`? (Perhaps i\u0027m just struggling to see where the problem lies.)","commit_id":"2b1ab4190f8d0e64ded1f9c2c017085e6155193b"},{"author":{"_account_id":8042,"name":"Jiří Stránský","email":"jistr@redhat.com","username":"jistr"},"change_message_id":"1a76e84d0dcdcef9423f5bb3b5354c493031026a","unresolved":false,"context_lines":[{"line_number":31,"context_line":"    end"},{"line_number":32,"context_line":"  end"},{"line_number":33,"context_line":"end"},{"line_number":34,"context_line":"# Ctlplane fqdn is an alias for just the fqdn. But we enable it here so we can"},{"line_number":35,"context_line":"# use it\u0027s value using the network name in t-h-t."},{"line_number":36,"context_line":"Facter.add(\u0027fqdn_ctlplane\u0027) do"},{"line_number":37,"context_line":"  setcode do"}],"source_content_type":"text/x-ruby","patch_set":2,"id":"9a89bdaa_e52004b3","line":34,"in_reply_to":"9a89bdaa_90b939ce","updated":"2016-09-12 10:54:49.000000000","message":"Discussed this with jaosorior on IRC, this would indeed be incorrect, as `fqdn` doesn\u0027t map onto ctlplane network in net iso scenarios.\n\nWe might need another per-host entry in /etc/hosts, that would map to ctlplane IP even when we deploy with an added management network. Currently there\u0027s probably no host entries pointing to ctlplane if we deploy full net iso + management network?","commit_id":"2b1ab4190f8d0e64ded1f9c2c017085e6155193b"}]}