Comment 3 for bug 1828880

Reviewed: https://review.opendev.org/658174
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=0dddabca4dd9c65996367f6a8e7140077f626558
Submitter: Zuul
Branch: master

commit 0dddabca4dd9c65996367f6a8e7140077f626558
Author: Tee Ngo <email address hidden>
Date: Thu May 9 14:29:25 2019 -0400

    Enable platform APIs from pods at bootstrap

    This commit enables access to platform service APIs from within
    Kubernetes pods prior to initial controller unlock. Prior to
    this changes, service endpoints were only reconfigured right
    before the unlock making sysinv apis inaccessible to services
    running inside the pods as they can not reach the loopback IP
    (127.0.0.1).

    This is achieved by reconfiguring service endpoints
      a) during initial bootstrap play from loopback IP to the provided
         management and OAM IPs
      b) during subsequent replays with newly provided management
         and/or oam network config values.

    Tests performed:
      - Bootstrap with defaults, verify endpoints
      - Change management subnet value and replay, verify endpoints
      - Change oam floating IP and replay, verify endpoints
      - Configure host for unlock
      - Unlock controller

    Story: 2004695
    Task: 30914
    Related-Bug: #1828880

    Change-Id: I9ef9d30bbf8713c75206b338aefd53c3e77db0cb
    Signed-off-by: Tee Ngo <email address hidden>