From 1cbd3cba138f22e9edf1bc1614425f8d9e4a6575 Mon Sep 17 00:00:00 2001 From: garciadeblas Date: Fri, 24 Jul 2020 16:29:47 +0200 Subject: [PATCH] Doc update for Rel EIGHT Signed-off-by: garciadeblas --- 01-quickstart.md | 10 ++-- 03-installing-osm.md | 89 +++++++++++++++-------------- 05-osm-usage.md | 4 +- 09-troubleshooting.md | 10 ++-- 10-osm-client-commands-reference.md | 2 +- 11-osm-im.md | 12 ++-- 6 files changed, 65 insertions(+), 62 deletions(-) diff --git a/01-quickstart.md b/01-quickstart.md index c781640..e540bdc 100644 --- a/01-quickstart.md +++ b/01-quickstart.md @@ -4,7 +4,7 @@ Open Source MANO (OSM) is an ETSI-hosted open source community delivering a production-quality MANO stack for NFV, capable of consuming openly published information models, available to everyone, suitable for all VNFs, operationally significant and VIM-independent. OSM is aligned to NFV ISG information models while providing first-hand feedback based on its implementation experience. -Release SEVEN brings a number of improvements over previous releases. For the full list of new features, please refer to the [Release SEVEN Documentation](index.md). For a comprehensive overview of OSM functionalities, you can also refer to the [OSM Scope and Functionality White Paper](https://osm.etsi.org/images/OSM_EUAG_White_Paper_OSM_Scope_and_Functionality.pdf) or to the release notes of previous OSM releases ([ONE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseONE-FINAL.pdf), [TWO](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseTWO-FINAL.pdf), [THREE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseTHREE-FINAL.pdf), [FOUR](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseFOUR-FINAL.pdf), [FIVE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseFIVE-FINAL.pdf)). +Release EIGHT brings a number of improvements over previous releases. For the full list of new features, please refer to the [Release EIGHT Documentation](index.md). For a comprehensive overview of OSM functionalities, you can also refer to the [OSM Scope and Functionality White Paper](https://osm.etsi.org/images/OSM_EUAG_White_Paper_OSM_Scope_and_Functionality.pdf) or to the release notes of previous OSM releases ([ONE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseONE-FINAL.pdf), [TWO](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseTWO-FINAL.pdf), [THREE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseTHREE-FINAL.pdf), [FOUR](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseFOUR-FINAL.pdf), [FIVE](https://osm.etsi.org/images/OSM-Whitepaper-TechContent-ReleaseFIVE-FINAL.pdf)). **OSM in Practice**: @@ -38,7 +38,7 @@ All you need to run OSM is a single server or VM with the following requirements Once you have prepared the host with the previous requirements, all you need to do is: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh ``` @@ -46,7 +46,7 @@ chmod +x install_osm.sh **TIP:** In order to facilitate potential trobleshooting later, it is recommended to save the full log of your installation process: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh 2>&1 | tee osm_install_log.txt ``` @@ -68,7 +68,7 @@ Example: #### Installation on a standalone Kubernetes environment -From Release SEVEN, OSM can be deployed on a single host running a Kubernetes cluster. Although the default option is to use docker swarm, you can now tell the installer to use K8s as the container framework. The installer will install the required packages to run a single-node K8s cluster and will deploy the different K8s objects on it. +OSM can be deployed on a single host running a Kubernetes cluster. Although the default option is to use docker swarm, you can now tell the installer to use K8s as the container framework. The installer will install the required packages to run a single-node K8s cluster and will deploy the different K8s objects on it. ```bash ./install_osm.sh -c k8s @@ -83,7 +83,7 @@ In addition, you can use the option `--k8s_monitor` to install an add-on to moni #### Other installation options - An additional installation option is the [Charmed Installation](03-installing-osm.md#charmed-installation) which will install OSM on Kubernetes with charms. -- You can also run OSM using a pre-built [vagrant](https://app.vagrantup.com/osm/boxes/releaseseven) image. You can find here detailed instruction on [how to install OSM in Vagrant](03-installing-osm.md#vagrant-installation) +- You can also run OSM using a pre-built [vagrant](https://app.vagrantup.com/osm/boxes/releaseeight) image. You can find here detailed instruction on [how to install OSM in Vagrant](03-installing-osm.md#vagrant-installation) - For other special installation options, please refer to the [specific chapter on installation options](03-installing-osm.md). ### Checking your installation diff --git a/03-installing-osm.md b/03-installing-osm.md index a8863a0..7ab1542 100644 --- a/03-installing-osm.md +++ b/03-installing-osm.md @@ -28,7 +28,7 @@ Hence, it is assumed that: Once you have one host available with the characteristics above, you just need to trigger the OSM installation by: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh ``` @@ -36,7 +36,7 @@ chmod +x install_osm.sh **TIP:** In order to facilitate potential troubleshooting later, it is recommended to save the full log of your installation process: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh 2>&1 | tee osm_install_log.txt ``` @@ -51,10 +51,12 @@ newgrp docker ### Installation based on Kubernetes -From Release SEVEN, OSM can be deployed on a single host running a Kubernetes cluster. Although the default option is to use docker swarm, you can now tell the installer to use K8s as the container framework. The installer will install the required packages to run a single-node K8s cluster and will deploy the different K8s objects on it. +OSM can be deployed on a single host running a Kubernetes cluster. Although the default option is to use docker swarm, you can now tell the installer to use K8s as the container framework. The installer will install the required packages to run a single-node K8s cluster and will deploy the different K8s objects on it. + +The minimum requirements to run OSM on top of Kubernetes are 2 CPUs, 6 GB RAM, 20GB disk and a single interface with Internet access. ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh -c k8s ``` @@ -122,7 +124,7 @@ Follow the instructions to install them in their respective sites: #### 2) Create the initial Vagrantfile in a predefined directory of your choice ```bash -vagrant init osm/releaseseven +vagrant init osm/releaseeight ``` - NOTE: to ensure the latest version is downloaded, destroy any previous existing OSM boxes (i.e. using `vagrant box list` and, if needed, `vagrant box remove`) @@ -131,7 +133,7 @@ vagrant init osm/releaseseven Editing the `Vagrantfile` is required if you need to customize the image for opened ports, assigned memory, etc. -For Release SEVEN, this is these are the recommended contents for the `Vagrantfile`: +For Release EIGHT, this is these are the recommended contents for the `Vagrantfile`: ```ruby Vagrant.configure("2") do |config| @@ -147,7 +149,7 @@ Vagrant.configure("2") do |config| exec "vagrant " + ARGV.join(' ') end config.disksize.size = "40GB" - config.vm.box = "osm/releaseseven" + config.vm.box = "osm/releaseeight" config.vm.network "forwarded_port", guest: 80, host: 8080 config.vm.provider "virtualbox" do |vb| vb.memory = "6144" @@ -197,14 +199,14 @@ scp -P 2222 -i /path/to/private_key someFileName.txt vagrant@127.0.0.1: To use an image downloaded manually, add the box to Vagrant and create a matching `Vagrantfile`: ```bash -vagrant box add osm/releaseseven /path/to/vagrant.box -vagrant init osm/releaseseven +vagrant box add osm/releaseeight /path/to/vagrant.box +vagrant init osm/releaseeight ``` If at any point you need to add the optional components (`elk_stack`, `vimemu`, ...) you can do so by downloading the installer from inside your VM and executing it with the `-o` option, for example: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh -o elk_stack ``` @@ -218,7 +220,7 @@ config.vm.network "forwarded_port", guest: 5601, host: 5601 #### Including VIM Emulator in a Vagrant installation of OSM ```bash -vagrant init osm/releaseseven +vagrant init osm/releaseeight vagrant up vagrant ssh # startup VIM-EMU @@ -261,7 +263,7 @@ Some cases where the Charmed installer might be more suitable: ![OSM Docker containers](assets/800px-OSM_charmed_standalone.png) ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh --charmed ``` @@ -273,7 +275,7 @@ This will install OSM on [microk8s](https://microk8s.io/) using Charms. For the installation using external components the following parameters can be added: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh --charmed --k8s ~/.kube/config --vca --lxd --lxd-cred ``` @@ -352,8 +354,8 @@ In order to install the OSM Client in your local Linux machine, you should follo ```bash # Clean the previous repos that might exist sudo sed -i "/osm-download.etsi.org/d" /etc/apt/sources.list -wget -qO - https://osm-download.etsi.org/repository/osm/debian/ReleaseSEVEN/OSM%20ETSI%20Release%20Key.gpg | sudo apt-key add - -sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseSEVEN stable devops IM osmclient" +wget -qO - https://osm-download.etsi.org/repository/osm/debian/ReleaseEIGHT/OSM%20ETSI%20Release%20Key.gpg | sudo apt-key add - +sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseEIGHT stable devops IM osmclient" sudo apt-get update sudo apt-get install -y python3-pip sudo -H python3 -m pip install -U pip @@ -380,7 +382,7 @@ For additional remote access options, see `osm --help` for more info. Due to the new architecture and dockerized components introduced in OSM since Release FOUR, OSM platform upgrade is quite easy. Upgrading to the latest minor version is as simple as running again the installer: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh ``` @@ -400,7 +402,7 @@ You can use option `-t` in the installer to specify a specific docker tag to be To install the latest daily images: ```bash -./install_osm.sh -t releaseseven-daily +./install_osm.sh -t releaseeight-daily ``` To install a previous version e.g. v6.0.3: @@ -409,16 +411,17 @@ To install a previous version e.g. v6.0.3: ./install_osm.sh -t v6.0.3 ``` -The previous commands will do the installation and deployment of the stack, but will not make it persistent after re-deployments of the stack (or reboots). In order to make it persistent, you will have to update the file `docker-compose.yaml`. Below an example to update it to use `releaseseven-daily` tag: +The previous commands will do the installation and deployment of the stack, but will not make it persistent after re-deployments of the stack (or reboots). In order to make it persistent, you will have to update the file `docker-compose.yaml`. Below an example to update it to use `releaseeight-daily` tag: ```bash -sudo sed -i "s/ro\:\${TAG\:-7}/ro\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/lcm\:\${TAG\:-7}/lcm\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/mon\:\${TAG\:-7}/mon\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/pol\:\${TAG\:-7}/pol\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/nbi\:\${TAG\:-7}/nbi\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/light-ui\:\${TAG\:-7}/light-ui\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml -sudo sed -i "s/keystone\:\${TAG\:-7}/keystone\:\${TAG\:-releaseseven-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/ro\:\${TAG\:-8}/ro\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/lcm\:\${TAG\:-8}/lcm\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/mon\:\${TAG\:-8}/mon\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/pol\:\${TAG\:-8}/pol\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/nbi\:\${TAG\:-8}/nbi\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/light-ui\:\${TAG\:-8}/light-ui\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/ng-ui\:\${TAG\:-8}/ng-ui\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml +sudo sed -i "s/keystone\:\${TAG\:-8}/keystone\:\${TAG\:-releaseeight-daily}/" /etc/osm/docker/docker-compose.yaml docker stack rm osm docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -430,7 +433,7 @@ sudo apt-get remove python-osmclient sudo apt-get remove pytho3-osmclient # Clean the previous repos that might exist sudo sed -i "/osm-download.etsi.org/d" /etc/apt/sources.list -sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseSEVEN-daily testing osmclient" +sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseEIGHT-daily testing osmclient" sudo apt-get update sudo apt-get install python3-osmclient dpkg -l |grep python3-osmclient #to check the installed version @@ -457,7 +460,7 @@ docker service update osm_ro --force --image opensourcemano/ro:develop # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/ro\:\${TAG\:-7}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/ro\:\${TAG\:-8}/ro\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -472,7 +475,7 @@ docker service update osm_lcm --force --image opensourcemano/lcm:develop # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/lcm\:\${TAG\:-7}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/lcm\:\${TAG\:-8}/lcm\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -487,7 +490,7 @@ docker service update osm_mon --force --image opensourcemano/mon:develop # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/mon\:\${TAG\:-7}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/mon\:\${TAG\:-8}/mon\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -502,7 +505,7 @@ docker service update osm_pol --force --image opensourcemano/pol:develop # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/pol\:\${TAG\:-7}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/pol\:\${TAG\:-8}/pol\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -517,7 +520,7 @@ docker service update osm_nbi --force --image opensourcemano/nbi:develop # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/nbi\:\${TAG\:-7}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/nbi\:\${TAG\:-8}/nbi\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -532,7 +535,7 @@ docker service update osm_light-ui --force --image opensourcemano/light-ui:devel # In order to make this change persistent after reboots or restart of the docker stack # you will have to update the file /etc/osm/docker/docker-compose.yaml to reflect the change # in the docker image, for instance: -# sudo sed -i "s/light-ui\:\${TAG\:-7}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml +# sudo sed -i "s/light-ui\:\${TAG\:-8}/light-ui\:\${TAG\:-develop}/" /etc/osm/docker/docker-compose.yaml # docker stack rm osm # docker stack deploy -c /etc/osm/docker/docker-compose.yaml osm ``` @@ -580,7 +583,7 @@ Or to use an old version of MON: Upgrading to the latest minor version is as simple as running again the installer: ```bash -wget https://osm-download.etsi.org/ftp/osm-7.0-seven/install_osm.sh +wget https://osm-download.etsi.org/ftp/osm-8.0-eight/install_osm.sh chmod +x install_osm.sh ./install_osm.sh -c k8s ``` @@ -600,7 +603,7 @@ You can use option `-t` in the installer to specify a specific docker tag to be To install the latest daily images: ```bash -./install_osm.sh -c k8s -t releaseseven-daily +./install_osm.sh -c k8s -t releaseeight-daily ``` To install a previous version e.g. v6.0.3: @@ -611,16 +614,16 @@ To install a previous version e.g. v6.0.3: The previous commands will do the installation and deployment of the whole platform in the namespace `osm`. -Another option is to change directly the K8s Manifest YAML files located in `/etc/osm/docker/osm_pods`. Below an example to update them to use `releaseseven-daily` tag: +Another option is to change directly the K8s Manifest YAML files located in `/etc/osm/docker/osm_pods`. Below an example to update them to use `releaseeight-daily` tag: ```bash -sudo sed -i "s/opensourcemano\/ro:.*/opensourcemano\/ro:releaseseven-daily/g" /etc/osm/docker/osm_pods/ro.yaml -sudo sed -i "s/opensourcemano\/lcm:.*/opensourcemano\/lcm:releaseseven-daily/g" /etc/osm/docker/osm_pods/lcm.yaml -sudo sed -i "s/opensourcemano\/mon:.*/opensourcemano\/mon:releaseseven-daily/g" /etc/osm/docker/osm_pods/mon.yaml -sudo sed -i "s/opensourcemano\/pol:.*/opensourcemano\/pol:releaseseven-daily/g" /etc/osm/docker/osm_pods/pol.yaml -sudo sed -i "s/opensourcemano\/nbi:.*/opensourcemano\/nbi:releaseseven-daily/g" /etc/osm/docker/osm_pods/nbi.yaml -sudo sed -i "s/opensourcemano\/light-ui:.*/opensourcemano\/light-ui:releaseseven-daily/g" /etc/osm/docker/osm_pods/light-ui.yaml -sudo sed -i "s/opensourcemano\/keystone:.*/opensourcemano\/keystone:releaseseven-daily/g" /etc/osm/docker/osm_pods/keystone.yaml +sudo sed -i "s/opensourcemano\/ro:.*/opensourcemano\/ro:releaseeight-daily/g" /etc/osm/docker/osm_pods/ro.yaml +sudo sed -i "s/opensourcemano\/lcm:.*/opensourcemano\/lcm:releaseeight-daily/g" /etc/osm/docker/osm_pods/lcm.yaml +sudo sed -i "s/opensourcemano\/mon:.*/opensourcemano\/mon:releaseeight-daily/g" /etc/osm/docker/osm_pods/mon.yaml +sudo sed -i "s/opensourcemano\/pol:.*/opensourcemano\/pol:releaseeight-daily/g" /etc/osm/docker/osm_pods/pol.yaml +sudo sed -i "s/opensourcemano\/nbi:.*/opensourcemano\/nbi:releaseeight-daily/g" /etc/osm/docker/osm_pods/nbi.yaml +sudo sed -i "s/opensourcemano\/light-ui:.*/opensourcemano\/light-ui:releaseeight-daily/g" /etc/osm/docker/osm_pods/light-ui.yaml +sudo sed -i "s/opensourcemano\/keystone:.*/opensourcemano\/keystone:releaseeight-daily/g" /etc/osm/docker/osm_pods/keystone.yaml kubectl -n osm apply -f /etc/osm/docker/osm_pods ``` @@ -631,7 +634,7 @@ sudo apt-get remove python-osmclient sudo apt-get remove pytho3-osmclient # Clean the previous repos that might exist sudo sed -i "/osm-download.etsi.org/d" /etc/apt/sources.list -sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseSEVEN-daily testing osmclient" +sudo add-apt-repository -y "deb [arch=amd64] https://osm-download.etsi.org/repository/osm/debian/ReleaseEIGHT-daily testing osmclient" sudo apt-get update sudo apt-get install python3-osmclient dpkg -l |grep python3-osmclient #to check the installed version diff --git a/05-osm-usage.md b/05-osm-usage.md index 8740006..f6d7ff1 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -308,7 +308,7 @@ Day-1 and Day-2 are both managed by the VCA (VNF Configuration & Abstraction) mo There are two types of charms: -- **Native charms:** the set of scripts run inside the VNF components. This kind of charms are new in Release 7. +- **Native charms:** the set of scripts run inside the VNF components. - **Proxy charms:** the set of scripts run in LXC containers in an OSM-managed machine (which could be where OSM resides), which use ssh or other methods to get into the VNF instances and configure them. ![OSM Proxy Charms](assets/800px-OSM_proxycharms.png) @@ -1151,7 +1151,7 @@ To remove the NSI2 run the command: `osm nsi-delete my_shared_slice`. ## Using Kubernetes-based VNFs (KNFs) -From Release SEVEN, OSM supports Kubernetes-based Network Functions (KNF). This feature unlocks more than 20.000 packages that can be deployed besides VNFs and PNFs. This section guides you to deploy your first KNF, from the installation of multiple ways of Kubernetes clusters until the selection of the package and deployment. +OSM supports Kubernetes-based Network Functions (KNF). This feature unlocks more than 20.000 packages that can be deployed besides VNFs and PNFs. This section guides you to deploy your first KNF, from the installation of multiple ways of Kubernetes clusters until the selection of the package and deployment. ### Kubernetes installation diff --git a/09-troubleshooting.md b/09-troubleshooting.md index b66bb57..d6ef191 100644 --- a/09-troubleshooting.md +++ b/09-troubleshooting.md @@ -15,7 +15,7 @@ dpkg -l osm-devops ||/ Name Version Architecture Description +++-======================-=================-=====================-===================================== -ii osm-devops 7.0.0-1 all +ii osm-devops 8.0.0-1 all ``` To know the current verion of the OSM client, you can also search the `python3-osmclient` package as a way to know your current version of OSM: @@ -24,7 +24,7 @@ To know the current verion of the OSM client, you can also search the `python3-o dpkg -l python3-osmclient ||/ Name Version Architecture Description +++-======================-=================-=====================-===================================== -ii python3-osmclient 7.0.0-1 all +ii python3-osmclient 8.0.0-1 all ``` ## Recommended installation to facilitate troubleshooting @@ -32,7 +32,7 @@ ii python3-osmclient 7.0.0-1 all It is highly recommended saving a log of your installation: ```bash -$ ./install_osm.sh 2>&1 | tee osm_install_log.txt +./install_osm.sh 2>&1 | tee osm_install_log.txt ``` ## Common issues and troubleshooting @@ -274,10 +274,10 @@ These are the steps to install NBI certificate on the client side (tested for Ub docker ps | grep nbi docker cp :/app/NBI/osm_nbi/http/cert.pem . ``` - - From souce code: NBI-folder/osm_nbi/http/cert.pem + - From source code: NBI-folder/osm_nbi/http/cert.pem - From ETSI's git: ```bash - wget -O cert.pem "https://osm.etsi.org/gitweb/?p=osm/NBI.git;a=blob_plain;f=osm_nbi/http/cert.pem;hb=refs/heads/v7.0" + wget -O cert.pem "https://osm.etsi.org/gitweb/?p=osm/NBI.git;a=blob_plain;f=osm_nbi/http/cert.pem;hb=refs/heads/v8.0" ``` 2. Then, you should install this certificate: ```bash diff --git a/10-osm-client-commands-reference.md b/10-osm-client-commands-reference.md index 4c6e060..bb872e3 100644 --- a/10-osm-client-commands-reference.md +++ b/10-osm-client-commands-reference.md @@ -158,7 +158,7 @@ sudo -H python3 -m pip install git+https://osm.etsi.org/gerrit/osm/IM --upgrade # You can install the latest client from master branch in this way: sudo -H python3 -m pip install git+https://osm.etsi.org/gerrit/osm/osmclient # You could also install a specific tag/version in this way -sudo -H python3 -m pip install git+https://osm.etsi.org/gerrit/osm/osmclient@v7.0.0rc1 +sudo -H python3 -m pip install git+https://osm.etsi.org/gerrit/osm/osmclient@v8.0.0rc1 ``` ### Installing from cloned repo (for developers) diff --git a/11-osm-im.md b/11-osm-im.md index cdb9619..22b23f7 100644 --- a/11-osm-im.md +++ b/11-osm-im.md @@ -14,7 +14,7 @@ Below you can find tree representations of the VNFD (VNF Descriptor), NSD (Netwo **Navigable version:** -**** +**** **Plain text version:** @@ -476,7 +476,7 @@ module: vnfd **Navigable version:** -**** +**** **Plain text version:** @@ -702,7 +702,7 @@ module: nsd **Navigable version:** -**** +**** **Plain text version:** @@ -835,7 +835,7 @@ module: nst **Navigable version:** -**** +**** **Plain text version:** @@ -1632,7 +1632,7 @@ module: vnfr **Navigable version:** -**** +**** **Plain text version:** @@ -2263,7 +2263,7 @@ module: nsr **Navigable version:** -**** +**** **Plain text version:** -- GitLab