...

1. The build .yaml file and the associated build .env file are used to invoke the VM which will build the image. The build .yaml will invoke the build script “v_gmux_build.sh”.
1. This will build vpp and honeycomb code, it may take 30-40 minutes
2. Log into the VM as the 'ubuntu' user and check that build script has finished executing.
1. cat /opt/script_status.txt
2. If the script has executed completely and successfully, the output will be “Execution of vG-MUX build script completed”.
3. If the script has failed to execute successfully, the output will should specify the reason for its failure. For more information, query the contents of the systemd journal using the ‘journalctl’ command. See also: Debugging and troubleshooting.
3. Clean up some files not required for the final image (this will save several gigabytes):

1. sudo

   su

   -

2. rm

   -fr

   /opt/vpp

   /opt/hc2vpp

   /opt/demo

   /opt/script_status.txt

4. Save an image of the VNF.

1. openstack

   server

   image

   create

   --name

   vgmux-base-ubuntu-16-04

   <VM

   Name

   or

   ID>

2. "vgmux-base-ubuntu-16-04" will be the name of the new vG-MUX image

Instantiate a VNF based on the pre-built Image

1. Change the base .env file to use the VNF image created using the process described above.

   1. For example - replace "ubuntu-16-04-cloud-amd64" with "vgmux-base-ubuntu-16-04" in "base_vcpe_vgmux.env".

2. Ensure the base .yaml file does not have the install script commented out.
   1. For example, ensure "v_gmux_install.sh" is not commented out in "base_vcpe_vgmux.yaml".
3. Create a 'stack'

   1. openstack

      stack

      create

      -t

      base_vcpe_vgmux.yaml

      -e

      base_vcpe_vgmux.env

      vGMUX

   2. Note, remove the "vGMUX" stack that was created during the "Building a VNF Image" stage.
   3. Using the image created above, the install script will perform some configuration steps and complete much more quickly since the VPP and Honeycomb code has already been compiled.

...

Prebuilt images in the ONAP-vCPE Project (as of 08/15/18):

Compatibility with Amsterdam and Beijing Releases

...

• To see the full output of the build script:

  Info
  journalctl

  
  Image Modified
  
  

• To check that the build script is running:

  Info
  ps aux | grep v_xxx_build.sh

• To check that vpp and honeycomb are running:

  Info
  systemctl status vpp.service systemctl status honeycomb.service

Note that the vpp service should be ‘inactive’ after the completion of the build script, and it should be ‘running’ on all machines after the completion of the install script.

...

This can also be confirmed by running ‘cat /var/log/honeycomb.log’:

• To check status on vGW of dhcp server:

  Info

  systemctl status

  service isc-dhcp-server status

• To check whether a package is installed using dpkg:

  Info
  dpkg -s [package name]

• For example: dpkg -s vpp

...

VNF Specific Usage Information

...

vppctl ip route add 10.3.0.0/24 via 10.1.0.10 GigabitEthernet0/4/0

·         To check whether a package is installed using dpkg:

o   dpkg -s [package name]

...