ONAP Community,
We wanted to make sure you were aware of the *Certified ONAP Professional
(COP) Beta Program*. The Linux Foundation worked with ONAP expert
volunteers to identify the core domains and the critical skills, knowledge
and competencies applicable to the Certified ONAP Professional (COP
Hello
There is a LFN Infra WG. You can find information on the LFN wiki:
https://wiki.lfnetworking.org/display/LN/Infrastructure+Working+Group+Summary+Report
Best Regards
Eric
-Message d'origine-
De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de
Kenny Paul
En
(removed helpdesk, moved TAC & TSC lists to Bcc)
Hi Tina,
There is not an LFEdge infrastructure or an LFNetworking infrastructure. The
infrastructure implementations are independent for each project and not shared.
The LF- IT team is a common organization with resources allocated based upon
t
Hi
A comment for External API text, Please replace with:
ONAP External APIs, North Bound Interface ( NBI ) module, exposes ONAP
capabilities to OSS/BSS by implementing TM Forum APIs. In the previous Release,
Casablanca, External APIs was already providing a set of serviceOrder,
serviceInventor
Hi Steve,
Originally CLAMP was in-between design time and runtime, now that the
‘DCAE-Design Studio’ is there inside SDC. CLAMP must be removed from SDC in the
diagram.
CLAMP is not and never was a sub-component of SDC, CLAMP is there to
“manage”/”orchestrate deployment”/”configuration” of the
Dear TSC, CCVPN Use Case Owners, impacted PTLs,
Please find below the proposal related to the SDC merge requests i.e. new TOSCA
parser
* https://gerrit.onap.org/r/#/c/84769/
* https://gerrit.onap.org/r/#/c/84786/
* https://gerrit.onap.org/r/#/c/84788/
As a pre-requisit
