Can you describe what you mean by "do not have a cinder service"? Can you provide the output of "keystone service-list"?
We'd have to know a bit more about what you have been doing: how did you install your openstack, how did you install kloudbuster, which kloudbuster qcow2 image version did you use, who did you run kloudbuster (cli or REST or web UI), what config file have you been using, complete log of the run (including backtrace)... But the key is - you should really have a fully working openstack deployment before using kloudbuster. Nobody has never tried so far to use kloudbuster without such basic service as cinder working. Thanks Alec From: Akshay Kumar Sanghai <akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>> Date: Monday, March 28, 2016 at 6:51 AM To: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>, Alec Hothan <ahot...@cisco.com<mailto:ahot...@cisco.com>> Cc: "Yichen Wang (yicwang)" <yicw...@cisco.com<mailto:yicw...@cisco.com>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem Hi Alec, Thanks for the help. I ran into another problem. At present I do not have a cinder service. So ,when i am trying to run kloudbuster, I am getting this error: "EndpointNotFound: publicURL endpoint for volumev2 service not found" Is it possible to run the scale test (creation of VMs, router, network) without having a cinder service? Any option that can be used so that kloudbuster can run without cinder. Thanks, Akshay On Wed, Mar 23, 2016 at 9:05 PM, Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote: Hi Akshay The URL you are using is a private address (http://192.168.138.51:5000/v2.0) and is likely the reason it does not work. If you run the kloudbuster App in the cloud, this app needs to have access to the cloud under test. So even if you can access 192.168.138.51 from your local browser (which runs on your workstation or laptop) it may not be accessible from a VM that runs in your cloud. For that to work you need to get an URL that is reachable from the VM. In some cases where the cloud under test is local, it is easier to just run kloudbuster locally as well (from the same place where you can ping 192.168.138.51). You can either use a local VM to run the kloudbuster image (vagrant, virtual box...) or just simpler, install kloudbuster locally using git clone or pip install (see the installation instructions in the doc http://kloudbuster.readthedocs.org/en/latest/). Regards, Alec
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
