Nephio is a Kubernetes-based automation platform for deploying and managing highly distributed, interconnected workloads such as 5G Network Functions, and the underlying infrastructure on which those workloads depend.
The package approval time seems to be at least partly a function of the functionality in the deployed packages (certainly in the case of cluster creation) and of the time it takes for the KPT functions in the package pipeline to run in the case of PackageVariants.
For the end to end tests, we could perhaps do some operations in parallel (such as creating the regional, edge01, and edge02 clusters), but this could load the test infrastructure.
Regarding PackageVariantSets and PackageVariants, care should be taken by the developers of these packages to take care to design efficient kpt functions so that the package approval time is not too slow.
Regarding this issue, in the Porch architecture for R3, the package approval time cannot easily be improved.
The package approval time is long for packages in Porch, especially for packages with complex KPT pipelines and PackageVariantSets.
This issue should be addressed in Porch:
See also: https://github.com/nephio-project/nephio/issues/462
The package approval time seems to be at least partly a function of the functionality in the deployed packages (certainly in the case of cluster creation) and of the time it takes for the KPT functions in the package pipeline to run in the case of PackageVariants.
For the end to end tests, we could perhaps do some operations in parallel (such as creating the regional, edge01, and edge02 clusters), but this could load the test infrastructure.
Regarding PackageVariantSets and PackageVariants, care should be taken by the developers of these packages to take care to design efficient kpt functions so that the package approval time is not too slow.
Regarding this issue, in the Porch architecture for R3, the package approval time cannot easily be improved.