[ICN-379] ECMO V2 Integration in ICN R3 Release version Created: 08/Jun/20  Updated: 24/Jul/20  Resolved: 16/Jun/20

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

Type: Story Priority: Medium
Reporter: Igor Duarte Cardoso Assignee: Igor Duarte Cardoso
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: KuD R3 Release works
Sprint: ICN Sprint 19
Story Points: 4

 Description   

Make sure the following items are checked for ECMO V2 release.

  • EMCO (ONAP4K8s) Micro-services are available in a common place (such as dockerHub).
  • Helm charts of EMCO are checked with ICN R3 release.
  • EMCO installation document is easy to use for ICN R3.

Enable all the end2end testing for ECMO V2 release.

  • Current hybrid virtual/container (vFW) example continue to work.
  • Application examples (cFW & Analytics) onboarding/deployment across multiple clusters are tried and working.
  • Making current ICN EdgeXFoundry use case working on EMCO v2.

 

 Comments   
Comment by Igor Duarte Cardoso [ 16/Jun/20 ]

Everything seems to run fine after minor change to the latest emco v2 patch. Feedback has been provided at https://gerrit.onap.org/r/c/multicloud/k8s/+/107159.

 

Instructions/steps for deploying and teting the multi-cluster are here: https://gitlab.devtools.intel.com/iduartec/steps/-/blob/master/emco/v2test/steps.sh

Comment by Igor Duarte Cardoso [ 11/Jun/20 ]

Latest onap4k8s image uploaded to dockerhub seems to be 0.6.0. As of May 7th: https://hub.docker.com/r/onap/multicloud-k8s.

Comment by Igor Duarte Cardoso [ 11/Jun/20 ]

Issue in documentation: https://github.com/onap/multicloud-k8s/blob/master/kud/hosting_providers/containerized/README.md;

sudo setup will create a ~/.vagrant.d owned by root which subsequently makes "vagrant up" fail:

$ vagrant up
Vagrant failed to initialize at a very early stage:

The home directory you specified is not accessible. The home
directory that Vagrant uses must be both readable and writable.

 ...

But changing owner doesn't help as vagrant up requires root permissions so:

sudo vagrant up

 

Fixes the problem for now.

Comment by Igor Duarte Cardoso [ 08/Jun/20 ]

Assigning epic ICN-217, please reassign if there's a better epic.

Comment by Kuralamudhan Ramakrishnan [ 08/Jun/20 ]

Patches to be tested.

https://gerrit.onap.org/r/c/multicloud/k8s/+/107164

https://gerrit.onap.org/r/c/multicloud/k8s/+/107159

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