Comment 6 for bug 1671680

I concur that Nobuto's approach is best. I've been struggling with any other method of making this relation work and what I've found is that relating landscape-client to landscape-server:registration is that if you have landscape-server in HA mode, the registration code pins you to one of the landscape-servers and half of them work great and half die on the vine.

This relation must also go hand-in-hand with a relation to the haproxy service for url, ping-url, and ssl-public-key as is noted in comment #3.

This extra step is not needed if you register an SSL cert for an externally queryable FQDN beforehand, nail an IP in MAAS for the HAproxy unit to match the externally queryable name (or use the maas auto-dns name), and place the ca and full external DNS name for the landscape-haproxy units into the landscape-client configs.