Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Thu, 02 Mar 2017 04:35:28 -0800 

On 03/02/2017 02:15 PM, Marco Varlese wrote:

On Thu, 2017-03-02 at 13:41 +0200, Tapio Tallgren wrote:

On 03/02/2017 10:45 AM, Marco Varlese wrote:

Hi,
In my previous email I did not mention the use of the docker image, I was trying to install it on the system following the online Yardstick documentation. 

Why do I need to use the docker image necessarily?


I have been using a kvm VM for Yardstick. Docker is easier to use 
since you do not need to set up the virtenv etc.



Also, are there any particular reasons/dependencies why it has to be 
Ubuntu 14.04? It's quite "old" and the new LTS (16.04) has been out 
for a while.





I just used the Xenial Ubuntu and it worked equally well. I 
downloaded and booted the Xenial image, git cloned Yardstick to it, 
and then installed Yardstick on it. For reporting, I used a Docker image.

How did you setup the Openstack environment?
In my case I cloned DevStack (master) and installed it on the box.

My setup has everything installed onto one single VM:
1) DevStack (with Heat)
2) Yardstick with its virtual-env


And when I try launch the ping.yaml test case I get the error 
mentioned in my prev email...


Any thoughts/ideas?




I had a physical deployment. Since you are running everything in a VM, 
it is best to use the virtenv and not launch another VM.
Can you use the "openstack server list" command from the Yardstick 
virtenv? Do you see cirros-0.3.3 when you do "openstack image list"? I 
think there was some confusion about cirros-0.3.3 and cirros-0.3.4, but 
I cannot find the reference right now.


-Tapio



Thanks,
Marco



-Tapio



Thanks,
Marco

On Thu, 2017-03-02 at 08:35 +0000, chenjiankun wrote:


Hi Marco,

What’s the latest status of this issue?

Does my solution be OK for you?

I’m looking forward to your reply.

Regards,

Jack Chan

*From:*chenjiankun
*Sent:* Thursday, February 23, 2017 5:25 PM
*To:* 'Marco Varlese'

*Cc:* [email protected] 
<mailto:[email protected]>
*Subject:* RE: [opnfv-tech-discuss] [yardstick] Yardstick run-time 
issue


Hi Marco,

I am Jack from yardstick team.


I haven’t experienced this issue before. But it seems there are 
some errors with the cirros image.


I think you can try to run ping test case in the follow steps:


1.*docker run -itd --privileged --name yardstick 
opnfv/yardstick:latest*


2.*docker exec -it yardstick bash*

3.config and source the openstack openrc file(include EXTERNAL_NETWORK)

4.load images: you can execute the follow command in this directory:

*cd /home/opnfv/repos/yardstick*

*bash tests/ci/load_image.sh*

5.run test case

*yardstick -d task start sample/ping.yaml*

BTW, can you tell me:

1.what’s your Openstack version in your SUT?

2.Which yardstick docker are you using?


If you have any other questions, please feel free to let me know. 
Thanks.


Best Regards,

Jack Chan

-----Original Message-----

From: [email protected] 
<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of 
Marco Varlese

Sent: Tuesday, February 21, 2017 7:37 PM

To: [email protected] 
<mailto:[email protected]>

Subject: [opnfv-tech-discuss] Yardstick run-time issue

Hi,


I'm trying to setup an environment to deploy Yardstick; to start 
with I'm doing everything in one single Virtual machine.



The Virtual Machine basically represent both the Jumphost and the 
SUT. I understand this is not the best to measure performance but 
my real lab setup is being currently worked on and I'd like to get 
ahead of the game with learning.



I have an Openstack environment installed via Devstack (master 
branch) including Heat.



When I try and launch the ping.yaml test case I get the following 
error:



2017-02-21 12:18:29,515 yardstick.orchestrator.heat heat.py:440 
INFO Creating stack 'demo-054b1f93'



error: failed to deploy stack: 'ERROR: Property error: : 
resources.ares.demo-



054b1f93.properties.image: : "cirros-0.3.3" does not validate 
glance.image (constraint not found)'


Has anybody experienced this issue before?

Any help or input would be much appreciated.

Thanks,

Marco

_______________________________________________

opnfv-tech-discuss mailing list


[email protected] 
<mailto:[email protected]>


https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss




_______________________________________________
opnfv-tech-discuss mailing list

[email protected] 
<mailto:[email protected]>

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



_______________________________________________
opnfv-tech-discuss mailing list

[email protected] 
<mailto:[email protected]>

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss




_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss






















					Reply via email to