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

2017-03-17 Thread Marco Varlese 
See inline...

On Fri, 2017-03-17 at 06:47 +, chenjiankun wrote:
> 
> 
> Hi,
>  
> for the yardstick-plot, now it is deprecated now.
I really hope the documentation will be updated soon then... 
I find it the biggest obstacle a new comer faces if he/she wants to start using
Yardstick. Anyway, I mentioned this gap already...

> 

> If you want to parse data to the GUI, you can use the InfluxDB and Grafana.
I am using them already.

> > > > > > > 

> But unfortunately, now our documentation only support using docker to 
> install. The link is as bellow:

> https://wiki.opnfv.org/display/yardstick/How+to+deploy+InfluxDB+and+Grafana+locally

>  

> Maybe you can use the documentation of influxDB and Grafana to install them.

> And then config yardstick  as the documentation in the link.

>  

> That would be great if you plan to submit a patch to yardstick.
A patch about what? 

> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 

> If you need any help, please do not hesitate to contact me.

>  

> Regards,

> Jack Chan

>  

>  

> > 
> > 
> 发件人> :> > >  Marco Varlese [mailto:marco.varl...@suse.com]


> 发送时间> :>  2017> > > 年> 3月> 14日> >  19:20

> 收件人> :> >  chenjiankun; Tallgren, Tapio;
opnfv-tech-discuss@lists.opnfv.org

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



>  

> > 
> On Tue, 2017-03-14 at 10:46 +, chenjiankun wrote:


> > > > > > > > > > > > > > > 
>  

> Hi,

>  

> See the comment.

>  

> Regards,

> Jack Chan

> > 
> > 
> From:> > > > > > > >  Marco Varlese [mailto:marco.varl...@suse.com]


Sent: Tuesday, March 14, 2017 5:14 PM

To: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org

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



>  

> > 
> On Tue, 2017-03-14 at 09:08 +, chenjiankun wrote:


> > > > > 
> Hi Marco,

>  

> We made some change in Danube(including split requirements.txt from setup.py 
> and using pip to install), I will upgrade the documentation soon.

> Now you can use pip to install(pip install -r requirements.txt and pip 
> install .).


> > 
> Ok, but as far as I can tell, there are missing entries in the 
> requirements.txt file which I had to manually install later (pip install ...) 
> when yardstick was failing to launch and the .py script


> > 
> was notifying me of missing modules... so I would say that there's still 
> something missing beside splitting things in different files?


> > 
> Do you mean there are some dependencies not including in the 
> requirements.txt? Can you tell me what they are?



> > 
>  


> > 
> Will do. I have to collect everything I've done over the past week. Will keep 
> you posted.


> > 
>  


> > 
> BTW, something appears to be broken with yardstick-plot too...


> > 
> I'm passing to the script the output file generated by Yardstick and it 
> breaks.


> > 
> I tried multiple test-cases and all of them can't be parsed by 
> yardstick-plot, generating always the same error message.


> > 
>  


> > 
> > (yardstick_venv) 
stack@wingenfelder:~/yardstick> yardstick-plot -i /tmp/yardstick.out -o 
/tmp/yardstick/


> > 
> Parsing input file


> > 
> Traceback (most recent call last):


> > 
>   File "/home/stack/yardstick_venv/bin/yardstick-plot", line 11, in 


> > 
> load_entry_point('yardstick==0.1.dev0', 'console_scripts', 
> 'yardstick-plot')()


> > 
>   File 
> "/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
>  line 315, in main


> > 
> parser.parse_input_file()


> > 
>   File 
> "/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
>  line 97, in parse_input_file


> > 
> self._add_record(record)


> > 
>   File 
> "/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
>  line 73, in _add_record


> > 
> runner_object = self.scenarios[record["runner_id"]]


> > 
> KeyError: 'runner_id'


> > 
>  


> > > > > > > > > > > > > > > > 
> > > 
>  

> Actually you can run ./install.sh in yardstick root path.


> > > > 
>  

>  

> As for creating a guest-image, you need not to add ssh-key-pair to the image. 
> Yardstick will inject the key when creating the instance automatically.


> > > 
> I suppose you use cloud-init in the VM image for accomplishing this, correct?

> We use heat to add the key. There is an option for it.


> > 
>  


> > > 
>  

> We generate the key dynamically for security reason. If you want to login the 
> instance, you can use yardstick generated key to login.


> > > > 
> The key gets deleted once the tests finish and - as you know - a new one is 
> created at the next iteration...

