Hi folks,
FYI - per what we also discussed on the last TSC all - the Calipso project team
decided that for release Euphrates,
Calipso will release as an independent tool.
As you know, Calipso is an operational tool for "day 2" operations of an NFV
solution stack, i.e. OPNFV scenario.
The Calips
Hi,
Meeting minutes are available on
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-pharos/2017/opnfv-pharos.2017-09-27-13.00.txt
/Fatih
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listi
Hi all,
Based on TSC request this week to bring out new ideas to propose, we propose to
address the ownership of functional test case development for EUAG specified
use cases starting F release.
The past attempts to execute Open Source Clearwater vIMS in B,D & E got
un-maintainable through re
I brought this up during the TSC call, but my original proposal was to
limit F-release to Australia/Oceania and G-release to Africa and it was
vetoed (Dave, if you recall you were one of the people who was against
this).
Anyhow, a suggestion was made in the TSC to do a re-vote on F-release name
ra
Hi Dovetailers
-For this week, we have a singular focus to review preparations and to
start beta, including 0.7.0 (beta) release, web portal, all relevant docs, and
support mechanism.
-Next week we may be impacted by China's holidays - let's see if we
need to cancel the call a
I think these ideas would be better discussed first in the testing working
group and see if there is an effective way to address them in the existing
projects. It's true that use case testing is a customer priority that has been
raised many times, and our current implementations have not been on
+1
Sounds like a good way forward. The filters make sense.
Regards
Wenjing
From: opnfv-tech-discuss-boun...@lists.opnfv.org
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Thursday, September 28, 2017 11:12 AM
To: Dave Neary
Cc: opnfv-tech-discuss@lists.opnf
Hi Alec
I think that is a good goal. Since VSPERF is stand-alone (not dependent on
OpenStack) there is no need for a Jump Server in the Pharos sense. In our CI
and sandbox environments both hardware and software traffic generators are
directly connected to the DUT. Especially for post-deploymen
I would second the point raised here.
We went through a similar thought process in Dovetail, and simplified the data
connection model between the jump server (the test node) and the pod (the
system under test). I agree that clarity here will reduce complexity for many
projects.
Regards
Wenjing
Bin
[1] https://wiki.opnfv.org/display/PROJ/Tc+Minutes+20170928
[2]
http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-09-28-13.00.html
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mail
10 matches
Mail list logo
