Does a License Agreement have to have at least one feature group? VLM is really just a Party 'Simplified' attributes for this Vendor are VendorName, and Description, which can be gotten from the Party model (PartyRole) Only EntitlementPoolDesc attributes currently being used are Name and MRN. Only attributes presently used are name, metric type and metric value. Only name and type are required. MRN should also be provided, but is not required. Instances (pools, entitlmenets, and keys) are in a license management system that is outside of ONAP A&AI does know about the asset tag as an attribute of the Vnf Instance VnfInstance points back to Entitlement and the key (asset tags). Vnf to entitlement in A&AI, but not in model? Maybe add a license key type (file and string) Do not need licenseKey ;/ License file?? FeatureGroup can have 1 or more EntitlementPools and related Entitlements related to it. Valid Relationship??

A licenseKeyPool can contain some number of LicenseKeys.

LicenseKey can have some number of service provider based limits applied to it. lLicenseKeyPool can have some number of service provider specified PoolLimits

LicenseKey can have some number of vendor based limits applied to it.

An EntitlementPool and the associated Entitlements can have some number of Service Provider based limits. EntitlementPool can have some number of service provider specified limits.

An EntitlementPool and the associated Entitlements can have some number of Vendor based limits. The EntitlementPool can have some number of Vendor specified limits.

A FeatureGroup can have one or more EntitlementPools associated with it. The EntitlementPool can be related to one FeatureGroup FeatureGroup can be related to some number of EntitlementPools.

FeatureGroup can have 1 or more LicenseKeyPools and related LicenseKeys related to it. LicenseKeyPool is related to one FeatureGroup A feature group can be related to some number of LicenseKeyPools

A FeatureGroup must be related to a Vnfd. Vnfd can have some number of feature groups

A Vendor can have some number of LicenseAgreements. A LicenseAgreement is related to some vendor.

EntitlementPool can contain some number of EntitlementInstances

