[ICN-298] Integrate eaa via onap4k8s Created: 06/Mar/20  Updated: 16/Jul/20  Resolved: 15/May/20

Status: Done
Project: Integrated Cloud Native NFV
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: High
Reporter: Chenjie Xu Assignee: Chenjie Xu
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: OpenNESS integration in ICN
Sprint: ICN Sprint 12, ICN Sprint 13, ICN Sprint 14, ICN Sprint 16, ICN Sprint 17, ICN Sprint 18

 Description   
  • build docker image, push image to repository
  • developing helm charts
  • creating ONAP4K8s artifacts
  • Onboarding and deploying
  • Integrate test cases for eaa

 Comments   
Comment by Chenjie Xu [ 07/Apr/20 ]

Submit another patch to build EAA image, producer image and consumer image:
https://gerrit.akraino.org/r/c/icn/+/3316

Comment by Chenjie Xu [ 01/Apr/20 ]

Patch has been submitted:
https://gerrit.onap.org/r/c/multicloud/k8s/+/104825

This patch is tracked by ONAP Multicloud story:
https://jira.onap.org/browse/MULTICLOUD-1044

Comment by Chenjie Xu [ 18/Mar/20 ]

It is need to deploy eaa as a microservice and build, deploy eaa on different machines. We have seen some potential conflicts to build and deploy eaa on different machines as below:

Will discuss this issue with Openness team on "Biweekly engineering sync between Openness – ICN"

Comment by Chenjie Xu [ 18/Mar/20 ]

Confirmed by Kural, eaa will be integrated via ONAP4K8S just like edgeX.

Generated at Sat Feb 10 05:58:48 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.