Automatic parameter deployment method and device

Abstract

The invention discloses an automatic parameter deployment method, and the method comprises the steps: defining a parameter template in advance according to manufacturer information, and enabling the parameter template to comprise the attribute information of virtual resources of different versions, the parameter information needing to be operated by the virtual resources, and parameter processinglogic; obtaining key information in the virtual resource instantiation information, and matching the parameter template according to the key information; and performing template rendering according tothe information recorded in the matched parameter template and the virtual resource instantiation information to obtain corresponding parameters. The invention further discloses an automatic parameter deployment device. According to the invention, automatic deployment of parameters can be realized.

Description

technical field [0001] The invention relates to the field of computer software, in particular to the automatic deployment technology of parameters. Background technique [0002] When deploying virtualized network elements, you need to use a pre-defined VNFD, that is, a TOSCA template, to instantiate a virtual machine, including computing, storage, and network resources of the virtual machine and their specification parameters. Since the TOSCA template cannot be directly accepted by the virtualization layer system, it is necessary to convert the TOSCA template into a specific deployment command and send it to each service of the virtualization layer, including the request URL and parameters. [0003] The TOSCA specification only defines the semantics and syntax, and does not limit how to parse and process it. Therefore, at present, each manufacturer privately implements the mapping from TOSCA to RESTful API. First, TOSCA is parsed into an Abstract Syntax Tree (AST), which is...

AI Technical Summary

Problems solved by technology

[0004] The specifications of TOSCA are in continuous development. In the process of development, the problem of different TOSCA versions used by various manufacturers has emerged. In the foreseeable future, all operators and equipment manufacturers will face the problem of supporting multiple versions of TOSCA; at the same time, Although OpenStack is the real-time standard of VIM, there are also many versions. The coexistence and co-management of different VIMs from multiple vendors will inevitably lead to the diversity of VIM interfaces.

[0005] The existing technology adopts TOSCA and API parameter hard-coded correspondence. After NFV is commercialized on a large scale, version compatibility and feature adaptation are issues that must be dealt with by operators' G-VNFM and even NFVO.

However, using hard-coded methods to do this conversion obviously has great constraints on system stability, flexibility, and scalability.

Images