Commit c6959a82 authored by garciadeblas's avatar garciadeblas
Browse files

Merge branch 'feature_10975_use_existing_flavor-id' into 'master' 

add documentation on using existing flavors

See merge request !129
parents 69b779e7 6aab6896

05-osm-usage.md

+11 −0
Original line number Diff line number Diff line
@@ -633,6 +633,17 @@ An existing persistent volume could be passed as an instantiation parameter by i 


Where the `name` of the `persistent-storage` is the one in the descriptor, and the `vim-volume-id` is the ID of volume in Openstack to be used (instead of being created).



### Using existing flavors (OpenStack only)



Typically, OSM creates the flavors needed by the VDUs, which are specified by the `virtual-compute-desc` parameter in the VNFD. In some cases, flavors must contain a complex EPA configuration that is not supported by descriptors, so they need to be created manually in the VIM beforehand.



An existing flavor can be used by passing it's ID to `vim-flavor-id` at the VDU level. The following example shows the syntax:



```yaml

--config '{vnf: [ {member-vnf-index: "vnf", vdu: [ {id: hackfest_basic-VM, vim-flavor-id: "O1.medium" } ] } ] }'

```





## Understanding Day-1 and Day-2 Operations



VNF configuration is done in three "days":