NFV FAQ - Revision history

Vreck at 09:00, 8 April 2020

2020-04-08T09:00:43Z

← Older revision		Revision as of 10:00, 8 April 2020
Line 162:		Line 162:

	----		----
	'' Acknowledgement: The Q&A (No.1-18) were originally contributed by STC(Saudi Telecom Company). ''		'' Acknowledgement: The Q&A (No.5-22) were originally contributed by STC (Saudi Telecom Company). ''
	----		----
	''' Link '''		''' Link '''

Vreck: (UPDATED and ADDED several questions, implementing the work done by Bruno Chatras upon request from the NFV Strategic group.)

2020-04-08T07:57:25Z

(UPDATED and ADDED several questions, implementing the work done by Bruno Chatras upon request from the NFV Strategic group.)

Show changes

Vreck: Reverted edits by Vreck (talk) to last revision by Nakamurate

2020-04-08T07:55:51Z

Reverted edits by Vreck (talk) to last revision by Nakamurate

Show changes

Vreck: UPDATED and ADDED several question, implementing the work done by Bruno Chatras upon request from the NFV Stretegic group.

2020-04-08T07:54:24Z

UPDATED and ADDED several question, implementing the work done by Bruno Chatras upon request from the NFV Stretegic group.

Show changes

Nakamurate at 18:17, 20 December 2017

2017-12-20T18:17:40Z

Show changes

Nakamurate at 16:40, 19 December 2017

2017-12-19T16:40:11Z

← Older revision		Revision as of 17:40, 19 December 2017
Line 175:		Line 175:


			----
			'' Acknowledgement: The Q&A (No.1-18) were originally contributed by STC(Saudi Telecom Company). ''
	----		----
	''' Link '''		''' Link '''

Nakamurate at 03:03, 19 December 2017

2017-12-19T03:03:08Z

← Older revision		Revision as of 04:03, 19 December 2017
Line 173:		Line 173:

	The two terms cover the same concept, which is the ability to limit disruption and return to normal or at a minimum acceptable service delivery level in the face of a fault, failure, or an event that disrupts the normal operation.		The two terms cover the same concept, which is the ability to limit disruption and return to normal or at a minimum acceptable service delivery level in the face of a fault, failure, or an event that disrupts the normal operation.


			----
			''' Link '''

			[https://nfvwiki.etsi.org/index.php?title=NFVSolutions Go to NFV Solutions page]

			[https://nfvwiki.etsi.org/index.php?title=Main_Page Go to NFV wiki main page]

			[http://www.etsi.org/technologies-clusters/technologies/nfv Go to ETSI ISG NFV page]

Nakamurate at 02:24, 19 December 2017

2017-12-19T02:24:38Z

← Older revision		Revision as of 03:24, 19 December 2017
Line 115:		Line 115:

	One of the differences is the VNF Configuration interface which is available only on the Ve-Vnfm-vnf. The VNF Configuration interface on the Ve-Vnfm-vnf reference point supports setting or updating virtualization-related configuration parameters for a VNF/VNFC instance.		One of the differences is the VNF Configuration interface which is available only on the Ve-Vnfm-vnf. The VNF Configuration interface on the Ve-Vnfm-vnf reference point supports setting or updating virtualization-related configuration parameters for a VNF/VNFC instance.


	== Can we have independent and multi-vendor VIM, VNF Manager and NFV Orchestrator in a real deployment? ==		== Can we have independent and multi-vendor VIM, VNF Manager and NFV Orchestrator in a real deployment? ==

Nakamurate: /* In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? */

2017-12-19T02:23:10Z

In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality?

← Older revision		Revision as of 03:23, 19 December 2017
Line 110:		Line 110:
	== In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? ==		== In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? ==

	[[File:NFV-framework.png]]		[[File:NFV-framework.png \| 500px]]

	The Ve-Vnfm-em reference point is used for exchanges between EM and VNF Manager. The Ve-Vnfm-vnf reference point is used for exchanges between VNF and VNF Manager. They share some common functionalities, for example, the VNF Indicator interface which is the information supplied by the VNF or the EM to provide some indication of the VNF behavior. VNFM can use these indicators in conjunction with virtualized resource data to perform auto-scaling decisions. Also, both reference points share most of the operations of the VNF Lifecycle Management interface produced by the VNFM and consumed by the EM and/or VNF.		The Ve-Vnfm-em reference point is used for exchanges between EM and VNF Manager. The Ve-Vnfm-vnf reference point is used for exchanges between VNF and VNF Manager. They share some common functionalities, for example, the VNF Indicator interface which is the information supplied by the VNF or the EM to provide some indication of the VNF behavior. VNFM can use these indicators in conjunction with virtualized resource data to perform auto-scaling decisions. Also, both reference points share most of the operations of the VNF Lifecycle Management interface produced by the VNFM and consumed by the EM and/or VNF.

Nakamurate: /* In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? */

2017-12-19T02:19:21Z

In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality?

← Older revision		Revision as of 03:19, 19 December 2017
Line 109:		Line 109:

	== In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? ==		== In the standard, there are two reference points, one between VNFM and VNF, and another one between VNFM and the EM for VNF. Are both reference points carrying the same type of functionality? ==

			[[File:NFV-framework.png]]

	The Ve-Vnfm-em reference point is used for exchanges between EM and VNF Manager. The Ve-Vnfm-vnf reference point is used for exchanges between VNF and VNF Manager. They share some common functionalities, for example, the VNF Indicator interface which is the information supplied by the VNF or the EM to provide some indication of the VNF behavior. VNFM can use these indicators in conjunction with virtualized resource data to perform auto-scaling decisions. Also, both reference points share most of the operations of the VNF Lifecycle Management interface produced by the VNFM and consumed by the EM and/or VNF.		The Ve-Vnfm-em reference point is used for exchanges between EM and VNF Manager. The Ve-Vnfm-vnf reference point is used for exchanges between VNF and VNF Manager. They share some common functionalities, for example, the VNF Indicator interface which is the information supplied by the VNF or the EM to provide some indication of the VNF behavior. VNFM can use these indicators in conjunction with virtualized resource data to perform auto-scaling decisions. Also, both reference points share most of the operations of the VNF Lifecycle Management interface produced by the VNFM and consumed by the EM and/or VNF.

	One of the differences is the VNF Configuration interface which is available only on the Ve-Vnfm-vnf. The VNF Configuration interface on the Ve-Vnfm-vnf reference point supports setting or updating virtualization-related configuration parameters for a VNF/VNFC instance.		One of the differences is the VNF Configuration interface which is available only on the Ve-Vnfm-vnf. The VNF Configuration interface on the Ve-Vnfm-vnf reference point supports setting or updating virtualization-related configuration parameters for a VNF/VNFC instance.


	== Can we have independent and multi-vendor VIM, VNF Manager and NFV Orchestrator in a real deployment? ==		== Can we have independent and multi-vendor VIM, VNF Manager and NFV Orchestrator in a real deployment? ==