From: garciadeblas Date: Tue, 8 Nov 2016 18:14:39 +0000 (+0100) Subject: euag_autoscaling_VNF_with_horizontal_scale_out_of_VDUs.md X-Git-Url: https://osm.etsi.org/gitweb/?a=commitdiff_plain;h=b17a14f03e834350b07fed9c835913aa4dbddf5c;p=osm%2FFeatures.git euag_autoscaling_VNF_with_horizontal_scale_out_of_VDUs.md Change-Id: I24770dc7366d919fad0b6baeb5b373bb3410df61 --- diff --git a/Release5/euag_autoscaling_VNF_with_horizontal_scale_out_of_VDUs.md b/Release5/euag_autoscaling_VNF_with_horizontal_scale_out_of_VDUs.md new file mode 100644 index 0000000..b99293f --- /dev/null +++ b/Release5/euag_autoscaling_VNF_with_horizontal_scale_out_of_VDUs.md @@ -0,0 +1,29 @@ +# Auto-scaling VNF with horizontal scale out of VDUs # + +## Proposer ## +**EUAG** + +## Type ## +**Feature** + +## Target MDG/TF ## +NBI, UI, LCM, RO, VCA + +## Description ## +Some VNFs have the capability to scale by adding more VDU/VM without adding new +internal VLDs and without changing the external connection points of the VNF, so +that this scale out has no effect in other VNFs of a NS. This is the commonest +case of scale out in cloud, so it is the most basic case to enable dynamicity in +the use of resources. This feature aims to enable this capability in OSM. + +The end user might use the UI to request, for a given NS, an action to scale a +VNF that is part of that NS. This action would be shown to the end user only if +the VNF has the capability to scale. + +In other cases, the own VNF might have been authorized to trigger (or suggest) a +scale out event based on pre-defined KPIs thresholds. + +Both use cases for driving scaling are considered of relevance for the project. + +## Demo or definition of done ## +N/A