Setup and register a GCP VIM in OSM

#### 2. Create a management network, with DHCP enabled, reachable from OSM

(particularly, it should be reachable from VCA container)

You need to create a management network, with DHCP enabled, and guarantee that this management network is reachable from OSM. The network is used by the VCA (Juju) for configuring the VNFs once they are running. It is recommended to create a provider network, isolated from OpenStack. For instance, in order to create a provider network using physical interface em1 and VLAN 500 and with CIDR 10.208.0.0/24, you should run the following commands:

```bash

#### 2. Create Microsoft Azure Virtual Network

The virtual networks created for the Azure VIM will all be created as subnets from a base virtual network. This base virtual network should be created before adding the VIM target and will also be provided as a configuration parameter.

The virtual networks created for the Azure VIM will all be created as subnets from a base virtual network `vnet_name`. This base virtual network should be created before adding the VIM target and will also be provided as a configuration parameter.

It is also recommended to create a management subnet in that virtual network for the VIM network services, and both vnet and subnet can be created in a single step. For example, this command creates in `osmRG` resource group (must exist) the `osm_vnet` virtual network and the `internal` management subnet which uses `10.0.0.0/24` address prefix:

**NOTE for VNF Onboarding:** You need to make sure that your VNF packages include a reference to an appropriate alternative image in Microsoft Azure's image repository. In case you are creating a VNF Package from scratch, please note you should use the full Azure image name: `publisher:offer:sku:version` (e.g. `Canonical:UbuntuServer:18.04-LTS:18.04.201809110`).

## Google Cloud Platform (GCP)

### Preparation for using GCP in OSM

#### 1. Obtain GCP credentials and project from Google GCP

In order to use a VIM target based on Google Cloud, the following information needs to be gathered:

- Access credentials file (`creds`): the JSON file corresponding to a GCP service account. This file is obtained from the portal in the moment the service account is created.

- The `project`, the name of the Google Cloud project to be used to deploy IaaS resources (VM, nets, etc.).

- The `region`to be used to deploy IaaS resources (VM, nets, etc.).

The `project` and `region` can be obtained through the GCP portal or the GCP CLI. For instance, the command `gcloud config list` returns all properties of the active configuration, including the `account` used to authorize access to the GCP, the `project` and the `region`.

#### 2. Create Google GCP Virtual Network

You need to create a management network, with DHCP enabled, and guarantee that this management network is reachable from OSM. The network is used by the VCA (Juju) for configuring the VNFs once they are running. It is recommended to create a provider network, isolated from OpenStack. For instance, these commands creates the `osm_vnet` virtual network and the `internal` management subnet which uses `10.10.0.0/24` address prefix:

```bash

gcloud compute networks create osm-net --subnet-mode=custom

gcloud compute networks subnets create internal --network=osm-net --range=10.10.0.0/24 --region=region_id

```

### Adding GCP as VIM target in OSM

To sum up, in order to register a GCP VIM target in OSM, the following command and options should be used:

```bash

osm vim-create --name gcp --account_type gcp --project "<project>" --description "Google Cloud"

    --config "{region_name: <region>, use_floating_ip: True}"

    --creds <credential_json_file>

```

where:

- `project`: corresponds to the project name.

- `region`: corresponds to the region name.

- `credentials_json_file`: Service account JSON file.

- `use_floatinp_ip` is set to True in order to allow automatic public IP addresses in all the interfaces connected to the management network of a NS.

**NOTE for VNF Onboarding:** You need to make sure that your VNF packages include a reference to an appropriate alternative image in Google Cloud's image repository. In Google Cloud there are a set of public preconfigured images grouped in image projects. In case you are creating a VNF Package from scratch, please note you should use the following naming conventions to get the Google Cloud image:

- `<image_project>:image-family:<family>`: to get the latest version of the images of the family `<family>` in the project `<image_project>` (e.g. `ubuntu-os-cloud:image-family:ubuntu-1804-lts`)

- `<image_project>:image:<image>`: to get a specific image `<image>` in the project `<image_project>` (e.g. `ubuntu-os-cloud:image:ubuntu-1804-bionic-v20210928`)

- `<image_project>:<image>`: equivalent to `<image_project>:image:<image>` (e.g. `ubuntu-os-cloud:ubuntu-1804-bionic-v20210928`)

## Eclipse fog05

Eclipse fog05 (can be read as _fog-O-five_ or _fog-O-S_) is a different kind of VIM, designed to manage a fog/edge environment, thus it is completely distributed (no controller/master node) and pluggable, and available as FOSS from Eclipse: <https://github.com/eclipse-fog05>