multus cni using the wrong calico ipam configuration

[Matt Peters]

Brief Description
-----------------
The multus CNI configuration is using host-local rather than calico-ipam ipam configuration for the delegates configuration.

Severity
--------
Critical - pods launched after a swact can have duplicate IPs

Steps to Reproduce
------------------
Standard deployment configuration

Expected Behavior
------------------
The IPAM configuration must use the calico-ipam to ensure IP address allocations for the pool is tracked globally.

Actual Behavior
----------------
The host-local IPAM configuration uses the local file system and therefore introduces inconsistencies when the Calico controller moves to another host.

Reproducibility
---------------
100%

System Configuration
--------------------
All configurations

Branch/Pull Time/Commit
-----------------------
OS="centos"
SW_VERSION="19.01"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="20190521T132734Z"

JOB="STX_build_master_master"
<email address hidden>"
BUILD_NUMBER="111"
BUILD_HOST="starlingx_mirror"
BUILD_DATE="2019-05-21 13:27:34 +0000"

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Developer Testing

[Ghada Khalil (gkhalil)]

Marking as release gating; high priority as new pods are impacted after swact

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/661986

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/661986
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=5bf8a1f84fff02b390a687f18f49b3638fe1a488
Submitter: Zuul
Branch: master

commit 5bf8a1f84fff02b390a687f18f49b3638fe1a488
Author: Steven Webster <email address hidden>
Date: Wed May 29 08:23:52 2019 -0500

    Configure calico-ipam for multus k8s pod network

    This commit configures calico-ipam rather than host-local for the
    IPAM configuration on the k8s pod network delegate.

    Using host-local IPAM, there is a possibility for duplicate IP
    address allocation as the IP addresses are managed locally on
    the node's file system.

    Using calico-ipam, the IP addresses are managed across the
    cluster as a whole.

    Closes-Bug: #1830282

    Change-Id: I9a68fc164ad88f295827442ec83236c454af7907
    Signed-off-by: Steven Webster <email address hidden>