Thanks Eric for adding more context around the OVP testing. To further
expound on the testing, there are 3 classes of testing:
1. Compliance - is the VNF packaged to the standards that will allow it
to integrated in the defined infrastructure?
2. Verification - does the VNF behave
Hello Jim
« Ease of Deployment » is important and OOM team (with the community) is
working hard to ease the deployment.
The first OVP Program step is only to validate the VNF package/descriptor.
There is no need to deploy full ONAP for that.
VNF Vendor just need to run VVP or VNFSDK to check
Hi all,
Next week's Usecase subcommittee meeting will be cancelled due to Passover
holidays. Happy Holidays to all people celebrating it!!!
On the use cases/functional requirements preparation plan, Catherine will kick
off voting within the TSC. Only after that we will be able to communicate a
Dear Use Case/Functional and Non-Functional Owners,
I want to inform you about a decision that the TSC took during the TSC call on
4/18.
TSC agreed that, if no feedback provided to Jim by 4/22 EOD, any requirement
(use case, functional requirement, non-functional requirement), currently
Hi Shankar,
As this should be a functional approach, terms like “growing set” etc “ little
code development” should be avoided, the don’t really capture a functional
description (which should address what it does or what its purpose).
I propose:
“
Provides optimization services for the
Hi Mandar,
I propose to include the following, which is a compression of what is in the
component description for DMaaP.
"DMaaP provides data movement services that transports and processes data from
any source to any target. This includes Message transfer services and data
transfer services.
Hi Deng,
Then we could consider to put a TOSCA Parser as a common service. I don’t
think that the implementation consideration of whether it’s a mocroservice or
not influences whether its is considered a commont service (that is the tail
wagging the dog) or the common library from a
Hi Steve
Yang yan’s team is working on micro service based parser in R4 which will be
used by VFC and UUI,
so maybe it have to belong to both common library (NFV Parser from
OPNFV/Openstack) and Common services.( Micro service based)
Thanks a lot for your reminder
Best regards,
DENG Hui
Hi Deng,
Modelling is the common libraries to capture it there, could you expand on why
you feel it should be in the common services instead of the common library?
BR,
Steve
From: onap-tsc@lists.onap.org On Behalf Of denghui (L)
Sent: Thursday 18 April 2019 05:13
To: onap-tsc@lists.onap.org
