b397d01a3e
The CSAR file for VNF package registered as a sample fails to run the VNF LCM instantiate. The cause of this issue is typo and invalid definition for the VNFD. I think that the csar zip file for uploaded VNF package should be able to run the VNF LCM instantiate normally. Therefore, fix typo and invalid definition for the VNFD in the CSAR file. Also, fix to the following settings that has a dependent on environment because the current VNFD can only be run in the limited environment. * Change hash algorithm from sha-256 to sha-512 according the Glance default hash algorithm * Change from 8192 MB to 256 MB in the `min_ram` size of the VirtualStorage to work even in a low specification environment * Delete `CP1.properties.vnic_type` to work even under a virtual environment Change-Id: Icccaa523d33115e8b7ec0a6fd7e9c5f177d0a363 Closes-Bug: #1886124
32 lines
890 B
YAML
32 lines
890 B
YAML
tosca_definitions_version: tosca_simple_yaml_1_2
|
|
|
|
description: Sample VNF.
|
|
|
|
imports:
|
|
- etsi_nfv_sol001_common_types.yaml
|
|
- etsi_nfv_sol001_vnfd_types.yaml
|
|
- helloworld3_types.yaml
|
|
- helloworld3_df_simple.yaml
|
|
|
|
topology_template:
|
|
inputs:
|
|
selected_flavour:
|
|
type: string
|
|
description: VNF deployment flavour selected by the consumer. It is provided in the API
|
|
|
|
node_templates:
|
|
VNF:
|
|
type: company.provider.VNF
|
|
properties:
|
|
flavour_id: { get_input: selected_flavour }
|
|
descriptor_id: b1bb0ce7-ebca-4fa7-95ed-4840d70a1177
|
|
provider: Company
|
|
product_name: Sample VNF
|
|
software_version: '1.0'
|
|
descriptor_version: '1.0'
|
|
vnfm_info:
|
|
- Tacker
|
|
requirements:
|
|
#- virtual_link_external # mapped in lower-level templates
|
|
#- virtual_link_internal # mapped in lower-level templates
|