> You can use --keep-deploy option, it do not delete the vm. For example,

> yardstick -d task start sample/ping.yaml --keep-deploy


> > 
>  


> > > 
>  

> The key file path is 
> /usr/local/lib/python2.7/dist-packages/yardstick/resources/

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

2017-03-16 Thread chenjiankun 
Hi,

for the yardstick-plot, now it is deprecated now.
If you want to parse data to the GUI, you can use the InfluxDB and Grafana.
But unfortunately, now our documentation only support using docker to install. 
The link is as bellow:
https://wiki.opnfv.org/display/yardstick/How+to+deploy+InfluxDB+and+Grafana+locally

Maybe you can use the documentation of influxDB and Grafana to install them.
And then config yardstick  as the documentation in the link.

That would be great if you plan to submit a patch to yardstick.
If you need any help, please do not hesitate to contact me.

Regards,
Jack Chan


发件人: Marco Varlese [mailto:marco.varl...@suse.com]
发送时间: 2017年3月14日 19:20
收件人: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org
主题: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

On Tue, 2017-03-14 at 10:46 +, chenjiankun wrote:

Hi,

See the comment.

Regards,
Jack Chan
From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Tuesday, March 14, 2017 5:14 PM
To: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

On Tue, 2017-03-14 at 09:08 +, chenjiankun wrote:
Hi Marco,

We made some change in Danube(including split requirements.txt from setup.py 
and using pip to install), I will upgrade the documentation soon.
Now you can use pip to install(pip install -r requirements.txt and pip install 
.).
Ok, but as far as I can tell, there are missing entries in the requirements.txt 
file which I had to manually install later (pip install ...) when yardstick was 
failing to launch and the .py script
was notifying me of missing modules... so I would say that there's still 
something missing beside splitting things in different files?
Do you mean there are some dependencies not including in the requirements.txt? 
Can you tell me what they are?

Will do. I have to collect everything I've done over the past week. Will keep 
you posted.

BTW, something appears to be broken with yardstick-plot too...
I'm passing to the script the output file generated by Yardstick and it breaks.
I tried multiple test-cases and all of them can't be parsed by yardstick-plot, 
generating always the same error message.

(yardstick_venv) stack@wingenfelder:~/yardstick> 
yardstick-plot -i /tmp/yardstick.out -o /tmp/yardstick/
Parsing input file
Traceback (most recent call last):
  File "/home/stack/yardstick_venv/bin/yardstick-plot", line 11, in 
load_entry_point('yardstick==0.1.dev0', 'console_scripts', 
'yardstick-plot')()
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 315, in main
parser.parse_input_file()
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 97, in parse_input_file
self._add_record(record)
  File 
"/home/stack/yardstick_venv/lib/python2.7/site-packages/yardstick-0.1.dev0-py2.7.egg/yardstick/plot/plotter.py",
 line 73, in _add_record
runner_object = self.scenarios[record["runner_id"]]
KeyError: 'runner_id'


Actually you can run ./install.sh in yardstick root path.


As for creating a guest-image, you need not to add ssh-key-pair to the image. 
Yardstick will inject the key when creating the instance automatically.
I suppose you use cloud-init in the VM image for accomplishing this, correct?
We use heat to add the key. There is an option for it.


We generate the key dynamically for security reason. If you want to login the 
instance, you can use yardstick generated key to login.
The key gets deleted once the tests finish and - as you know - a new one is 
created at the next iteration...
You can use --keep-deploy option, it do not delete the vm. For example,
yardstick -d task start sample/ping.yaml --keep-deploy


The key file path is 
/usr/local/lib/python2.7/dist-packages/yardstick/resources/files/.
Sure, I know about this path but as mentioned above, the keys are deleted once 
the tests finish...



Regards,
Jack Chan
Cheers,
Marco



From: Marco Varlese [mailto:marco.varl...@suse.com]
Sent: Monday, March 13, 2017 7:34 PM
To: chenjiankun; Tallgren, Tapio; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [yardstick] Yardstick run-time issue

Hi,

I solved all the issues, etc.
I spotted some descrepancies in documentation and/or points opened to 
interpretation. I plan to submit a patch soon to address those.
Also, on my environment, lots of python dependencies were not installed 
"automatically" by the yardstick script and I had to proceed
by manually install them via "pip install ..."

Having said all this, if I want to create a guest-image myself... do you have 
any documentation or can you suggest me how to make the
guest image "working" with the ssh-key-pair w