Commit 3f2e40c8 authored by rfigueiredo's avatar rfigueiredo
Browse files

Change 16.04 image to 18.04 used by the VNF

parent c126383a

05-osm-usage.md

+6 −6
Original line number Diff line number Diff line
@@ -10,22 +10,22 @@ The onboarding of a VNF in OSM involves preparing and adding the corresponding V 


#### Uploading VM image(s) to the VIM(s)



In this example, only a vanilla Ubuntu16.04 image is needed. It can be obtained from the following link: <https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img>

In this example, only a vanilla Ubuntu18.04 image is needed. It can be obtained from the following link: <https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img>



It will be required to upload the image into the VIM. Instructions differ from one VIM to another (please check the reference of your type of VIM).



For instance, this is the OpenStack command for uploading images:



```bash

openstack image create --file="./xenial-server-cloudimg-amd64-disk1.img" --container-format=bare --disk-format=qcow2 ubuntu16.04

openstack image create --file="./bionic-server-cloudimg-amd64.img" --container-format=bare ubuntu18.04

```



And this one is the appropriate command in OpenVIM:



```bash

#copy your image to the NFS shared folder (e.g. /mnt/openvim-nfs)

cp ./xenial-server-cloudimg-amd64-disk1.img /mnt/openvim-nfs/

openvim image-create --name cirros034 --path /mnt/openvim-nfs/xenial-server-cloudimg-amd64-disk1.img

cp ./bionic-server-cloudimg-amd64.img /mnt/openvim-nfs/

openvim image-create --name cirros034 --path /mnt/openvim-nfs/bionic-server-cloudimg-amd64.img

```



#### Onboarding a VNF Package
@@ -323,7 +323,7 @@ In a generic way, the mapping can be specified in the following way, where `vldn 
--config '{vld: [ {name: vldnet, vim-network-name: netVIM1} ] }'

```



You can try it using one of the examples of the hackfest (**packages: [hackfest_basic_vnf](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_vnf), [hackfest_basic_ns](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_ns)); images: [ubuntu16.04](https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img)**) in the following way:

You can try it using one of the examples of the hackfest (**packages: [hackfest_basic_vnf](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_vnf), [hackfest_basic_ns](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_ns)); images: [ubuntu18.04](https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img)**) in the following way:



```bash

osm ns-create --ns_name hf-basic --nsd_name hackfest_basic-ns --vim_account openstack1 --config '{vld: [ {name: mgmtnet, vim-network-name: mgmt} ] }'
@@ -351,7 +351,7 @@ The mapping can be specified in the following way, where `vldnet` is the name of 
--config '{vld: [ {name: vldnet, provider-network: {physical-network: physnet1, network-type: vlan, segmentation-id: 400} } ] }'

```



You can try it using one of the examples of the hackfest (**packages: [hackfest_basic_vnf](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_vnf), [hackfest_basic_ns](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_ns)); images: [ubuntu16.04](https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img)**) in the following way:

You can try it using one of the examples of the hackfest (**packages: [hackfest_basic_vnf](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_vnf), [hackfest_basic_ns](https://osm.etsi.org/gitlab/vnf-onboarding/osm-packages/-/tree/master/hackfest_basic_ns)); images: [ubuntu18.04](https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img)**) in the following way:



```bash

osm ns-create --ns_name hf-basic --nsd_name hackfest_basic-ns --vim_account openstack1 --config '{vld: [ {name: mgmtnet, provider-network: {physical-network: physnet1, network-type: vlan, segmentation-id: 400} } ] }'