Age | Commit message (Collapse) | Author | Files | Lines |
|
Added passthrough attributes in placement request.
Current attributes HAS request section changed to
filtering_attributes and new passthrough attributes
added in HAS request - this one is read from vnf policy
passthroughAttributes section.
Change-Id: Ic1e9dcafb0aa0ce5c1b4ddcf35d034d457ac7d48
Signed-off-by: vrvarma <vv8305@att.com>
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
Issue-ID: OPTFRA-611
|
|
Unique req field was moved from OSDF request
to VNF policy -> content -> vnfProperties
Change-Id: I96b8a2bb881370cdb8d86b52ad4798e24e98425d
Issue-ID: OPTFRA-482
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
|
|
List of candidate identifers in required and excluded
candidates list now is supported only as a list
Issue-ID: OPTFRA-486
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
Change-Id: I2fdc11bc23239eeb1500c95925f8779da89dfcaf
|
|
|
|
Fix to send num_solution as string to HAS
Issue-ID: OPTFRA-497
Change-Id: I5fe509330ccb9e1c97b92ae44cec919ada0f8594
Signed-off-by: Chayal, Avteet (ac229e) <ac229e@att.com>
|
|
Fixed TD policies after result of pair-wise testing
Change-Id: I47eb4fb4bef4fac42989770dfab8361d33ccdc5c
Issue-ID: OPTFRA-443
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
|
|
Fix OSDF input to HAS to use num_solution
Issue-ID: OPTFRA-497
Change-Id: I339a9e09aac766ce918ce6fa6d4dffc9d7ae741b
Signed-off-by: Chayal, Avteet (ac229e) <ac229e@att.com>
|
|
The fix changes how required and excluded candiates list
is generated for HAS request by OSDF. After the change it
is now alligned with request format of HAS.
Change-Id: I6c4a88c3672971e53b996d416caeda63771e08c1
Issue-ID: OPTFRA-483
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
|
|
* New local polcies for vFW TD use case
* Fixed encoding for conductor_request template and parameters
section modified to accept all requestParameters
* Conductor request can have many attributes in the
'attributes' section - all that are defined in the vnf policy file
* Conductor request can have many request parameters in the
'requestParameters' section. The parameters come from QueryPolicies.
Before list of suppoted parameters was hardcoded
* Optional 'unique' parameter added to the placementDemand section.
It is already supported by conductor for all inventory types
* Improved debug logs for local policies
* Unit tests added for expanded request format
Change-Id: I41f219c366a3a77881c7096e64a6272edbada23b
Issue-ID: OPTFRA-443
Signed-off-by: Lukasz Rajewski <lukasz.rajewski@orange.com>
|