-
Current profiles defined in RM are using 1:2 CPU to memory ratio, while there are workloads which are more memory intensive.
Let's figure out in this issue if we would like to introduce a new profile…
-
In the discussions or #383 there was no consensus about the place of Kubernetes in the ETSI NFV MANO stack. The resolution of this issue shall build a consensus on the functional areas Kubernetes cove…
-
Section 9.1
"According to the scope laid out in chapter 1, this chapter will include **any requirements** of the infrastructure (NFVI) and the infrastructure management (VIM) capabilities."
(Emphasi…
-
Work on Security chapter Clean up & re-arrangement
-
Hi,
I have investigated in mininet and docker containers integration for a **more widely-use emulation**, such as fog computing as my research issue. I prepare a proposal for asking whether container…
tz70s updated
3 years ago
-
Need to add more operation & LCM Requirements
-
Do we need Approach document at all? It is not keeping up to date and creating confusion.
-
Can some of the similar requirements defined in RM Ch04 and Ch05 be made consistent. For example, "i.nfvi.sla.cap.001 CPU overbooking" and "nfvi.com.cfg.001 CPU allocation ration"?
-
In the discussions of #383 there was a disagreement on two topics in the area of Kubernetes cluster management:
- Is CaaS Manager part of NFVO and if we care about the result in RA2
- Scope of on…
-
@petar.torre@intel.com suggested the following text for 1.3
All NFVI APIs must ensure Interoperability (multi-vendor, components substitution), drive Simplification, and come from Open Communities …