minor corrections to walkthrough (fef64c5f) · Commits · vnf-onboarding / VNF Onboarding Guidelines

06-walkthrough.md

+7 −7

Original line number	Diff line number	Diff line
		@@ -19,10 +19,10 @@ The following table describes the components description and associated images.

		And here the NFVI requirements (for this example, as the VNF has no strict requirements)

		\| VDU \| vCPU \| RAM (GB) \| Storage (GB) \| External volume? \| EPA Features \|
		\|:-------:\|:----:\|:--------:\|:------------:\|:----------------:\|:-----------------------------------------:\|
		\| spgwmme \| 2 \| 4 \| 10 \| N \| CPU Pinning, Huge Pages & SRIOV in S1/SGI \|
		\| hss \| 1 \| 2 \| 10 \| N \| - \|
		\| VDU \| vCPU \| RAM (GB) \| Storage (GB) \| EPA Features \|
		\|:-------:\|:----:\|:--------:\|:------------:\|:------------------------------------------\|
		\| spgwmme \| 2 \| 4 \| 10 \| CPU Pinning, Huge Pages & SRIOV in S1/SGI \|
		\| hss \| 1 \| 2 \| 10 \| - \|

		The topology of the VNF would be as follows:

		@@ -49,7 +49,7 @@ ssh_pwauth: True

		### Day-1 Requirements

		For this sample VNF, we will consider that establishing the session between the MME and HSS, and associated services, is enough to consider that the EPC is ready to provide its services. This VNF does not expose an API, so we will configure it with Linux commands through SSH.
		For this sample VNF, we will assume that establishing the session between the MME and HSS, and starting the main services, is enough to consider that the EPC is ready to start serving subscribers. This VNF does not expose an API, so we will configure it with Linux commands through SSH.

		SPGW-MME Day-1 operations include:

		@@ -136,10 +136,10 @@ cd devops/descriptor-packages/tools
		type: PARAVIRT
		external-connection-point-ref: spgwmme-sgi
		- name: eth3
		type: INTERNAL
		type: EXTERNAL
		virtual-interface:
		type: PARAVIRT
		internal-connection-point-ref: spgwmme-s6a
		external-connection-point-ref: spgwmme-s6a
		...
		```