Hi
Ok let's discuss it during next meeting
we have already something in Functest so we should take care not
bringing confusion here
an earlier discussion said that VNF onboarding could be done in Functest
(as we have the vIMS and should have additional ones for Danube)
based on that, Yardstick
Hi Ryota,
I know that Munich Lab and another Lab from HUAWEI are preparing to
provide to Community.
I think you can contract Phraos guys to comfirm it.
Best Regards
Justin
在 2016/12/8 6:41, Ryota Mibu 写道:
Yujun,
Yes, but I can remove it if some can provide POD(s) for these CI jobs.
On Thu, Dec 8, 2016 at 6:41 AM Ryota Mibu wrote:
Yujun,
Yes, but I can remove it if some can provide POD(s) for these CI jobs.
Maybe I can put document how to build such pod.
That would be great. Let me see if we can request some resource from ZTE
lab for Doctor CI.
Locked to the ool-virtual1 POD:
https://git.opnfv.org/releng/tree/jjb/doctor/doctor.yml
Carlos
From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: 07 December 2016 02:07
To: Ryota Mibu; Carlos Goncalves; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [doctor] doctor
Thanks, Tim.
On Mon, Dec 5, 2016 at 3:45 PM, Tim Rozet wrote:
> Hey Aric, David,
> Here are the artifacts built for release:
> http://artifacts.opnfv.org/apex/colorado/opnfv-2016-12-05.iso
> http://artifacts.opnfv.org/apex/colorado/opnfv-apex-3.0-
> 20161205.noarch.rpm
>
+1 to disable (not remove) tests that don't work due to upstream missing
functionality. The problem is: how do we show the upstream community that it
fails and we would like to use that?
+1 to remove release criteria from all the test cases in sdnvpn, which is the
same as requiring 100%
Hello Xuan Jia,
My thinking on this is that when you are running a containerized VNF,
you will interact primarily with the COE - the infrastructure (and thus,
whether it's AWS, Azure, OpenStack, or MyLittleCloud APIs) should be
abstracted away and is not part of the application definition - the
Hi Kubi
We have had some good discussions here at Plugfest with Rex and others
regarding adding VNF test features to Yardstick. Can we add this as an agenda
topic to next meeting (13/12 (0:03 UTC)(US time slot)? I have added this to the
agenda as a *proposed* topic.
Trevor
Thanks Arthur for the help. We will reference these codes.
Regards
Yingjun
From: Arthur Berezin [mailto:art...@gigaspaces.com]
Sent: Wednesday, December 07, 2016 7:06 AM
To: Yingjun Li; John Zannos; 赵化冰10201488; Land Lu; Artur Tyloch; Narinder
Gupta; Mark Ramm-Christensen (Canonical.com)
Cc:
We used the odd vs. even hour setup when we had separate call in numbers
for individual meetings (to avoid calls being disconnected if your meeting
went long). Obviously this will no longer be an issue as we move to single
dial-ins for each account
Can we stay with the method for now so that
Hi all,
Made some comments regarding Syncing of multiple keypairs at a time
https://docs.google.com/document/d/1N6HFAFUT5BbEp1wbnYjgaKdOlyJanwkXccv-_1zsVQc/edit?disco=A4VEf0U
as off now we have implemented keypair-sync for a specified keypair or sync all
keypairs
Ashish and I thought
Hi,
Bumping this thread. My understanding is as well that we should be able to use
both meeting accounts in parallel, independent from the starting hour. Ray, can
you confirm this?
Best regards
Georg
From: opnfv-tech-discuss-boun...@lists.opnfv.org
Hello, two comments in the doc. Need to discuss this in the weekly meeting.
Best Regards
Chaoyi Huang (joehuang)
From: Goutham Pratapa [goutham.prat...@tcs.com]
Sent: 07 December 2016 14:15
To: joehuang
Cc: Ashish Singh7; Dimitri Mazmanov; Ashish singh; caizhiyuan
13 matches
Mail list logo