Here are some thoughts related to the points you raised,
1) Minimal attributes -
We need to insist a minimal set of attrs (say cpu, mem, disk ? ) to successfully accept VNFD flavor. Otherwise we need to fail VNFD creation. We should also look at minimal attrs required to create nova flavor as an input.
Bharath,
Here are some thoughts related to the points you raised,
1) Minimal attributes -
We need to insist a minimal set of attrs (say cpu, mem, disk ? ) to successfully accept VNFD flavor. Otherwise we need to fail VNFD creation. We should also look at minimal attrs required to create nova flavor as an input.
2) For keywords we should always stick with TOSCA key strings. See here Properties in sec 5.4.3.1 docs.oasis- open.org/ tosca/TOSCA- Simple- Profile- YAML/v1. 0/csprd01/ TOSCA-Simple- Profile- YAML-v1. 0-csprd01. html#_Toc430015 746
,
http://
3) For units for both memory (RAM) and disk we need to support all three - KB, MB, GB
4) If both 'instance_type' and actual machine attrs are specified, I'd suggest to ignore the VM attributes and go with 'instance_type'
The implementation flow described - using deviceattributes table and have this tied to VNFD lifecycle seems reasonable to me.