Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-08-23 Thread Akshay Kumar Sanghai
how do you find KloudBuster so far? Does it do its job and >> fit your needs? J >> >> >> >> Thanks very much! >> >> >> >> Regards, >> >> Yichen >> >> >> >> *From:* Alec Hothan (ahothan) >> *Sent:* Tuesd

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-04-08 Thread Alec Hothan (ahothan)
questions)" 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 ge

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-04-07 Thread Akshay Kumar Sanghai
gt; > > > Thanks very much! > > > > Regards, > > Yichen > > > > *From:* Alec Hothan (ahothan) > *Sent:* Tuesday, April 5, 2016 9:54 AM > *To:* Akshay Kumar Sanghai ; Yichen Wang > (yicwang) > *Cc:* OpenStack List > > *Subject:* Re: [openstack-dev] [kloudb

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-04-06 Thread Yichen Wang (yicwang)
quot;Yichen Wang (yicwang)" mailto:yicw...@cisco.com>> Cc: Alec Hothan mailto:ahot...@cisco.com>>, OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem Hi Yichen, Thanks a lot . I will try with v

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-04-05 Thread Alec Hothan (ahothan)
.@cisco.com>> Cc: Alec Hothan mailto:ahot...@cisco.com>>, OpenStack List 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, Aks

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-30 Thread Akshay Kumar Sanghai
r the VM to be up running. > > > > Thanks very much! > > > > Regards, > > Yichen > > > > *From:* Akshay Kumar Sanghai [mailto:akshaykumarsang...@gmail.com] > *Sent:* Wednesday, March 30, 2016 7:31 AM > *To:* Alec Hothan (ahothan) > *Cc:* OpenSt

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-30 Thread Yichen Wang (yicwang)
ykumarsang...@gmail.com] Sent: Wednesday, March 30, 2016 7:31 AM To: Alec Hothan (ahothan) Cc: OpenStack List ; Yichen Wang (yicwang) 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

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-30 Thread Akshay Kumar Sanghai
day, March 28, 2016 at 6:51 AM > To: OpenStack List , Alec Hothan < > ahot...@cisco.com> > Cc: "Yichen Wang (yicwang)" > Subject: Re: [openstack-dev] [kloudbuster] authorization failed problem > > Hi Alec, > Thanks for the help. I ran into another problem. At

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-28 Thread Alec Hothan (ahothan)
:ahot...@cisco.com>> Cc: "Yichen Wang (yicwang)" 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 r

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-28 Thread Akshay Kumar Sanghai
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,

Re: [openstack-dev] [kloudbuster] authorization failed problem

2016-03-23 Thread Alec Hothan (ahothan)
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 (