Method and node for using templates
Embodiments herein relate to e.g. a method performed by a node for handling a management operation. The node receives from an orchestration node, a request for an operation related to virtual network function operation. The node maps a first parameter associated with the request to a second parameter related to a cloud native template; and invokes an orchestration command comprising the mapped second parameter related to the cloud native template.
1. A method performed by a node for handling a management operation, the method comprising:
receiving, from an orchestration node, a Life Cycle Management (LCM) request comprising a first parameter that is supported by the orchestration node and is incompatible with an operation provided by a cloud native deployment template;
translating the first parameter received in the LCM request to a second parameter that is compatible with the operation provided by the cloud native deployment template; and
using the second parameter that is compatible with the operation to invoke the operation provided by the cloud native deployment template.
2. The method of claim 1 , further comprising:
fetching a script from a Virtual Network Function (VNF) software package; and
using the script to translate the first parameter to the second parameter.
3. The method of claim 2 , wherein the script comprises the node calling the script.
4. The method of claim 2 , wherein input to the script is at least one of information from the LCM request received from the orchestration node, information from a request for grant, and information from a response to the request for grant.
5. The method of claim 2 , wherein output from the script comprises input parameter key-value pairs for the cloud native deployment template.
6. The method of claim 2 , wherein using the script to translate the first parameter to the second parameter comprises using a name correlation scheme to derive a Topology and Orchestration Specification for Cloud Applications (TOSCA) Virtualized Network Function Descriptor (VNFD) resource name from a corresponding resource name in the cloud native deployment template.
7. The method of claim 1 , wherein the second parameter comprises input parameter key-value pairs for cloud native template specified inputs that need values specific to the operation.
8. The method of claim 1 , wherein the first parameter comprises virtual resource parameters that are not statically defined in a VNFD.
9. The method of claim 1 , wherein the LCM request relates to adding, changing, or removing virtual resources.
10. The method of claim 1 , further comprising:
sending a request for grant to the orchestration node; and
receiving a response indicating a grant to the sent request for grant.
11. The method of claim 10 , further comprising computing resource changes to be performed, wherein the request for grant includes information associated with the computed resource changes.
12. The method of claim 1 , wherein using the second parameter to invoke the operation comprises using the second parameter to invoke a cloud native template orchestration Application Programming Interface (API) command.
13. The method of claim 1 , wherein the node is a Virtualized Network Function Manager (VNFM).
14. The method of claim 1 , wherein the orchestration node is a Network Function Virtualization Orchestrator (NFV-O).
15. The method of claim 1 , wherein using the second parameter to invoke the operation comprises using the second parameter as input to the cloud native deployment template.
16. The method of claim 15 , wherein using the second parameter as input to the cloud native deployment template comprises using a key-value pair as input to the cloud native deployment template.
17. The method of claim 1 , further comprising sending a notification to the orchestration node, wherein the notification comprises the list of virtual resources.
18. The method of claim 1 , further comprising interacting with a Virtualization Infrastructure Manager (VIM) to get a list of virtual resources deployed for a VNF.
19. The method of claim 1 , further comprising mapping at least one cloud native resource identifier to an identifier in a VNFD.
20. A node for handling a management operation, wherein the node is adapted to:
receive, from an orchestration node, a Life Cycle Management (LCM) request comprising a first parameter that is supported by the orchestration node and incompatible with an operation provided by a cloud native deployment template;
translating the first parameter received in the LCM request to a second parameter that is compatible with the operation provided by the cloud native deployment template; and
use the second parameter that is compatible with the operation to invoke the operation provided by the cloud native deployment template.
21. The node of claim 20 , wherein the node is further adapted to:
fetch a script from a Virtual Network Function (VNF) software package; and
use the script to translate the first parameter to the second parameter.
22. The node of claim 21 , wherein the script comprises the node calling the script.
23. The node of claim 21 , wherein input to the script is at least one of information from the LCM request received from the orchestration node, information from a request for grant, and information from a response to the request for grant.