Open Stack

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) <yicwang at 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. J
>
>
>
> 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:akshaykumarsanghai at gmail.com]
> *Sent:* Wednesday, March 30, 2016 7:31 AM
> *To:* Alec Hothan (ahothan) <ahothan at cisco.com>
> *Cc:* OpenStack List <openstack-dev at lists.openstack.org>; Yichen Wang
> (yicwang) <yicwang at 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.
>
> [image: 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) <ahothan at 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 <akshaykumarsanghai at gmail.com>
> *Date: *Monday, March 28, 2016 at 6:51 AM
> *To: *OpenStack List <openstack-dev at lists.openstack.org>, Alec Hothan <
> ahothan at cisco.com>
> *Cc: *"Yichen Wang (yicwang)" <yicwang at 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) <ahothan at 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
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/0f557def/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 28812 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160330/0f557def/attachment.png>