From da5e1b9d20b28e6fab9a611c6b2198513d1724dc Mon Sep 17 00:00:00 2001 From: joquiltyL Date: Tue, 8 May 2018 16:56:48 +0100 Subject: Change all mentions of EPA to HPA Changed the term EPA to HPA in Chapter 4 section 4.6, and Chapter 5 section 5.1.1 and the title of section 5.1.9 Issue-ID: VNFRQTS-209 Change-Id: I72e3821eb0b63b9b60a2d1b83b85c48a63d06d90 Signed-off-by: joquiltyL --- docs/Chapter4.rst | 2 +- docs/Chapter5.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/Chapter4.rst b/docs/Chapter4.rst index c501e7f..b72afc1 100644 --- a/docs/Chapter4.rst +++ b/docs/Chapter4.rst @@ -1367,7 +1367,7 @@ Second, the VNF provider should provide the VNF Rest API to integrate with the GVNFM if needed. The VNF Rest API is aligned to the ETSI IFA document. -Third, the TOSCA model supports the EPA feature. +Third, the TOSCA model supports the HPA feature. Note: diff --git a/docs/Chapter5.rst b/docs/Chapter5.rst index decbfc7..5db3e71 100644 --- a/docs/Chapter5.rst +++ b/docs/Chapter5.rst @@ -23,7 +23,7 @@ Network Cloud. It has the following features: 2. VNF TOSCA template is aligned to the newest TOSCA protocol, “Working Draft 04-Revision 06”. -3. VNF TOSCA template supports EPA features, such as NUMA, Hyper +3. VNF TOSCA template supports HPA features, such as NUMA, Hyper Threading, SRIOV， etc. Intended Audience @@ -192,7 +192,7 @@ specification [TOSCA-Simple-Profile-NFV-v1.0] for NFV VNFD. +====================================================================+ +--------------------------------------------------------------------+ -EPA Requirements +HPA Requirements ^^^^^^^^^^^^^^^^^^ 1. SR-IOV Passthrought -- cgit 1.2.3-korg