diff --git a/05-osm-usage.md b/05-osm-usage.md index 6f463cea2ed91b348638dbf75fe10bb8e5956a9f..f4fb8afebb63bfc86162faa1db56989696be48a8 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -198,11 +198,55 @@ All day1-2:terminate-config-primitives are allowed to change. Policy update changes are performed on running VNF instance unless `software-version` is changed in the new revision of VNFD. -TODO: write the alterable parameters +Policy update can be used to update all the parameters related to policies like scaling-aspect and healing. + +```yaml + +--rw vdu* [id] + | +--rw scaling-aspect* [id] + | | +--rw id string + | | +--rw name? string + | | +--rw description? string + | | +--rw max-scale-level? uint32 + | | +--rw aspect-delta-details + | | | +--rw deltas* [id] + | | | | +--rw id string + | | | | +--rw vdu-delta* [id] + | | | | | +--rw id -> ../../../../../../vdu/id + | | | | | +--rw number-of-instances? uint32 + | | | | +--rw virtual-link-bit-rate-delta* [id] + | | | | | +--rw id string + | | | | | +--rw bit-rate-requirements + | | | | | +--rw root uint32 + | | | | | +--rw leaf? uint32 + | | | | +--rw scaling:kdu-resource-delta* [id] + | | | | +--rw scaling:id -> ../../../../../kdu-resource-profile/id + | | | | +--rw scaling:number-of-instances? uint32 + | | | +--rw step-deltas? -> ../deltas/id + | | +--rw scaling:scaling-policy* [name] + | | | +--rw scaling:name string + | | | +--rw scaling:scaling-type? common:scaling-policy-type + | | | +--rw scaling:enabled? boolean + | | | +--rw scaling:scale-in-operation-type? common:scaling-criteria-operation + | | | +--rw scaling:scale-out-operation-type? common:scaling-criteria-operation + | | | +--rw scaling:threshold-time uint32 + | | | +--rw scaling:cooldown-time uint32 + | | | +--rw scaling:scaling-criteria* [name] + | | | +--rw scaling:name string + | | | +--rw scaling:scale-in-threshold? decimal64 + | | | +--rw scaling:scale-in-relational-operation? common:relational-operation-type + | | | +--rw scaling:scale-out-threshold? decimal64 + | | | +--rw scaling:scale-out-relational-operation? common:relational-operation-type + | | | +--rw scaling:vnf-monitoring-param-ref? string + | | +--rw scaling:scaling-config-action* [trigger] + | | +--rw scaling:trigger common:scaling-trigger + | | +--rw scaling:vnf-config-primitive-name-ref? -> /vnfd:vnfd/df/lcm-operations-configuration/operate-vnf-op-config/day1-2:day1-2/config-primitive/name +``` #### REMOVE_VNF Update -TODO: write the details +REMOVE_VNF operation involves terminating a running VNF instance. This operation could terminate one VNF instance at a time from a NS instance. If termination is invoked for a VNF and it is the last VNF instance in a NS instance, then it cannot be terminated. + +The Remove VNF operation currently does not support VNFs that include charms. ### Perform NS Update Operation @@ -233,6 +277,38 @@ Example command: osm ns-update 6f0835ba-50cb-4e69-b745-022ea2319b96 --updatetype CHANGE_VNFPKG --config '{changeVnfPackageData: [{vnfInstanceId: "f13dfde9-b7da-4469-a921-1a66923f084c", vnfdId: "7f30ca8b-2c96-4bd3-8eab-b7eb19c2a9ed"}]}' --timeout 300 --wait ``` +#### Removing a VNF from UI + +- Go to 'NS Instances' on the 'Instances' menu to the left +- Next, in the NS instance where the VNF to be terminated is a part of, click on the 'Action' button. +- From the dropdown actions, click on 'NS Update' + +![Remove VNF](assets/500px-NS_Update_Terminate_VNF.png) + +- Fill in the form by selecting 'REMOVE_VNF' from the dropdown of 'Update Type' and the member vnf index of the VNF to be terminated and click 'Apply' +- A warning message is displayed, click 'Terminate VNF' to proceed + - Click 'Cancel' to cancel the termination operation + +![Warning message for Terminate VNF](assets/500px-Terminate_VNF.png) + +#### Redeploying a VNF from UI + +- Go to 'NS Instances' on the 'Instances' menu to the left +- Next to the NS instance which the VNF to be redeployed is a part of, click on the 'Action' button. +- From the dropdown actions, click on 'NS Update' + +![NS Update](assets/500px-NS_Update.png) + +- Fill in the form by selecting the following, + - 'CHANGE_VNFPKG' from the dropdown of 'Update Type' + - The member vnf index of the VNF to be updated + - VNFDId for the update (Should be same as the vnfd-id of the VNF to be updated) + - Finally, click 'Apply' +- A warning message is displayed, click 'Redeploy and Update' to proceed + - Click 'Cancel' to cancel the update operation + +![Warning message for Redeploying VNF](assets/500px-NS_Update_Software_Change.png) + ## Advanced instantiation: using instantiation parameters OSM allows the parametrization of NS or NSI upon instantiation (Day-0 and Day-1), so that the user can easily decide on the key parameters of the service without any need of changing the original set of validated packages. diff --git a/assets/500px-NS_Update.png b/assets/500px-NS_Update.png new file mode 100644 index 0000000000000000000000000000000000000000..8e637b5ee79ce2b0976ef78c1d1b03f030b5ea6f Binary files /dev/null and b/assets/500px-NS_Update.png differ diff --git a/assets/500px-NS_Update_Software_Change.png b/assets/500px-NS_Update_Software_Change.png new file mode 100644 index 0000000000000000000000000000000000000000..75037b9bebcda957a9840e7393497daf2d3912e3 Binary files /dev/null and b/assets/500px-NS_Update_Software_Change.png differ diff --git a/assets/500px-NS_Update_Terminate_VNF.png b/assets/500px-NS_Update_Terminate_VNF.png new file mode 100644 index 0000000000000000000000000000000000000000..3e2eeb29d4e97dc9e76909d445603d9378fe6ecb Binary files /dev/null and b/assets/500px-NS_Update_Terminate_VNF.png differ diff --git a/assets/500px-Terminate_VNF.png b/assets/500px-Terminate_VNF.png new file mode 100644 index 0000000000000000000000000000000000000000..8d24c354eacdcf821a4fd4cd0fb6e4b0da8b3852 Binary files /dev/null and b/assets/500px-Terminate_VNF.png differ