Allotted Resources are portions of one service which can be allotted to be used as resources by another. The distinguishing factor that makes a Resource allotted is simply the requirement for a service which has an AllottedResourceProvider constrained by a valid source type which is the allotted resource's node type. There is no longer a need for a specific based type for Allotted Resources.
This permits allotted network functions to be chosen during abstraction resolution as long as filtering criteria are matched.See also:
Allotted Resource Model explains the allotted resource concept in general.
TIDM onap.relationships.AllottedBy
A capability derived of this type, when exposed by a service, indicates that a "slice" of this service can be used as a resource inside another service.
A requirement for this capability type specified an abstract resource node suggests that the orchestrator will resolve this abstraction by taking a slice of an already deployed provider service.
To assist the orchestrator in finding the best match, the designer is supposed to specify the expected type of the provided resource in the valid_source_types construct.
Definition
| Code Block | ||||
|---|---|---|---|---|
| ||||
onap.capabilities.AllottedResourceProvider:
derived_from: tosca.capabilities.Root
description: Capability to produce allotted resources
valid_source_types: [] |
Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
capability_types:
vendorYYY.capabilities.SunshineDatabaseAsAServiceProvider:
derived_from: onap.capabilities.AllottedResourceProvider
valid_source_types: [vendorYYY.nodes.SunshineDatabase] |