Commit 2c466648 authored by lavado's avatar lavado
Browse files

Small fix

parents a8a4fc4a 14f63cc4

01-quickstart.md

+0 −1
Original line number Diff line number Diff line
@@ -106,7 +106,6 @@ If the previous docker commands do not work, you might need to either reload the 
newgrp docker

```





![OSM Docker containers](assets/600px-Osm_containers_rel5.png)



At any time, you can quickly relaunch your deployment by using the pre-built docker images, like this:

03-installing-osm.md

+2 −3
Original line number Diff line number Diff line
@@ -6,7 +6,7 @@ In order to install OSM, you will need, at least, a single server or VM with the 


- MINIMUM: 2 CPUs, 4 GB RAM, 20GB disk and a single interface with Internet access

- RECOMMENDED: 2 CPUs, 8 GB RAM, 40GB disk and a single interface with Internet access

- Base image: Ubuntu18.04 (64-bit variant required) (http://releases.ubuntu.com/18.04/)

- Base image: Ubuntu18.04 (64-bit variant required) (<http://releases.ubuntu.com/18.04/>)



In addition, you will need a Virtual Infrastructure Manager available so that OSM can orchestrate workloads on it. The following figure illustrates OSM interaction with VIMs and the VNFs to be deployed there:
@@ -361,7 +361,7 @@ dpkg -l |grep python3-osmclient #to check the installed version 


One of the commonest reasons for this type of upgrade is using your own cloned repo of a module for development purposes.



The procedure below involves building manually some docker images. The developer environment might require updating manually the MTU of the docker default "bridge" network following the procedure in this link: https://docs.docker.com/network/bridge/

The procedure below involves building manually some docker images. The developer environment might require updating manually the MTU of the docker default "bridge" network following the procedure in this link: <https://docs.docker.com/network/bridge/>



#### Upgrading RO
@@ -491,4 +491,3 @@ Or to use an old version of MON: 
```bash

./install_osm.sh -m MON -b tags/v6.0.3

```

04-vim-setup.md

+14 −15
Original line number Diff line number Diff line
@@ -1138,4 +1138,3 @@ The previous configuration has taken as a reference the documents in the links b 
- <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_planning_guide/>

- <https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/>

- <https://docs.openstack.org/newton/networking-guide/config-sriov.html>

09-troubleshooting.md

+3 −3
Original line number Diff line number Diff line
@@ -545,7 +545,7 @@ Please provide some context to your questions. As an example, find below some gu 
- In case of operational issues, the following information might help:



  - Version of OSM that you are using

- Logs of the system. Check https://osm.etsi.org/wikipub/index.php/Common_issues_and_troubleshooting to know how to get them.

- Logs of the system. Check <https://osm.etsi.org/wikipub/index.php/Common_issues_and_troubleshooting> to know how to get them.

  - Details on the actions you made to get that error so that we could reproduce it.

  - IP network details in order to help troubleshooting potential network issues. For instance:

    - Client IP address (browser, command line client, etc.) from where you are trying to access OSM

11-osm-im.md

+2 −2
Original line number Diff line number Diff line
@@ -2,7 +2,7 @@ 


## YANG model in OSM repos



YANG models can be found in the IM repo under the models folder: https://osm.etsi.org/gitweb/?p=osm/IM.git;a=tree

YANG models can be found in the IM repo under the models folder: <https://osm.etsi.org/gitweb/?p=osm/IM.git;a=tree>



OSM uses [pyang](https://github.com/mbj4668/pyang) and [pyangbind](https://github.com/robshakir/pyangbind) to generate Python classes used by the different OSM components.