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 NINE brings a number of improvements over previous releases. For the full list of new features, please refer to the [Release Notes](https://osm.etsi.org/wikipub/images/0/01/OSM_Release_NINE_-_Release_Notes.pdf). For a comprehensive overview of OSM functionalities, you can also refer to the [OSM White Papers and Release Notes of previous releases](https://osm.etsi.org/wikipub/index.php/Release_notes_and_whitepapers).
Release TEN brings a number of improvements over previous releases. For the full list of new features, please refer to the [Release Notes](https://osm.etsi.org/wikipub/images/0/01/OSM_Release_TEN_-_Release_Notes.pdf). For a comprehensive overview of OSM functionalities, you can also refer to the [OSM White Papers and Release Notes of previous releases](https://osm.etsi.org/wikipub/index.php/Release_notes_and_whitepapers).
**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:
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:
@@ -504,7 +504,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 releasenine-daily
./install_osm.sh -c k8s -t releaseten-daily
```
To install a previous version e.g. v6.0.3:
@@ -515,16 +515,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 `releasenine-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 `releaseten-daily` tag:
@@ -689,7 +689,7 @@ Or to use an old version of MON:
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:
@@ -709,7 +709,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 releasenine-daily
./install_osm.sh -t releaseten-daily
```
To install a previous version e.g. 8.0.4:
@@ -718,17 +718,17 @@ To install a previous version e.g. 8.0.4:
./install_osm.sh -t 8.0.4
```
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 `releasenine-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 `releaseten-daily` tag: