vim configuration does not allow the INSECURE property

[Manuel Buil]

There are openstack deployments which use self-signed certificates which require the variable OS_INSECURE to be 'true' in order to communicate with endpoints that use SSL. This is unfortunately not possible to configure in the vim config file when registering a vim. Therefore, tacker is does not work on openstack deployments that use self-signed certificates

[yong sheng gong (gongysh)]

Taseer Ahmed, do you have time for it?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/529374
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=e1f3d8285cbf8a662605027e62fb23d4ff7e4a2f
Submitter: Zuul
Branch: master

commit e1f3d8285cbf8a662605027e62fb23d4ff7e4a2f
Author: Manuel Buil <email address hidden>
Date: Wed Dec 20 18:02:33 2017 +0100

    Check if certificates must be verified in the vim

    This patch tries to fix the bug: https://bugs.launchpad.net/tacker/+bug/1719841

    To disable the verification, a parameter must be included in vim_config.yaml
    file.
    cert_verify: 'False'

    Co-Authored-By: Cong Phuoc Hoang <email address hidden>
    Closes-Bug: #1719841

    Change-Id: If9c8eab81bad2028ae146598d559831bc51cbbf5
    Signed-off-by: Manuel Buil <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 0.9.0 release.