A License Key Group is created for each type of License Key that is required for the software. Each License Key Group is assigned a Name and Description for modeling purposes and is uniquely identified by a UUID. In addition, a list of characteristics of the License Key Group are defined. The license key group model provides a description to systems like ALTS for the license keys that are provided by a vendor. ALTS will create a “group” and Purchasing systems (GPS and HP Asset Center) will send the inventory of license keys/files to be held by ALTS in the appropriate group. Controllers will request license keys from ALTS using the UUID of the group, as directed by the ASDC models for the software (i.e. VFs). A license key group is not specific to a feature group. A license key group may be related to multiple feature groups of a software item or even to multiple software items. Pool limits applied by the service provider Pool limits applied by the vendor. The license key may be ‘universal’ or ‘unique’ or ‘one-time’. - A ‘universal’ value indicates that the same exact license key (string) may be associated with all instances of the software. - A ‘unique’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may be returned to the license key pool for reuse. - A ‘one-time’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may not be reused. Units can be either absolute or a percentage (%). Specified threshold value for the license key pool. Specifies how the key must be purchased. If in blocks of 1000, the increment would be 1000. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. Identifier that stays the same irrespective of version. The version of this entity. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. LicenseKeyPool can contain some number of LicenseKeyInstances. A Service Provider internally generated asset tag (id). Vendor provided license key value that is entered into the vendor software to activiate / unlock it. The requestor of the license key. The assignment status of the license (assigned, available, ...). The date the license key was assigned. Vendor provided license key file that is entered into the vendor software to activiate / unlock it. A variable set of values that identify the limits that may be imposed by an entitlement instance in the pool. Multiple constraints may be applicable for an instance of entitlement in the pool. For example, an entitlement based on GB and number of sessions. Increments, aggregation function, time scope, threshold value may repeat for each metric in the list. Limits can be applied by the vendor or the service provider. Specifies if this pool holds entitlements based on usage of the software (number of users), number of sessions, country, line of business, etc. The value of some limit being applied. Type of aggregation being performed (Peak or Average) The units of the limit (Trunks, Users, Subscribers, Sessions, tentants, Tokens, Seats, TB, GB, MB, ...) Units time is specified in (day, month, hour, minute, second, millisecond. LimitMetricType if Other enumeration is selected. Represents an instance of a EntitlementDesc. Specifies the use rights for the software as described by the license. A Service Provider internally generated asset tag (id). The requestor of the entitlement. The assignment status of the entitlement (assigned, available, ...). The date the entitlement was assigned. An EntitlementPool is created for each type of Entitlement that is required for the software products. An EntitlementPool is not specific to a Feature Group. An Entitlement Pool may be related to multiple Feature Groups of a software product or even to multiple software products. Purchased entitlements are inventoried in the Entitlement Pools. Multiple pools for the same type of entitlement may be created based on the constraints. An Entitlement Pool is created for each type of Entitlement that is required for the software products. Each Entitlement Pool is assigned a Name and Description for modeling purposes and is uniquely identified by a UUID. In addition, a list of characteristics of the Entitlement Pool are defined. Controllers will request entitlements. An entitlement pool is not specific to a feature group. An entitlement pool may be related to multiple feature groups of a software item or even to multiple software items. Note: The only fields being used in this class are Name and MRN (manufactureReferenceNumber. The rest are optional. Note: StateDate and ExpiryDate are covered by the inherited validFor attribute. Note: description is required according to the inherited attribute, but it presently is optional. Note: description is required according to the inherited attribute, but it presently is optional. Pool limits applied by the service provider Pool limits applied by the vendor. Identifier for the entitlement as described by the vendor in their price list / catalog /contract. This field contains information to tell a Designer how the entitlement must be purchased. For example, if the entitlement must be purchased in blocks of 1000, the increment would be 1000. A description of a threshold that will be assessed for some business purpose (e.g. 20% of entitlement pool remains available). (The threshold of interest to DCAE or Capacity Planning, etc.) This may be an absolute value or a percentage. For example: when 90% of the pool is in-use, trigger an additional purchase of inventory. A description of a threshold that will be assessed for some business purpose (e.g. 20% of entitlement pool remains available). (The threshold of interest to DCAE or Capacity Planning, etc.) This may be an absolute value or a percentage. For example: when 90% of the pool is in-use, trigger an additional purchase of inventory. Specifies the Units for the ThresholdValue. Identifier that stays the same irrespective of version. Identifier that stays the same irrespective of version. The version of this entity. The license key may be ‘universal’ or ‘unique’ or ‘one-time’. - A ‘universal’ value indicates that the same exact license key (string) may be associated with all instances of the software. - A ‘unique’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may be returned to the license key pool for reuse. - A ‘one-time’ value indicates that each instance of the software must be related to a unique license key (string). When no longer needed, the key may not be reused. EntitlementPool can contain some number of EntitlementInstances. Feature groups represent a set of the features of the software. Feature groups may be defined by the vendor and/or by the service provider. Software may be related to multiple feature groups. At least one feature group will be related to software. If no sub-sets are needed, a single feature group will be defined that represents the base or core capabilities of the software. If an Entitlement Pool or License Key Group is associated with a particular Feature Group, the Feature Group becomes a “constraint” for the pool/group. Name of the feature group Description of the feature group. The featureGroupPartNumber specifies the SKU or reference number that the Vendor has for the Vnf that this FeatureGroup is related to. The featureGroupPartNumber specifies the Vnf that this FeatureGroup is related to. An agreement between the service provider and a given vendor granting the service provider to use the vendor's products. Generally the license agreement is specific to a family of vendor products and/or to some service provider's project/product or product family. Free form text. Includes information such as operating system or hypervisor required for the software. This may also contain factors to be considered in deployment/placement of the software instances. These requirements and constraints may need to be abstracted as policies or other business rules. Term of the license: -fixed term -perpetual -unlimited -subscription OCL true Valid values: year, quarter, month, day. Not applicable when license type is Perpetual. Units of the entitlement/license term. Valid values: year, quarter, month, day.