hi Graham as far as I understand you'll need to stick to the v2 API to use Apache Brooklyn, as that is what is currently supported by the underlying jclouds library.
As it happens this was a topic of conversation this very morning on the jclouds mailing list [1], so there may be some progress on this in the near but not immediate future. [1] https://lists.apache.org/thread.html/b1162446800011a8343e67a7cda55a5033754881529c74fafa47109b@%3Cdev.jclouds.apache.org%3E regards Geoff On Wed, 3 May 2017 at 14:16 Graham Ashby <[email protected]> wrote: > I need some help with deploying to openstack... > > For some reason, our openstack-nova identity endpoint has to be the v3 > version: > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3 > > When I try to deploy, I get an exception: > org.jclouds.http.HttpResponseException: command: POST > https://canhdc-controller.canlab.ibm.com:5000/v3/tokens HTTP/1.1 failed > with response: HTTP/1.1 404 Not Found; content: [{"error": {"message": > "The resource could not be found.", "code": 404, "title": "Not Found"}} > > Do I need to somehow tell jclouds to use the v3 api? Or am I stuck > needing to use the v2.0 api? > > Also, our https endpoint is self signed, so I need to set OS_CACERT to > make the openstack CLI work. > > For reference, here's the appropriate bit of my yaml: > > jclouds:openstack-nova: > endpoint: https://canhdc-controller.canlab.ibm.com:5000/v3 > identity: "fa4c7f59767d487682a7798550b946bd:[email protected]" > credential: ******** > displayName: hdc-canada > > imageId: Lobby/e3b40a4f-4e82-41b3-857c-68799c4a9009 > hardwareId: Lobby/m1.small > keyPair: openstack-gsa-gen > keyPairName: openstack-gsa-gen > loginUser: cloudusr > loginUser.privateKeyFile: /home/cloudusr/.ssh/openstack-gsa-gen.pem > > jclouds.openstack-nova.cacert: /opt/brooklyn/ca-1/hdc.pem > jclouds.openstack-nova.openIptables: true > jclouds.openstack-nova.selinux.disabled: true > jclouds.openstack-nova.auto-create-floating-ips: true > jclouds.openstack-nova.auto-generate-keypairs: false > >
