...
- (Reminder - record the meeting)
- Any follow Follow up questions related to the ASD PoC presentation from July 14th
- Is the PoC using the service instance API? Byung-Woo Jun - not yet. Building block implemented, but no macro.Lukasz Rajewski recommends using the API for better integration with other workflows. That will enable orchestrating CNFs together with other parts of the Network Service.
- Marian Darula - There is a need to model a distributed service, which is deployed in multiple edge locations. ETSI-NSD concept is one option for that. EMCO seems to have support for a similar concept and may be an option, too.
- Byung-Woo Jun - The CNFM functionality is separated in the SO, and it may use multicloud, or call EMCO in the future. The motivation was to minimize changes on existing ONAP modules. The only difference between ASD orchestration and other orchestration flows is the interface to the "ASD repository" and "Helm Artifact Repository". CNFO does not interact with the "Image Artifact Repository", this is done directly from the K8S cluster. Parameterization is done by SO providing the overridable parameters (based on user input) to the CNFM. The CNFM uses these parameters to crate the instance level Helm chart. (Referring to slide #9 in last week's presentation ASD-PoC-Update-Plans-2022-07-14-v2.pptx
- Lukasz Rajewski - The existing orchestration macro is very close in its functionality to what was done in the ASD PoC. Recommends the ASD PoC be merged with the CNFO approach.
- Question about whether K8S API is used directly or through kubectl? currently kubectl is used.
- Lukasz Rajewski - The SO integration with EMCO was done in a different way than depicted in the ASD PoC diagram.
July 28th, 2022 at 1pm UTC
- (Reminder - record the meeting)
- Follow up questions related to the ASD PoC presentation from July 14th
- Alignment with Nephio, CNF-WG under CNCF, and other initiatives
- Action Item(s) (In Progress)
...