Hi Carlos,
Thanks for your greate contribution in Doctor and had a nice tour with you in
Beijing.
Yunjun and I will go to attend the OpenStack PTG in Dublin, looking forward to
see you and have a beer. :-)
BR,
dwj
原始邮件
发件人： ;
收件人： ; ;
日 期 ：2018年01月22日 1
Hi DaveNeary,
Thanks for the reply.
I can take over the task, but I'm not familiar with TripleO.
As far as I know is that I need to do some steps in upstream:
how to deploy Vitrage in puppet-tripleo project
add heat template in tripleo-heat-template
build image include Vitrage pack
Hi Tim Rozet,
I noticed that you are the assignee for task `integrate project Vitrage in
Apex`[1].
May I ask what's the progress? Do you have a plan to implement it in F release?
Thanks~
[1]https://jira.opnfv.org/browse/APEX-213
BR,
dwj__
Hi Jose,
Thanks for the fix~ :-)
I'll check after these patches were merged.
BR,
dwj
原始邮件
发件人： ;
收件人：董文娟00101742;
抄送人： ; ;
; ;
日 期 ：2017年10月17日 22:56
主 题 ：Re: [opnfv-tech-discuss] [Doctor][Functest] about doctor verify job using
'functest-suite-builder'
Hi All,
As doctor verify job using the 'functest-suite-builder' to test, I found that
many parameters are not passed to start functest docker container.
Such as {sshkey_vol}, {TESTCASE_OPTIONS}, you can see the log from[1]
[1]
https://build.opnfv.org/ci/job/doctor-python-verify-apex
Hi doctors,
FYI:
ZTE-virtual3(Apex) Pod was already upgraded to master branch(using
opnfv-2017-07-29.iso).
ZTE-virtual4(MCP) Pod was deployed successfully now. But I don't know how to
use yet.
BR,
dwj___
opnfv-tech-discuss mailing list
opnf
Hi all,
Currently, there are some issues about the python verify jobs as we run the
tests in Functest docker container.
Don't setup the tox in container.
This can be solved if we install tox in doctor test script
only support python 2.7.6 in functest docker container.
The container O
Hi doctors,
The doctor verify jobs were failed in Apex and Fuel Pods, the reason is that:
As we called functest builder 'functest-suite-builder':
1) For Fuel Pod
It uses salt_master_ip(192.168.10.100) as installer_ip in 'master'
branch[1].
So we need to upgrade the version.
2)
Thanks~
原始邮件
发件人：
收件人：董文娟00101742
抄送人：
日 期 ：2017年06月26日 19:11
主 题 ：RE: [opnfv-tech-discuss] [doctor] zte-virtual3(apex)zte-virtual4(fuel)
Wenjuan,
Please go ahead!
Thanks,
Ryota
From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn]
Hi,
As I mentioned in the previous email, I would like to tag zte pod and ool pod
with the same label.
What do you think? Let me know if you have some ideas.
Thanks~
BR,
dwj
原始邮件
发件人：董文娟00101742
收件人：
日 期 ：2017年06月22日 17:41
主 题 ：[opnfv-tech-discuss] [doctor] zte-
Hi All,
I deployed zte-virtual3 with apex Danube2.0 and zte-virtual4 with fuel
Danube2.0.
Now these two pods are online[1].
I also updated the pods info in the etherpad[2]
How about tagging ool-virtual1 and zte-virtual3 with the same label:
doctor-apex-verify,
and ool-virtual2 and zte-vi
11 matches
Mail list logo
