Update 06-osm-platform-configuration.md

Where:

* `juju add-k8s` command takes the kubeconfig from stdin.

* <controller_name>: Name of the controller to which this cloud will be added to.

* <cloud_name>: The cloud name that will be assigned to the cloud. By default, the credential name will be the same as the cloud name. Underscores (“_”) or names starting with numbers (“1-9”) are not valid.

* `<controller_name>`: Name of the controller to which this cloud will be added to.

* `<cloud_name>`: The cloud name that will be assigned to the cloud. By default, the credential name will be the same as the cloud name. Underscores (“_”) or names starting with numbers (“1-9”) are not valid.

**Example:**

Example:

``` bash

$ cat kubeconfig.yaml | juju add-k8s --controller osm-vca my-k8s-cloud

```

Where:

* <controller_name>: Name of the controller to which this cloud will be added to.

* <cloud_name>: The cloud name that will be assigned to the cloud. By default, the credential name will be the same as the cloud name. Underscores (“_”) or names starting with numbers (“1-9”) are not valid.

* <cloud_file> and <credentials_file>: Path to the cloud and credentials files. The following subsections explain how to build these files.

* `<controller_name>`: Name of the controller to which this cloud will be added to.

* `<cloud_name>`: The cloud name that will be assigned to the cloud. By default, the credential name will be the same as the cloud name. Underscores (“_”) or names starting with numbers (“1-9”) are not valid.

* `<cloud_file>` and `<credentials_file>`: Path to the cloud and credentials files. The following subsections explain how to build these files.

**Cloud file**

##### Cloud file

```yaml

clouds:

          ssl-hostname-verification: false

```

*   <CLOUD_NAME>: Name of the cloud that will be specified in the `juju add-cloud` command. Underscores are not valid.

*   <LXD_ENDPOINT>: The endpoint of the LXD cloud, is the URL needed to reach the LXD Nodes. For more information, [go here](https://osm.etsi.org/docs/user-guide/16-lxd-cluster.html), and search for “What IP address or DNS name should be used to reach this node?”.

- `<CLOUD_NAME>`: Name of the cloud that will be specified in the `juju add-cloud` command. Underscores are not valid.

- `<LXD_ENDPOINT>`: The endpoint of the LXD cloud, is the URL needed to reach the LXD Nodes. For more information, [go here](https://osm.etsi.org/docs/user-guide/16-lxd-cluster.html), and search for “What IP address or DNS name should be used to reach this node?”.

**Credentials file**

##### Credentials file

```yaml

credentials:

              <CLIENT_KEY>

```

*   <CLOUD_NAME>: Name of the cloud that will be specified in the `juju add-cloud` command.

*   <CREDENTIALS_NAME>: Name of the credentials for the cloud. No underscores or names starting with numbers are valid.

*   <SERVER_CERTIFICATE>: Obtaining the server certificate is as easy as executing the following command in an LXD Node: `$ cat /var/snap/lxd/common/lxd/server.crt`

*   <CLIENT_CERTIFICATE> and <CLIENT_KEY>: The client key and certificate will be used by Juju, to contact the LXD cloud endpoint. Can be generated with the following command: `$ openssl req -nodes -new -x509 -keyout client.key -out client.crt -days 365 -subj "/C=FR/ST=Nice/L=Nice/O=ETSI/OU=OSM/CN=osm.etsi.org"`. It is important to trust the certificate in the LXD node: `$ lxc config trust add local: client.crt`

- `<CLOUD_NAME>`: Name of the cloud that will be specified in the `juju add-cloud` command.

- `<CREDENTIALS_NAME>`: Name of the credentials for the cloud. No underscores or names starting with numbers are valid.

- `<SERVER_CERTIFICATE>`: Obtaining the server certificate is as easy as executing the following command in an LXD Node: `$ cat /var/snap/lxd/common/lxd/server.crt`

- `<CLIENT_CERTIFICATE>` and `<CLIENT_KEY>`: The client key and certificate will be used by Juju, to contact the LXD cloud endpoint. Can be generated with the following command: `$ openssl req -nodes -new -x509 -keyout client.key -out client.crt -days 365 -subj "/C=FR/ST=Nice/L=Nice/O=ETSI/OU=OSM/CN=osm.etsi.org"`. It is important to trust the certificate in the LXD node: `$ lxc config trust add local: client.crt`

**Example**

Example:

```bash

$ juju add-cloud --controller osm-vca my-lxd-cloud cloud.yaml --force

$ juju add-credential --controller osm-vca my-lxd-cloud-f credentials.yaml

```

**cloud.yaml**

`cloud.yaml`

```yaml

clouds:

          ssl-hostname-verification: false

```

**credentials.yaml**

`credentials.yaml`

```yaml

credentials:

              -----END PRIVATE KEY-----

```

```bash

$ juju add-cloud --controller osm-vca my-lxd-cloud cloud.yaml --force

$ juju add-credential --controller osm-vca my-lxd-cloud-f credentials.yaml

```

### Select clouds for vim account

Now that we know how to add LXD and K8s clouds to Juju, we only need to associate specific clouds with the vim account, so all the Proxy charms of the network functions targeting that vim will be deployed in the clouds we select.

The important thing to explain are the four parameters in the configuration of the vim account:

*   vca_cloud: Name of the cloud for LXD Proxy charms

*   vca_cloud_credential: Name of the cloud credentials for LXD Proxy charms

*   vca_k8s_cloud: Name of the cloud for K8s Proxy charms

*   vca_k8s_cloud_credential: Name of the cloud credentials for K8s Proxy charms

- vca_cloud: Name of the cloud for LXD Proxy charms

- vca_cloud_credential: Name of the cloud credentials for LXD Proxy charms

- vca_k8s_cloud: Name of the cloud for K8s Proxy charms

- vca_k8s_cloud_credential: Name of the cloud credentials for K8s Proxy charms