Scaling or Replicating the amount of containers each OSM component has can help both with distributing the workloads (in the case of some components) and also with high availability in case of one of the replicas failing.
Scaling or replicating the amount of containers each OSM component has can help both with distributing the workloads (in the case of some components) and also with high availability in case of one of the replicas failing.
For the High Availability scenario Charms will automatically applies anti-affinity rules to distribute the component pods between different Kubernetes Worker Nodes. Therefore for _real_ High Availability a Kubernetes with multiple Worker Nodes will be needed.
For the High Availability scenario Charms will automatically apply anti-affinity rules to distribute the component pods between different Kubernetes worker nodes. Therefore for _real_ High Availability a Kubernetes with multiple Worker Nodes will be needed.
To scale a charm the following command needs to be executed:
```
```bash
juju scale-application lcm-k8s 3 # 3 being the amount of replicas
```
@@ -350,7 +350,7 @@ If the application is already scaled to the number stated in the scale-applicati
##### Scaling OSM VCA
For more detailed information about setting up a Highly Available Controller please consult the official [documentation](https://juju.is/docs/controller-high-availability).
For more detailed information about setting up a highly available controller please consult the official [documentation](https://juju.is/docs/controller-high-availability).
Nevertheless, one way of setting up a manual HA Juju Controller which will act as VCA will be demonstrated.
@@ -358,16 +358,15 @@ First of all, the set up of 3 machines with the latest LTS of Ubuntu and at leas
Afterwards, the manual cloud will be added, executing the first command and following the steps shown in the screenshot.
Once the add-cloud command is finished. The following commands will be executed to create the controller, add the remaining machines and enable HA.
```
```bash
juju bootstrap my-manual manual-controller
juju switch controller
juju add-machine ssh:ubuntu@<ip-second-machine>
@@ -379,7 +378,7 @@ Once the juju status shows all machines in a “started” state, the HA control
To install Charmed OSM with the HA controller the following argument will be passed:
```
```bash
./install_osm.sh --charmed--vca manual-controller
```
@@ -877,13 +876,13 @@ By upgrading the OSM Charms new features for operations can be enabled or a new
To update a charm to its latest stable version the following command will be executed:
```
```bash
juju upgrade-charm ui-k8s --channel stable
```
There is also the possibility to upgrade to a specific revision with the following command:
```
```bash
juju upgrade-charm ui-k8s --revision 43 # 43 being the revision number of the new charm version.
```
@@ -891,17 +890,17 @@ juju upgrade-charm ui-k8s --revision 43 # 43 being the revision number of the ne
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:
```
```bash
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).