TSC 2018-11-27

06:08:43 From Srini Addepalli (Intel) : HPA feature is not an issue. vCPE-with-TOSCA use case is working fine with HPA.But vFW use case with HPA is still in progress.

06:09:07 From Catherine Lefevre : thanks for the clarifications

06:09:36 From Srini Addepalli (Intel) : @Catherine, in regards to release notes, who should I talk to?

06:10:06 From Lingli Deng : Please also make sure that HPA is not a use case but a functional requirement. Otherwise, it is still very confusing.

06:11:11 From Srini Addepalli (Intel) : @Lingli, good point. HPA is a functional requirement.

06:11:27 From Catherine Lefevre : @srini, please talk to sofia wallin, documentation PTL

06:11:37 From Kenny Paul (LFN) : #info Andreas online

06:12:00 From Srini Addepalli (Intel) : @Giidas, it would be good if you could change your terminogloy from HPA(vFW) to vFW-with-HPA.

06:12:07 From Kenny Paul (LFN) : #info Eric online

06:12:54 From Gildas Lanilis : Got it @Srini.

06:12:55 From Kenny Paul (LFN) : Helen reports Tlab still unstable

06:13:22 From Kenny Paul (LFN) : 2 groups moved to windriver

06:13:42 From Gildas Lanilis : @Srini and @Lingli: I chnage to HPA (vFW-with-HPA) Functional Requirement and CCVPN Use Case have not completed their testing

06:16:12 From Kenny Paul (LFN) : vCPE w/ TOSCA being moved to release env for retest.

06:17:08 From Lingli Deng : @Gildas @ Srini Perhaps it is more clear to say that "HPA feature with HEAT VNF" is not completed as part of vFW (HEAT) use case, while "HPA feature with TOSCA VNF" is verified as part of the vCPE (TOSCA) use case.

06:17:56 From Kenny Paul (LFN) : 5G OOF-PCI release env retest pending

06:24:22 From Kenny Paul (LFN) : vFW HPA - Srini- believe it is a config issue. If not addressed today will be in maintenance rel.

06:26:31 From Kenny Paul (LFN) : Alex- HPA VNF on HEAT was always a stretch goal. TOSCA was the primary target.

06:27:08 From Lingli Deng : @Alex, in your statement, HPA as a functional requirement has failed at least partially.

06:28:01 From Kenny Paul (LFN) : Alex - Lessons learned for Dublin need to review what it means when a PTL commits to a requirement

06:28:32 From Lingli Deng : @Alex @Helen @Srini It would help that we understand the expectation and scope for HPA requirement.

06:28:32 From Kenny Paul (LFN) : HPA hardening targeted for Dublin.

06:29:17 From Helen Chen : https://wiki.onap.org/display/DW/vFW+with+HPA+Integration+Test+-+Test+Status

06:32:35 From Kenny Paul (LFN) : CM Flex Designer & Orch. - testing on release still required.

06:34:55 From Alexander Vul : @Lingli - the objective of HPA FR was to enable TOSCA based VNFs across all ONAP orchestration paths.

06:35:07 From Kenny Paul (LFN) : CM Traffic Mgmt- testing on SB04 w/ OOM having problems - Helen recommends moving to SB07

06:36:48 From Kenny Paul (LFN) : CM - 5G PNF - Yang-Xu- duplicate entry. to be removed by Helen

06:37:33 From Alexander Vul : @Lingli - HPA was as advertised with VF-C, but we have no working TOSCA orchestration path in SO, so for now have enabled manual specification of HPA policies for HEAT based VNFs. Once we figure how to orchestrate VNFs in SO using TOSCA, we can call the whole thing done…

06:37:35 From Kenny Paul (LFN) : CM Sched opt. - retest on release pending.

06:38:04 From Lingli Deng : @Alex I am not sure I understand what do you mean by all orchestration paths.

06:38:07 From Kenny Paul (LFN) : Stability E2E test @ 85%

06:39:11 From Lingli Deng : @Alex Seems like a moving target to me.

06:39:34 From Kenny Paul (LFN) : https://wiki.onap.org/display/DW/Casablanca+Release+Resiliency+Testing+Status

06:40:50 From Alexander Vul : @Lingli - it should not be a moving target, if we can all agree on a normative specification of VNFDs in ONAP

06:41:02 From Alexander Vul : @Lingli - there two ways to instantiate a VNF in ONAP - using VF-C and using SO. These are the two orchestration paths that I refer to.

06:43:43 From Kenny Paul (LFN) : CCVPN - Yan - 85% - 3 blockers ; Service Dist, Client Integration and Link Mgmt.

06:43:46 From Lingli Deng : @Alex Thanks for the clarification. In this case, what we did with vCPE (TOSCA) does not cover SO.

06:44:22 From Kenny Paul (LFN) : blockers sdc-1955, sdc-1958, aai-1923

06:44:51 From Kenny Paul (LFN) : Seshu - workaround for site services

06:45:00 From Gildas Lanilis : @Kenny: theses blockers sdc-1955, sdc-1958, aai-1923

are scheuled for Csablanca Maitenance Release.

06:45:05 From Michael Lando : the sdc issues are not blocking the casablanc release

06:45:18 From Michael Lando : as there was no commitment

06:45:45 From Kenny Paul (LFN) : SDC -best effort only

06:46:00 From Michael Lando : thank you

06:46:06 From Lingli Deng : The problem is that the two modules committed to CCVPN actually dependent on SDC parser.

06:46:16 From Lingli Deng : which are SO and UUI.

