Comment 5 for bug 1846799

Reviewed: https://review.opendev.org/690082
Committed: https://git.openstack.org/cgit/starlingx/ansible-playbooks/commit/?id=8849dc98294c7410717b30ebd39e0c5ab8cdbed4
Submitter: Zuul
Branch: master

commit 8849dc98294c7410717b30ebd39e0c5ab8cdbed4
Author: Tao Liu <email address hidden>
Date: Tue Oct 22 09:44:11 2019 -0400

    Allow subcloud to use central-cloud's local registry

    Add the following to bootstrap to setup the environment
    which allows the subcloud to use central-cloud's local registry
    via the OAM interface

     - Add system controller oam floating address and subnet support
     - Populate the system controller oam address pool and network
       on subcloud
     - Add 'registry.central' to the host file on subcloud until dnsmasq
       takes over after the first unlock
     - Copy the central-cloud's local registry certificate to the
       subcloud's docker certificate directory
     - Add docker registry public IP and realm host support
     - Add 'registry.central' and system_controller_oam_floating_address
       to the default_no_proxy list on subcloud

    Change-Id: I05bdbac30c25da371ffa879babfc8df2e88f2812
    Partial-Bug: 1846799
    Signed-off-by: Tao Liu <email address hidden>