I agree (have not checked every one, but makes sense to me) From: jessie jewitt [mailto:[email protected]] Sent: Monday, April 02, 2018 2:01 PM To: SCAGGS, KEVIN <[email protected]>; MAYER, ANDREW J <[email protected]> Cc: yangxu (H) <[email protected]>; [email protected] Subject: [modeling] Classes vs. Datatypes
The following entities that are listed as "classes" on the following wiki: https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Design-2BTime-2BModel-2BClean-2BVersion&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=gZVVoWy9KwtzjPbNdGg0fg&m=f51fj_i__S8JhfBsHz-_2KoffNkTxO_tcHuCKarvE1w&s=UfRdj20zn60_hQ8NCX0WeqqnrZ7hjGUgnMDagNrfz_Y&e=> Should be "datatypes", in accordance with the ETSI NFV Info Model attached: *VirtualCpuData *VirtualMemoryData *LogicalNodeData *LinkBitrateRequirements *ScaleInfo *QoS (VnfQos?) *LocalAffinityOrAntiAffinityRule *AddressData *L2AddressData *L3AddressData *CpProtocolData *ConnectivityType *VirtualCpuPinningData *RequestedAdditionaCapabilityData *VnfConfigurableProperties *VnfcConfigurableProperties (didn't find in spec, but looks like a candidate) *LifecycleManagementScript *MonitoringParameter *VnfInfoModifiableAttributes The spec clearly defines them as datatypes. For example: "B.3.5.7.1.4.6 VirtualCpuData datatype" I believe they are also specified as TOSCA datatypes in the DM. They should be changed. -Jessie
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
