Editing the `Vagrantfile` is required if you need to customize the image for opened ports, assigned memory, etc.
For Release EIGHT, this is these are the recommended contents for the `Vagrantfile`:
For Release EIGHT, these are the recommended contents for the `Vagrantfile`:
```ruby
Vagrant.configure("2")do|config|
@@ -859,9 +859,9 @@ Or to use an old version of MON:
./install_osm.sh -c k8s -m MON -b tags/v6.0.3
```
### How to upgrade OSM when using the Charmed Installation
#### How to upgrade OSM when using the Charmed installation
#### Upgrading only a specific component
##### Upgrading only a specific component
There are two main components which can be upgraded: The OSM charms and the OSM images.
@@ -870,7 +870,7 @@ In general for a complete upgrade of an OSM component the following steps are re
1. Upgrade the OSM Charm to the latest version.
2. Upgrade the OSM version by passing the latest OSM image.
##### Upgrading OSM Charms
###### Upgrading OSM Charms
By upgrading the OSM Charms new features for operations can be enabled or a new OSM version can be supported in case the previous charm revision wasn’t able to support it. New Charm revisions will be compatible with different OSM versions, therefore the charm can be updated without updating the docker image version.
@@ -886,7 +886,7 @@ There is also the possibility to upgrade to a specific revision with the followi
juju upgrade-charm ui-k8s --revision 43 # 43 being the revision number of the new charm version.
```
##### Upgrading OSM version
###### Upgrading OSM version
OSM is distributed with docker images, therefore, when a new version is released, a new tag is created for it. To update to this new tag the following command needs to be executed:
@@ -896,7 +896,7 @@ juju config lcm-k8s image=opensourcemano/lcm:8.0.1 # 8.0.1 Being the version tag
This will restart the pod with the new image version.
##### Upgrading from source version
###### Upgrading from source version
First, the microk8s registry will have to be enabled, for more information please consult the official [documentation](https://microk8s.io/docs/registry-built-in).
