From 15c9cef440763ea0aba8868cfa8ad6d6ab78b98b Mon Sep 17 00:00:00 2001 From: baldoni Date: Fri, 12 Jun 2020 17:33:55 +0200 Subject: [PATCH] Updated Eclipse fog05 VIM instructions Signed-off-by: baldoni --- 04-vim-setup.md | 57 +++++++++++-------------------------------------- 1 file changed, 13 insertions(+), 44 deletions(-) diff --git a/04-vim-setup.md b/04-vim-setup.md index 565a5d3..49695d2 100644 --- a/04-vim-setup.md +++ b/04-vim-setup.md @@ -383,49 +383,21 @@ Additional optional configuration: - `flavors_pattern`: Regular expression to be used during flavor selection. This allows to select the desired virtual machine tier. -## Fog05 +## 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: +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: It stores information in a distributed key-value store that then is able to provide location transparency to the user, and all the state information are stored in it. -### Configure fog05 for OSM - -In order to make OSM able to contact fog05, you need to configure the REST proxy on one node that has access to the whole fog05 deployment, this node will act as a proxy and thus allow OSM to interact with fog05. This requires python3-flask, fog05 python api to be installed in the node. - -```bash -$ cd fog05/src/utils/python/rest_proxy -$ sudo make install -``` - -The installation will install also a systemd service, then you have to configure this service by editing the JSON configuration file under `/etc/fos/rest/service.json` following your fog05 installation. - -```json -{ - "host": "", - "port": 8080, - "debug": false, - "yaks": "", - "sysid": "0", - "tenantid": "0", - "image_path": "imgs" -} -``` - -Then you can simply start the service using systemd. - -```bash -$ sudo systemd start fosrest -``` #### Upload Images -You can use the REST proxy also as image service, image upload can be done by using the python rest API. First generate the descriptor of your image: +Image registration can be done by using the python rest API. First generate the descriptor of your image: ```json { - "name": "", - "uri": "", + "name": "example-image", + "uri": "lxd://alpine/edge", "checksum": "" } @@ -433,10 +405,8 @@ You can use the REST proxy also as image service, image upload can be done by us the using the python api the upload of the image can be done: -```text ->>>api.image.add(img_descriptor, img_file_path) -{'result': '92274e2e-129f-40a3-be7e-a35ea596d439'} -where the value of result is the uuid of the image +```python +>>>api.image.add(img_descriptor) ``` ### Adding Eclipse fog05 as VIM target of OSM @@ -444,14 +414,13 @@ where the value of result is the uuid of the image Alike the rest of VIM types, you should provide the appropiate paramenters in `--config` when creating the VIM target. ```bash -osm vim-create --name fos --auth_url :8080 --account_type fos --tenant osm --user dummy --password dummy --config '{hypervisor: LXD}' +osm vim-create --name fos --auth_url :7447 --account_type fos --tenant osm --user dummy --password dummy --config '{hypervisor: LXD}' ``` The following configuration can be added: - `arch`: cpu architecture used when creating the VDUs for this VIM account eg. x86\_64, aarch64, default is x86\_64. -- `hypervisor`: hypervisor supported by this VIM account, can be one of: LXD, KVM, BARE, DOCKER, XEN, at least one node of the system as to be able to manage the selected hypervisor, default is LXD. -- `nodes`: if you want this VIM account to be able to manage only a subset of the nodes in the system you can pass a list of node uuids, by default is an empty list that means all nodes. +- `hypervisor`: hypervisor supported by this VIM account, can be one of: LXD, KVM, BARE, DOCKER, ROS2, at least one node of the system as to be able to manage the selected hypervisor, default and supported is LXD. #### VLAN configuration (optional) @@ -468,7 +437,7 @@ If you want your fog05 installation to be able to use VLANs for virtual networks ], "description": "linux Bridge network plugin", "configuration": { - "ylocator": "tcp/:7887", + "ylocator": "tcp/:7447", "nodeid": "", "dataplane_interface": "", "use_vlan": true, @@ -487,7 +456,7 @@ After that you have to restart the fog05 network and runtime plugins in the node Here you can find and example of network service that can be instantiated to the Eclipse fog05 VIM using OSM. The network service is composed by a single VNF based on an Alpine Linux LXD image. -**`alpinevnfd.yaml`**: +**`alpine-vnfd.yaml`**: ```yaml vnfd:vnfd-catalog: @@ -511,7 +480,7 @@ vnfd:vnfd-catalog: vcpu-count: 1 memory-mb: 256 storage-gb: 1 - image: 2db8b83a-62ea-4543-83c7-1818f403f6f4 + image: alpine-lxd interface: - name: eth0 type: EXTERNAL @@ -524,7 +493,7 @@ vnfd:vnfd-catalog: cp: eth0 ``` -**`alpinens.yaml`**: +**`alpine-ns.yaml`**: ```yaml nsd:nsd-catalog: -- GitLab