Hi all, Maybe this will be a good guideline for all OPNFV projects when they consume or provide APIs.
Regards, Julien yaohelan <yaohe...@huawei.com>于2017年3月10日周五 上午11:15写道： > Hi Tomofumi, > > > > I am a committer of Functest. I will try to enable HTTPS for Functest. > > > > There is a JIRA item tracking the status. > > https://jira.opnfv.org/browse/FUNCTEST-757 > > > > > > *From:* opnfv-tech-discuss-boun...@lists.opnfv.org [mailto: > opnfv-tech-discuss-boun...@lists.opnfv.org] *On Behalf Of *Tomofumi > Hayashi > *Sent:* Thursday, March 02, 2017 9:14 PM > > > *To:* trevor.coo...@intel.com; opnfv-tech-discuss@lists.opnfv.org > *Subject:* [opnfv-tech-discuss] [functest][dovetail] OpenStack HTTPS > transport support in functest/dovetail > > > > Hi folks, > > > > Let me clarify HTTPS support status and plan of > functest/yardstick/dovetail. > > > > I tried to run functest/dovetail against TripleO deployment and find that > functest script, leveraged by dovetail, only works with HTTP (!= HTTPS) for > OpenStack API (see verify_connectivity(): functest/ci/check_os.py). In > addition, more modification is required certificate (such as self-signed > one). > > > > At that time, OPNFV testing project is mainly consumed by OPNFV platforms > (e.g. Apex). But in the future, at least dovetail should be used for C&C > (compliance and certification) in various OpenStack platform and some of > them does not support HTTP transport for OpenStack API (mostly due to > security reason). So I suppose we should support HTTPS OpenStack API in > dovetail and functest. > > > > What do you think about it? > > > > Regards, > > Tomofumi > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss >
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
