From 2a82dce62ef9e3b7502e83d930bbd5c6c4553fcf Mon Sep 17 00:00:00 2001 From: Sona Sarmadi Date: Fri, 17 May 2019 09:11:48 +0200 Subject: replace target, uCPE with uCPE device - Use unified terms to refer to uCPE device throughout all documentation - Replace "instantiation" with "Create" in instantiation.xml ch 3.1 it is actually "Create" button which deploys the VNF. Change-Id: Ia872a79f0bd57552640225b9412f5479f93edeff Signed-off-by: Sona Sarmadi --- .../doc/instantiation.xml | 14 +++++++------- .../doc/introduction.xml | 4 ++-- .../doc/vnf_onboarding.xml | 6 +++--- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml index bb0e28b..b06395d 100644 --- a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml +++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml @@ -3,10 +3,10 @@ Instantiation When a VNF is onboarded and available in the VNF catalog, it can be - instantiated (deployed) on connected uCPEs. The instantiation wizard uses + instantiated (deployed) on connected uCPE devices. The instantiation wizard uses the configurations provided when the VNF is onboarded, as a template for - instantiation. Before the instantiation, however, the uCPE needs to be - prepared: + instantiation. Before the instantiation, however, the uCPE device needs + to be prepared: @@ -16,7 +16,7 @@ Before configuring any physical NICs determine which is used for - managing the device. Altering the configuration of a NIC may cause + managing the uCPE device. Altering the configuration of a NIC may cause connectivity issues. @@ -49,7 +49,7 @@ - Target (the uCPE device to instantiate the VNF on). + VIM (the uCPE device to instantiate the VNF on). @@ -85,7 +85,7 @@ - Hit the instantiation button to deploy the VNF. + Hit the Create button to deploy the VNF. @@ -123,4 +123,4 @@ - \ No newline at end of file + diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml index cee9fcb..d216d7a 100644 --- a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml +++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml @@ -4,7 +4,7 @@ This document describes the process of onboarding a new VNF onto the Enea uCPE Manager so that it can subsequently instantiate and run the VNF on - one or more uCPEs. + one or more uCPE devices.
Prerequisites @@ -87,4 +87,4 @@ Guide, with configurations typically specific to the intended use case of the VNF.
- \ No newline at end of file + diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml index 5759f7b..f0d4e8f 100644 --- a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml +++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml @@ -3,7 +3,7 @@ VNF Onboarding The onboarding of a VNF means adding it to the Enea uCPE Manager VNF - Catalog and preparing it for instantiation (deployment on connected uCPEs). + Catalog and preparing it for instantiation (deployment on connected uCPE devices). This is accomplished using the Enea uCPE Manager Onboarding Wizard, a graphical user interface specifically designed to make VNF onboarding simple and fast. @@ -168,6 +168,6 @@ When the onboarding is complete, the VNF will appear in the VNF - Catalog and can be used for deploying services on the uCPEs. + Catalog and can be used for deploying services on the uCPE devices. - \ No newline at end of file + -- cgit v1.2.3-54-g00ecf