Hi all, We have some indication from Compass as they need to downgrade their efforts to support Keystone V2.0 for Opera in D , where as JOID needs to upgrade its support for Keystone v3.0 API for E.
Please comment if my understanding is correct by installers and we can discuss this in tomorrow's MANO WG meeting for E-Release minimum baselines suggested by David McBride Release manager OPNFV as OpenStack Ocata and Keystone API v3.0. Thanks Prakash [cid:jira-generated-image-avatar-b775a13f-c1b8-459a-a31f-4cc6ffefbeb8] Harry Huang<https://jira.opnfv.org/secure/ViewProfile.jspa?name=huangxiangyu> commented on [Improvement] COMPASS-524<https://jira.opnfv.org/browse/COMPASS-524> Re: Support Keystone Api V2 <https://jira.opnfv.org/browse/COMPASS-524> Compass now has a open-o scenario (os-nosdn-openo-noha) has this Api issue which mainly because open-o sun release and juju2.0 are using keystone Api v2 while compass creates keystone Api v3 as default. This is the only scenario which may fail because of Api v3 in compass. However you can still be authorized with api v2 openrc file to access almost full openstack service except some identity function. So far compass manage to install open-o and juju-controller using api v2 rc file to authorize with v3. Considering open-o mercury is scheduled to release in this April, we may not be talking this issue two months later. [Add Comment]<https://jira.opnfv.org/browse/COMPASS-524#add-comment> Add Comment<https://jira.opnfv.org/browse/COMPASS-524#add-comment> This message was sent by Atlassian JIRA (v7.0.4#70113-sha1:3aced62) [Atlassian logo]
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
