From: Akshay Kumar Sanghai <akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>> Date: Thursday, April 7, 2016 at 1:46 AM To: "Yichen Wang (yicwang)" <yicw...@cisco.com<mailto:yicw...@cisco.com>>, Alec Hothan <ahot...@cisco.com<mailto:ahot...@cisco.com>> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem
Thanks Yichen and Alec. Yichen, It was what I was looking for. I started with Rally , but faced problem with defining the number of router per tenant and traffic generation. Then, I found that there is a new project Kloudbuster. I faced some issues , but with your help , I succeeded in running it. One suggestion: I think Rally developers are also trying for the traffic generation. So just make sure, we don't have two things for the same work under the openstack umbrella. We're also using Rally to test our control plane. Data plane testing at scale is a whole different ballgame (than control plane) and we had very specific scale test requirements in mind for our own usage as far back as late 2014, which is why we developed kloudbuster in Feb 2015 with HTTP traffic at scale. At that time there was no solution available for doing automated data plane scale testing, even today as you can see the number of solutions is actually very limited. Anyway if the Rally developers are interested to discuss about it, I or Yichen would be happy to discuss. One Request: I have not contributed to any project till now. I am interested in contributing to the Kloudbuster project. Please suggest how to start and help me in getting up to speed. There is currently no bug backlog in kloudbuster. Since we use it quite a lot, every issue we run into is fixed pretty quickly but it is likely there are uncovered issues when run in a different environment. There are also obviously many feature enhancements of any size but we only add when there is an ask as we want to keep the code small (do one thing but do it well). If you use it and find a bug or need some enhancement, you're welcome to contribute and we can help root cause and fix. Have you been looking for traffic generation for any particular purpose? We use it for testing our openstack data plane at scale (and storage now). Regards, Alec Regards, Akshay On Wed, Apr 6, 2016 at 1:44 PM, Yichen Wang (yicwang) <yicw...@cisco.com<mailto:yicw...@cisco.com>> wrote: Hi, Akshay, Just curious, how do you find KloudBuster so far? Does it do its job and fit your needs? ☺ Thanks very much! Regards, Yichen From: Alec Hothan (ahothan) Sent: Tuesday, April 5, 2016 9:54 AM To: Akshay Kumar Sanghai <akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>>; Yichen Wang (yicwang) <yicw...@cisco.com<mailto:yicw...@cisco.com>> Cc: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem Akshay, Note that version 6 is now released so please use the official image from the OpenStack App Catalog and update your code to latest. The doc has also been updated, you might want to have a look at the new arch section and gallery - those should help you with the questions you had below regarding the scale test staging and traffic flows. http://kloudbuster.readthedocs.org/en/latest/index.html Thanks Alec From: Akshay Kumar Sanghai <akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>> Date: Wednesday, March 30, 2016 at 11:11 AM To: "Yichen Wang (yicwang)" <yicw...@cisco.com<mailto:yicw...@cisco.com>> Cc: Alec Hothan <ahot...@cisco.com<mailto:ahot...@cisco.com>>, OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem Hi Yichen, Thanks a lot . I will try with v6 and reach out to you for further help. Regards, Akshay On Wed, Mar 30, 2016 at 11:35 PM, Yichen Wang (yicwang) <yicw...@cisco.com<mailto:yicw...@cisco.com>> wrote: Hi, Akshay, From the log you attached, the good news is you got KloudBuster installed and running fine! The problem is the image you are using (v5) is outdated for the latest KloudBuster main code. ☺ Normally for every version of KloudBuster, it needs certain version of image to support the full functionality. In the case when new feature is brought in, we tag the main code with a new version, and bump up the image version. Like from v5 to v6, we added the capability to support storage testing on cinder volume and ephemeral disks as well. We are right in our time for publishing the v6 image to the OpenStack App Catalog, which may take another day or two. This is why you are seeing the connection to the redis agent in KB-Proxy is failing… In order to unblock you, here is the RC image of v6 we are using right now, replace it in your cloud and KloudBuster should be good to go: https://cisco.box.com/s/xelzx15swjra5qr0ieafyxnbyucnnsa0 Now back to your question. -Does the server side means the cloud generating the traffic and client side means the the cloud on which connections are established? Can you please elaborate on client, server and proxy? [Yichen] It is the other way around. Server is running nginx, and client is running the traffic generator (wrk2). It is like the way we normally understand. Since there might be lots of servers and clients in the same cloud, so KB-Proxy is an additional VM that runs in the clients side to orchestrate all client VMs to generate traffic, collect the results from each VM, and send them back to the main KloudBuster for processing. KB-Proxy is the where the redis server is sitting, and acts as the proxy node to connect all internal VMs to the external network. This is why a floating IP is needed for the proxy node. -while running the kloudbuster, I saw "setting up redis connection". Can you please expain to which connection is established and why? Is it KB_PROXY? [Yichen] As I explained above, KB-Proxy is the bridge between internal VM and external world (like the host you are running KloudBuster from). “Setting up redis connection” means the KloudBuster is trying to connect to the redis server on the KB-Proxy node. You may see some retries because it does take some time for the VM to be up running. Thanks very much! Regards, Yichen From: Akshay Kumar Sanghai [mailto:akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>] Sent: Wednesday, March 30, 2016 7:31 AM To: Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>> Cc: OpenStack List <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>; Yichen Wang (yicwang) <yicw...@cisco.com<mailto:yicw...@cisco.com>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem Hi Alec, Thanks for clarifying. I didnot have the cinder service previously. It was not a complete setup. Now, I did the setup of cinder service. Output of keystone service list. [Inline image 1] I installed the setup of openstack using the installation guide for ubuntu and for kloudbuster, its a pypi based installation. So, I am running kloudbuster using the CLI option. kloudbuster --tested-rc keystone-openrc.sh --tested-passwd ***** --config kb.cfg contents of kb.cfg: image_name: 'kloudbuster' I added the kloudbuster v5 version as glance image with name as kloudbuster. I don't understand some basic things. If you can help, then that would be great. -Does the server side means the cloud generating the traffic and client side means the the cloud on which connections are established? Can you please elaborate on client, server and proxy? -while running the kloudbuster, I saw "setting up redis connection". Can you please expain to which connection is established and why? Is it KB_PROXY? Please find attached the run of kloudbuster as a file. I have still not succeeded in running the kloudbuster, some errors. I appreciate your help Alec. Thanks, Akshay On Mon, Mar 28, 2016 at 8:59 PM, Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote: 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
