Skip to content

javierhersan/nfv

Repository files navigation

nfv-lab

Repository for NFV lab with OSM MANO. It contains a helm-repository, check out the index.yaml

Scenario

scenario detail

Quick testing guide

  1. Launch the machines RDSV-OSM and RDSV-K8S
  2. On both machines open a terminal, clone the repository and change to the folder nfv-lab:
cd Desktop
git clone https://github.com/educaredes/nfv-lab.git
cd nfv-lab
  1. On RDSV-K8S, start the VNX scenarios
sudo vnx -f vnx/nfv3_home_lxc_ubuntu64.xml -t
sudo vnx -f vnx/nfv3_server_lxc_ubuntu64.xml -t
  1. On RDSV-OSM, from the Desktop (graphically):
  • start Firefox to access OSM at localhost (admin/admin)
  • register a new k8s repository using id: helmchartrepo, type: "Helm Chart" and URL https://educaredes.github.io/nfv-lab (DO NOT TERMINATE WITH "/")

new-k8s-repository-details

  1. On RDSV-OSM, from the Desktop (graphically):
  • select the Package menu in OSM
  • access the package folder nfv-lab/pck
  • onboard the VNFs accessknf_vnfd.tar.gz and cpeknf_vnfd.tar.gz
  • onboard the NS renes_ns.tar.gz
  1. On RDSV-OSM, from the terminal instantiate the service renes1 and wait until it is completely instantiated:
osm ns-create --ns_name renes1 --nsd_name renes --vim_account dummy_vim
watch osm ns-list

Exit with ctrl+C

  1. On RDSV-OSM launch the additional configuration:
export OSMNS=7b2950d8-f92b-4041-9a55-8d1837ad7b0a   #OSM namespace
./osm_renes1.sh

(alternatively, follow the Alternative steps for testing)

  1. On RDSV-K8S, accesss the h11 terminal (root/xxxx) and check connectivity:
ifconfig eth1 # should have a 192.168.1.255.X/24 IP address
ping -c 5 8.8.8.8
firefox www.upm.es

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published