In DC system, subcloud local registry token realm is currently set to
oam floating IP address. When a new docker registry certificate is
installed in central cloud and get synced to subcloud, access to local
registry in subcloud is broken during certificate verfication, with error
like the following:
Error response from daemon: Get https://registry.local:9001/v2/: Get
https://10.10.10.13:9002/token/?account=admin&client_id=docker&
offline_token=true&service=192.168.101.2%3A9001:
x509: certificate is valid for 192.168.204.2, 10.10.10.3, not
10.10.10.13
This change updated subcloud local registry's token auth realm to be
domain name registry.local so the certificate verfication is against
the DNS names in the certifcate. This makes the verfication succeed.
Change-Id: I710e2e27461276db90cd9f9275655b5ecf00e342
Closes-Bug: 1851252
Signed-off-by: Andy Ning <andy.ning@windriver.com>