vFW K8s created by CDS with ability to execute LCM actions on it
Description
blocks
is blocked by
Confluence content
Activity
Former user January 4, 2021 at 8:16 AM
an we close this Jira
I can see one task open for guilin, I assume it will not be done for guilin anymore.
Lukasz Rajewski June 2, 2020 at 4:56 PM
@Former user The only remainings in here expected for Frankfurt is the finalization of tests https://lf-onap.atlassian.net/browse/INT-1457, doc change for https://lf-onap.atlassian.net/browse/INT-1457 and minor changes to doc and demo scripts as a result of the final tests with RC2 images. So normal integration tests phase. Nothing that blocks release or RC2 in general.
Former user June 2, 2020 at 4:03 PM
I think we can close for frankfurt and/or move to Guilin, the remaining open tasks seem to be tagged for Guilin
Lukasz Rajewski March 4, 2020 at 2:47 PM
All implementation related tasks are delivered for M4. The only one still pending are related to the integration phase and tests, like finalization of documentation, integration scripts, tests. https://lf-onap.atlassian.net/browse/INT-1260 is blocked by https://lf-onap.atlassian.net/browse/CCSDK-2044 . Anyway, https://lf-onap.atlassian.net/browse/INT-1260 is related with changes in demo repository and demo only scripts.
The purpose of this work is to build vFW K8S service on K8s cluster with help of CDS blueprint and GR-API.
Modification of vFW K8s helm charts to make them compatible with CDS
Preparation of CDS blueprint for vFW K8s service
Creation of K8s Profile in Mutlicloud for vFW K8s service base on the information from the CDS blueprint
Enabling GR-API for K8S services i.e. for vFW K8s service.
Modification of Mutlicloud/K8s API to execute selected actions of K8s resources like scaling of Deployment/StatefulSet
Modification in A&AI to represent resources created in K8S for vFW like vf-module, v-server, vnfc, and related network configuration in order to enable further LCM actions for such created service
Modification of vFW K8s helm charts in order to enable LCM operations with NetConf, Ansible
Modification of vFW K8s helm charts to have better modelling compatibile with vf-module and vnfc in order to let scaling operation be triggered properly by ONAP
Modifications in Multicloud/K8s and vFW K8s helm charts in order to support multiple instances of the same K8s service in the same time, especially for networks being created and K8s services
Related with https://lf-onap.atlassian.net/browse/MULTICLOUD-457
Related wiki page for Frankfurt: https://wiki.onap.org/display/DW/Integration+with+CDS