Hi Guys,
After looking at onap tosca resource
IM(https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version)
DM(https://wiki.onap.org/display/DW/Data+Model+align+with+TOSCA+NFV+Profile),
it seems to me that several features are missing. I'm asking to add these
missing features in our onap tosca model.
- Need a way to specify root local disk size for VDU
The VM launched for VDU needs the ephemeral root local disk size, which means
the amount of local disk space to be used for the root (/) partition to be
launched with for that VM. This information is required by multiple VIM
backend(e.g. OpenStack. AWS, Azure, etc) Currently there is no way to specify
this information in onap tosca model. However, in OSASIS TOSCA's
tosca.capabilities.Compute, there is a disk_size property. We need a similar
thing in our onap model.
- Need a way to specify a fixed IP address for a CP
This feature is required for the vCPE use case, and I believe this might be
needed for other use cases too. Currently, in onap tosca model, there is no
way to specify a fixed ip address for the CP. However, in OSASIC TOSCA's
tosca.nodes.network.Port, we can specify the fixed ip for it. We need a similar
thing in our onap model.
- Need a way to make cloudinit userdata script working
The cloudinit user-data script is very useful when configuring VDU VMs and are
supported by many VIM. This feature is required by vCPE use case and I believe
this migh be needed for other use cases too. In openstack heat template, it is
expressed as the following:
user_data:
str_replace:
params:
__dcae_collector_ip__: { get_param: dcae_collector_ip }
__repo_url_blob__ : { get_param: repo_url_blob }
template: |
#!/bin/bash
# Create configuration files
mkdir /opt/config
echo "__dcae_collector_ip__" > /opt/config/dcae_collector_ip.txt
# Download and run install script
curl -k __repo_url_blob__/org.onap.demo/vnfs/vcpe/v_aaa_install.sh -o
/opt/v_aaa_install.sh
/opt/v_aaa_install.sh
The heat will first replace the user_data template script with params defined
in str_replace(i.e. __dcae_collector_ip__ in the above example), then pass the
replaced user_data template script as cloudinit user-data script when launching
the VDU VM. In our onap model, the most similar way is to use the
tosca.interfaces.node.lifecycle.Standard interface defined in tosca.nodes.root.
However, the tosca spec says in that way, the param values are passed to the
script in environment variables. However, since cloudinit doesn't support
specify environment variables, we need a similar way like str_replace to make
cloudinit userscript working.
Best Regards,
-Lianhao Lu
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
