GithubHelp home page GithubHelp logo

vBNG setup on OpenStack manually about onap-demo HOT 1 CLOSED

cncf avatar cncf commented on June 9, 2024
vBNG setup on OpenStack manually

from onap-demo.

Comments (1)

lixuna avatar lixuna commented on June 9, 2024

Building a pre-built VNF Image

(Originally source)

Using the vBNG as an example, the following steps are used to create a vBNG image which can then be used as the image for instantiating a v vBNG.

  1. Manually configure the .yaml file to not run the install script
  1. Create a 'stack' - using an appropriately populated .env file
  1. Log into the VM as the 'ubuntu' user and switch to the 'root' user
  • sudo su -
  • cd /opt
  1. Create the file "/opt/config/compile_state.txt" with the contents of "build"

  2. From /opt, invoke the install script

  • ./v_bng_install.sh
  • This will build vpp and honeycomb code, it may take 30-40 minutes
  1. Clean up some files not required for the final image (this will save several gigabytes):
  • rm -fr /opt/vpp /opt/hc2vpp /opt/demo
  1. Edit the file "/opt/config/compile_state.txt" and change the contents of the file to "done"
  • Note: In the case of the vbrg emulator, the file /opt/config/compile_state.txt is created by
    the base_vcpe_vbrg.yaml file. The compile state (done, auto or build) can be passed into
    the vbrg env file before the VNF is created.
  • Compile state / description
    • Done / Use a prebuilt image. Install script sets up the environment
    • Auto / Install script builds honeycomb and vpp and sets up the environment
    • Build / Install script builds honeycomb and vpp
  1. Reboot

  2. Save an image of the VNF

  • openstack server image create --name vbng-base-ubuntu-16-04
  • "vgmux-base-ubuntu-16-04" will be the name of the new vBNG image

Instantiate a VNF based on the pre-built Image

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

    • For example - replace "ubuntu-16-04-cloud-amd64" with "vbng-base-ubuntu-16-04" in "vcpe_vbng.env"
  • Ensure the .yaml file does not have the install script commented out

    • For example, ensure "v_bng_install.sh" is not commented out in "base_vcpe_vbng.yaml"
  • Create a 'stack'

    • openstack stack create -t base_vcpe_vbng.yaml -e base_vcpe_vbng.env vBNG
    • Note, remove the "vBNG" stack that was created during the "Building a VNF Image" stage
    • 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.

from onap-demo.

Related Issues (7)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.