06:46:47 From Michael Lando : the two defact that are reported on sdc are the same issue parsing is failing on the model.

06:46:52 From Lingli Deng : Leasons learned for PTLs to commit to a requirement in the future: make sure that any other project which you depend on is also committed to the specific usecase.

06:47:36 From Lingli Deng : Or you have to think about decouple the basic functionality on another uncommitted module.

06:47:43 From Lingli Deng : @Tao @Seshu

06:48:27 From Catherine Lefevre : #action - SDC generic parser

06:48:39 From Lingli Deng : I would be happy to volunteer

06:48:48 From Lingli Deng : @Catherine

06:49:52 From Catherine Lefevre : thanks Lingli

06:50:17 From Lingli Deng : My pleasure@Catherine

06:50:37 From Alexander Vul : From the TOSCA Task Force perspective, we have identified a few new SDC requirements for Dublin…

06:51:09 From Catherine Lefevre : thanks Alex

06:51:10 From Alexander Vul : @Lingli, @Catherine - how do we make sure these new requirements get priority with the SDC team…

06:51:13 From Jimmy Forsyth (AT&T) : AAI-1923 is set as Medium in Jira w/ Casablanca Maintenance Release as the target fixVersion. If it is a blocker that needs to be included in Casablanca this needs to be communicated to the AAI team.

06:51:33 From Catherine Lefevre : does SDc already aware of TOSCA task force inputs?

06:51:45 From Michael Lando : we are not

06:52:17 From Alexander Vul : @Lando - Anatoly and you are part of the team…

06:52:25 From Gildas Lanilis : @Jimmy AAI-1923 is not a blocker for current Casablanca Release. AAI-1923 is for Miantenance release.

06:52:56 From Alexander Vul : @Lando - we meet on regular basis, but some members don’t attend :-)

06:53:35 From Jimmy Forsyth (AT&T) : @Gildas - ok, great, thanks :)

06:53:53 From Kenny Paul (LFN) : #topic vulnerability

06:53:54 From Michael Lando : @Alex ok you are corect on this point. i will ask antly to join as i have been ocupied with the sdc work

06:54:11 From Michael O'Brien (LOG, Amdocs) : log response

06:54:12 From Michael O'Brien (LOG, Amdocs) : https://lists.onap.org/g/onap-discuss/topic/update_s3p_for_tsc/28276517?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28276517

06:54:41 From Alexander Vul : @Lando - we need someone who can speak and commit on your behalf. I know you are crazy busy with other things.

06:55:10 From Kenny Paul (LFN) : Amy- need feedback on AAI, Logging, MSB, SDC &

06:55:13 From Kenny Paul (LFN) : ?

06:55:20 From Gildas Lanilis : Amy, Steve, Pawel: Need to follow with LOg, MSB, AAI, SDC and SDNC project

06:55:41 From Michael Lando : @alex i was working on unblocking the issue HPA found i belive we will have more time soon.

06:56:17 From Michael O'Brien (LOG, Amdocs) : SDNC-context-builder is in master for dublin only - in response to logging S3P https://lists.onap.org/g/onap-discuss/topic/update_s3p_for_tsc/28276517?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,28276517

06:57:05 From Kenny Paul (LFN) : Documentation for all due by Thursday

06:57:35 From Jimmy Forsyth (AT&T) : AAI needs response on request for feedback on ESR issues from ESR sub-project team, Lv Bo or Huabing have been handling similar requests. All other issues in AAI have been addressed.

06:59:26 From Kenny Paul (LFN) : Amy - for things that cannot be fixes - must document risk and mitigation.

07:00:29 From Kenny Paul (LFN) : #action @Michael O - sent email to Catherine on resources needed for assistance

07:00:53 From Kenny Paul (LFN) : Seshu offers help

07:05:14 From Lingli Deng : Tao is online

07:05:21 From Lingli Deng : I am sorry that I could not speak up.

07:05:30 From Lingli Deng : Please call Tao out. @Kenny

07:10:01 From Catherine Lefevre : #Action - check if the change was made in UUI otherwise is it just a text to change or does it require more work

07:10:02 From Kenny Paul (LFN) : #action Tao provide the commit # fix for the issue related to licensing

07:10:17 From Catherine Lefevre : more work then we will need to re-assess this finding

07:25:30 From Kenny Paul (LFN) : prior phone bridge was killed due to conflict.
07:26:21 From Michael O'Brien : Seshu thanks, was on the arch call - where everyone else is
07:26:51 From Michael Lando : yes thank you seshu wiht out you we would not have found the bridge
07:26:53 From Sai Seshu : Most welcome buddy
07:27:21 From Kenny Paul (LFN) : #info Catherine, Ranny, Davide, Lingli, Eric, Milind,
07:28:01 From Lingli Deng : Shall we wait for more to come?
07:28:42 From Michael O'Brien : arch call
07:28:43 From Michael O'Brien : https://zoom.us/j/608270884
07:29:18 From Michael O'Brien : sorry wrong link
07:29:34 From Lingli Deng : I am OK with email vote.
07:30:35 From Kenny Paul (LFN) : #action Kenny to send email vote out immediately
07:31:40 From Michael O'Brien : sounds good
07:31:47 From Lingli Deng : Works for me. @Catherine.
07:32:38 From Helen Chen : https://zoom.us/j/4466668888
07:32:42 From Michael O'Brien : Seshu is a good buddy
07:32:57 From Lingli Deng : +1
07:33:20 From Michael O'Brien : thanks kenny - will fix my calendar