Hi Morgan,

 

I have confirmed the release version of vfc artifacts and updated the
VFC-1665 status yesterday morning (Beijing time) and I also clarified the
latest status  at the PTL meeting yesterday. Please double check. Thanks.

 

BTW, we have upgrade VFC components three times  from M4 to RC1. And almost
all issue we have fixed during vCPE integration testing, From RC1, there is
no more changes and bug fixed.

 

 

BR,

Yan

发件人: [email protected] [mailto:[email protected]] 代表 Morgan
Richomme via lists.onap.org
发送时间: 2020年6月1日 18:30
收件人: David McBride; Lefevre, Catherine; [email protected]
抄送: [email protected]; Krzysztof Opasiak; ZWARICO, AMY; 'Pawel
Pawlak'; David Perez Caparros
主题: [onap-ptl] [ONAP] [Frankfurt] Integration status for RC2

 

Hi

 

I will not be able to attend this afternoon (Public holiday in Europe).

I updated the status for the PTL meeting

 

1) Do we have all our RC2 dockers?

*************************************

the Readiness board is up to date:
https://wiki.onap.org/display/DW/Frankfurt+Readiness+dashboard

 

RC2 dockers are missing for some projects

They have been merged in Master Gate and are still in Frankfurt Gate for
OOF, SDC and AAI

They are still in Master Gate for AAF and SO 

 

I need also some clarification for SDNC and CDS 

for CDS:  there are some patches for frankfurt in CCSDK gerrit
(https://gerrit.onap.org/r/c/ccsdk/features/+/108581) but I did not find any
corresponding OOM patches yet

for SDNC: As the docker versions of the master branches are different than
the ones of the frankfurt branch, I just need to be sure that the versions
in Master are for Guilin and the ones in Frankfurt are the right ones.

Otherwise the integration in OOM is missing.

 

Finally I did not get any feedback from VFC.

I imagine that the versions are the right ones - no changes since M4..and
possibly no lots of changes from El Alto.

But I need a confirmation to close the JIRA.

 

I updated the follow up pod by pod:
https://docs.google.com/spreadsheets/d/1t3GNRtabdkVxG4ZAxqBJ-X7OO-Zv6xRwd8Kr
R52V9zU/edit?usp=sharing

 

the RC1 1/06 (=RC2 candidate) column = results of the Frankfurt Daily run
executed today:
https://gating-results.onap.eu/results/onap_daily_pod4_frankfurt-574930638-0
6-01-2020_02-06/

the RC2 target includes the versions currently in gate in Frankfurt or in
Master (announced for Frankfurt in patch), the ?? corresponds to the open
question (tracked in the JIRA)

the Master column = results of the Master Daily branch executed today:
https://gating-results.onap.eu/results/onap_daily_pod4_master-575064753-06-0
1-2020_06-06/

 

Considering the RC2 target, column

green => we have the dockers, we are ready

orange => the dockers in OOM frankfurt are not the ones we expected

 

so from a Readiness point of view it is a NOGO.

 

2) Use cases

**************

 

30 on 31 use cases had been completed in RC1.

last use case was about 75%.

Wait for RC2 dockers for regression tests (but need the RC2 dockers for
that)

 

Please also note that the 72h stability test was OK

 

3) CI

******

results are not bad (bad results on the 28th seem to be due to hardware
transient issue)

we should now be able to get a 100% on smoke tests (current results in daily
Master)

 

I summarized the CI test results in the following graphs

Note that the threshold change for smoke tests as we introduced new use
cases in CI during the RC0-RC2 period, some issues have been found on fixed
that is why the target is now 100%

 

错误!未指定文件名。

 

 

Conclusions

*************

 

NOGO

 

Action points for the PTL

- finalize the merge for the OOF, SDC, AAI

- finalize Master merge then Frankfurt merge for AAF and SO

- Clarify SDNC, CCSK, VFC

 

/Morgan

____________________________________________________________________________
_____________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu
ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
 
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and
delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#6459): https://lists.onap.org/g/onap-tsc/message/6459
Mute This Topic: https://lists.onap.org/mt/74618516/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to