WO2017202211A1

WO2017202211A1 - Method and device for installing service version on virtual machine

Info

Publication number: WO2017202211A1
Application number: PCT/CN2017/083977
Authority: WO
Inventors: 李跃基; 刘冉; 王鑫; 王康华
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-05-26
Filing date: 2017-05-11
Publication date: 2017-11-30
Also published as: CN107436775A

Abstract

Provided are a method and device for installing a service version on a virtual machine. The method comprises: performing instantiation of a virtual machine through a virtualized network function module manager (VNFM), and sending a product package of the VNFM to an operation and maintenance service installation module, wherein an operation and maintenance service is provided on the VNFM (101); and calling, through the VNFM, the operation and maintenance service installation module to acquire a service version installation file in the product package and a software orchestration file in the operation and maintenance service, and installing service versions of various virtual machines according to the service version installation file and the software orchestration file (102). By means of the technical solution, the consumption of network resources can be reduced, service versions are simultaneously installed on a large number of virtual machines quickly and efficiently, and the success rate is high.

Description

Method and device for installing service version on virtual machine

Technical field

The present invention relates to the field of mobile communications, and in particular, to a method and apparatus for installing a service version on a virtual machine.

Background technique

The virtualized Network Function Manager (VNFM) system installed in the virtualized Network Function Virtualization (NFV) architecture is a self-developed iTool tool. The tool supports the SSH, TELNET, and RES (resident programs) in the virtual machine mode. The version mode supports ftp and sftp. If you install a service version on a large number of VMs, you need to connect ssh and ftp to each VM. The connection takes a long time and consumes resources. When the number of ftp connections is too large, the concurrent version may fail. .

Ansible is an emerging automated operation and maintenance tool. Based on Python development, it combines the advantages of many operation and maintenance tools (puppet, cfengine, chef, func, fabric) to implement batch system configuration, batch program deployment, batch run commands and other functions. Ansible is based on modules and does not have the ability to deploy in bulk. The real bulk deployment is the module that Ansible runs, and Ansible just provides a framework. mainly includes:

1, the connection plugin connection plugins: responsible for communication with the monitored terminal;

2, host inventory: the specified operation of the host, is a configuration file to define the monitoring host;

3, various module core modules, command modules, custom modules;

4, with the help of plug-ins to complete logging log mail and other functions;

5, playbook: When the script performs multiple tasks, it is not necessary to allow the node to run multiple tasks at once.

Table 1 is a comparison table between iTool and Ansible;

Table 1

Summary of the invention

In view of the problem in the prior art that the service version is installed on a large number of virtual machines at the same time, the connection time is long and the resources are consumed, and in the case of concurrency, the issued version fails, the present invention is proposed to provide an overcoming of the above problems or A method and apparatus for installing a service version on a virtual machine that at least partially solves the above problems.

The present invention provides a method for installing a service version on a virtual machine, including:

The virtual machine is instantiated by the virtualized network function module manager VNFM, and the VNFM product package is sent to the operation and maintenance service installation module, wherein the operation and maintenance service is set on the VNFM;

The VNFM is used to invoke the operation and maintenance service installation module to obtain the service version installation files in the product package and the software orchestration files in the operation and maintenance service, and install the service version of each virtual machine according to the service version installation file and the software orchestration file.

The present invention also provides a device for installing a service version on a virtual machine, which is disposed in a virtualized network function module manager VNFM, and includes:

The instantiation module is configured to instantiate the virtual machine through the virtualized network function module manager VNFM, and send the VNFM product package to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM;

The installation module is configured to invoke the operation and maintenance service installation module of the VNFM to obtain the service version installation file in the product package and the software orchestration file in the operation and maintenance service, and install the service version of each virtual machine according to the service version installation file and the software layout file. .

The embodiment of the invention further provides an apparatus for installing a service version on a virtual machine, including:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to perform the steps in the aforementioned method.

The embodiment of the present invention further provides a computer readable storage medium for storing a program, wherein when the program is executed, the device that installs the service version on the virtual machine performs the steps in the foregoing method.

The beneficial effects of the present invention are as follows:

By adopting the automatic operation and maintenance service and developing the installation module based on the automatic operation and maintenance service, the installation sequence and the feedback of the installation progress and the log are controlled, and the installation time is improved in the prior art for installing the service version on a large number of virtual machines at the same time. Long and resource-intensive, in the case of concurrency, it will cause the problem of the failed version, reduce the cost of network resources, and install the service version on a large number of virtual machines at the same time quickly and efficiently, with a high success rate.

The above description is only an overview of the technical solutions of the present invention, and the above-described and other objects, features and advantages of the present invention can be more clearly understood. Specific embodiments of the invention are set forth below.

DRAWINGS

Various other advantages and benefits will become apparent to those skilled in the art from a The drawings are only for the purpose of illustrating the preferred embodiments and are not to be construed as limiting. Throughout the drawings, the same reference numerals are used to refer to the same parts. In the drawing:

1 is a flowchart of a method for installing a service version on a virtual machine according to an embodiment of the present invention;

2 is a flowchart of a detailed process of a method for installing a service version on a virtual machine in an NFV framework according to an embodiment of the present invention;

3 is a schematic diagram of an integration mode of a product package in a version package according to an embodiment of the present invention;

4 is a schematic diagram showing a directory structure of a baseline package according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a directory structure of a logical device package according to an embodiment of the present invention; FIG.

6 is a schematic diagram showing a directory structure of a script template according to an embodiment of the present invention;

7 is a schematic diagram of content of a logical device installation script template according to an embodiment of the present invention;

8 is a schematic diagram of a file format of an execution sequence file deviceinfo.yml of each logical device according to an embodiment of the present invention;

9 is a schematic diagram of an execution sequence file of a product package according to an embodiment of the present invention;

10 is an interaction flowchart of an service version in an Ansible installation instantiated virtual machine according to an embodiment of the present invention;

11 is an interaction flowchart of an service version in an Ansible installation and expansion virtual machine according to an embodiment of the present invention;

12 is an interaction flowchart of a service version in an Ansible upgrade virtual machine according to an embodiment of the present invention;

FIG. 13 is a schematic structural diagram of an apparatus for installing a service version on a virtual machine according to an embodiment of the present invention; FIG.

FIG. 14 is a detailed structural diagram of an apparatus for installing a service version on a virtual machine in an NFV framework according to an embodiment of the present invention.

detailed description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the embodiments of the present invention have been shown in the drawings, the embodiments Rather, these embodiments are provided so that this disclosure will be more fully understood and the scope of the disclosure will be fully disclosed.

In order to solve the problem in the prior art that the service version is installed on a large number of virtual machines at the same time, the connection time is long and the resources are consumed, and in the case of concurrency, the issued version fails. The present invention provides an NFV framework under virtual The method and device for installing the service version on the machine adopts the open source Ansible, and develops and installs the module on the basis of the Ansible version, controls the installation sequence and feedbacks the installation progress and logs. When the installation fails and needs to be retried, the retry interface of Ansible is called on the VNFM system. The invention will be further described in detail below with reference to the drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

Method embodiment

According to an embodiment of the present invention, a method for installing a service version on a virtual machine is provided. FIG. 1 is a flowchart of a method for installing a service version on a virtual machine according to an embodiment of the present invention. The method of installing the service version on the virtual machine under the NFV framework includes the following processing:

According to an embodiment of the present invention, a method for installing a service version on a virtual machine is provided. FIG. 1 is a flowchart of a method for installing a service version on a virtual machine according to an embodiment of the present invention, as shown in FIG. The method for installing a service version on a virtual machine under the NFV framework of the embodiment includes the following processing:

Step 101: Instantiate the virtual machine by using the virtualized network function module manager VNFM, and send the product package of the VNFM to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM; preferably, the product package specifically includes : custom parameter file, version file and installation information of each logical device, and script file, wherein the custom parameter file includes: a baseline common parameter template, and a logical device installation sequence The file, wherein the baseline common parameter template includes: logical device basic information and logical device common parameters. The product package is integrated in such a way that one or more baseline packages form a logical device package, and one or more logical device packages form a production package.

In the embodiment of the present invention, after the virtual machine is instantiated by the VNFM, the operation and maintenance service installation module of the VNFM is required to perform link detection of the virtual machine, and it is determined that all links are detected normally.

Step 101 specifically includes the following processing:

1. Register the version package on the VNFM, and send the product package in the version package to the operation and maintenance service installation module;

2. Perform resource scheduling and software orchestration on the VNFM, and obtain software programming files of each logical device according to the software programming results and product packages, and deliver the software programming files to the operation and maintenance service;

3. The virtual machine is instantiated by the VNFM according to the configuration information file required for the VNFM instantiation in the resource orchestration package and the version package.

In step 102, the operation and maintenance service installation module is invoked by the VNFM to obtain the service version installation file in the product package and the software orchestration file in the operation and maintenance service, and the business version of each virtual machine is installed according to the service version installation file and the software layout file.

Step 102 specifically includes: calling an installation interface of the operation and maintenance service installation module, and installing a custom parameter file and a script file in the task directory according to the service version in the operation and maintenance service directory, and a version file and installation information in the product package, The virtual machine performs the installation of the business version.

In the embodiment of the present invention, when the VNFM needs to be expanded, the VNFM needs to be configured according to the capacity expansion, and the software layout file of the virtual machine is expanded, and the software programming file is sent to the operation and maintenance service; the VNFM triggers the expansion process. The resource is created, and the pre-processing request is sent to the network element management system OMU, and the configuration data that needs to be parsed and read when the OMU installs the service version generated according to the pre-processing request is received, and the configuration data is uploaded to the operation and maintenance service; The service installation module installs the service version of the expansion VM based on the software layout files, configuration data, and service version installation files in the product package.

When the upgrade of the service version is required, the upgrade package is registered on the VNFM, and the upgrade package in the upgrade package is sent to the operation and maintenance service installation module. The software layout file of the virtual machine to be upgraded is obtained through the VNFM according to the upgrade package. Configure the required parameters for the upgrade according to the software orchestration file, and send the software orchestration file to the operation and maintenance service; invoke the operation and maintenance service installation module, and modify the software layout files of the virtual machine according to the needs of the operation and maintenance service, and upgrade the product package. The service version installation file is used to upgrade the service version of the virtual machine that needs to be upgraded.

It should be noted that, in the embodiment of the present invention, the product package satisfies the following packaging rules:

1. The version files and installation information of each baseline package included in the logical device package under the product package are saved in the roles directory under the product package;

2. The baseline common parameter template of each baseline package included in the logical device package under the product package is saved in the group_vars directory under the product package;

3. The script file of each baseline package included in the logical device package under the product package is saved in the playbook directory under the product package;

4. The logical device installation sequence file of the product package is saved in the device_order.yml directory under the product package;

5. If the product package is a multi-product package, place the package execution sequence file pack_order.yml in a directory alongside the product package.

In the embodiment of the present invention, the VNFM can also receive the service version installation progress and/or the installation log fed back by the automatic operation and maintenance service installation module.

Preferably, the automatic operation and maintenance service comprises: Ansible service.

The above technical solution of the embodiment of the present invention is described in detail below by taking the Ansible service as an example.

2 is a flowchart of a detailed process of a method for installing a service version on a virtual machine in an NFV framework according to an embodiment of the present invention. FIG. 2 is a diagram showing a method for installing a service version on a virtual machine in an NFV architecture according to an embodiment of the present invention. Including the following processing:

Step 201: deploy an Ansible service on the virtualized network function module manager VNFM.

Specifically, the Ansible service is deployed on the VNFM system. The service is stored in the VNFM version directly in the form of a zip-free package. When the VNFM is installed, Ansible is deployed at the same time.

Step 202: Perform instantiation of the virtual machine by using the VNFM. Step 202 specifically includes the following processing:

The version package is registered on the VNFM, and the version package includes: a product package, a configuration information file required for the VNFM to be instantiated; specifically, the configuration information file required for the VNFM to be instantiated includes: a policy template file, a kpi indicator file. , template files, and other configuration information files needed for VNFM instantiation;

VNFM sends the product package to the Ansible installation module, and creates a business version installation task in the Ansible directory through the Ansible installation module;

Perform resource scheduling on the VNFM, generate ade resource files, and perform software orchestration on the VNFM, and obtain custom parameter files and script files of each logical device according to the product package; specifically, the ade resource files are arranged by the ade graphical tool. A resource template file, including VMs, mirrors, networks, VM specifications, elastic groups, cloud disks, and relationship groups.

The VNFM sends the customized parameter file and the script file to the directory of the service version installation task corresponding to Ansible.

The VNFM instantiates the virtual machine based on the ade resource file and the configuration information file required for VNFM instantiation.

In the embodiment of the present invention, the VNFM system needs to inject a public key when instantiating (creating) a virtual machine, and generates a private key on the VNFM for connecting to the virtual machine for subsequent service version installation.

Step 203: The link detection interface of the Ansible installation module is used by the VNFM to detect the link of the virtual machine. When all the links are detected normally, the installation interface of the Ansible installation module is invoked to perform a service version on each virtual machine according to the product package. installation;

In step 203, the installation of the service version of each virtual machine specifically includes the following processing:

Call the installation interface of the Ansible installation module, install the custom parameter file and script file in the task directory according to the service version in the Ansible directory, and the version file and installation information in the product package to install the service version for each virtual machine.

In the embodiment of the present invention, the service version installation progress and/or the installation log fed back by the Ansible installation module may also be received through the VNFM. Preferably, in the embodiment of the present invention, the installation progress and the log are returned to the VNFM system through the REST information.

Preferably, in the embodiment of the present invention, when the service version upgrade of the virtual machine to be expanded is performed, the following processing needs to be performed:

The VNFM performs the software orchestration according to the capacity expansion, and generates a script file and a custom parameter file for the expansion of the virtual machine. The customized parameter file and the script file are sent to the directory of the service version installation task corresponding to Ansible.

The VNFM triggers the capacity expansion process and creates a resource. After the resource is successfully created, the VMF sends a pre-processing request to the network element management system (OMU). Specifically, the pre-processing request carries the information of the expanded virtual machine resource and the service version path information. The OMU needs to record the created virtual machine resource information. After the VM is created, the OMU monitors the resources. In other cases, the IP address of the VM is allocated by the OMU. The OMU will use the VM resource information delivered by the VNFM. The IP is assigned and then reported to the VNFM. The VNFM creates a virtual machine based on the reported IP. In addition, when the service version is installed, some parameters cannot be determined before installation. Only the OMU can obtain data in real time and then use it during installation.

The VNFM receives configuration data that needs to be parsed and read when the OMU is installed according to the pre-processing request, and uploads the configuration data to the directory of the service version installation task corresponding to the Ansible.

Call the installation interface of the Ansible installation module, install the custom parameter file and script file, configuration data, and the version file and installation information in the product package according to the service version in the Ansible directory, and then expand the service version of the virtual machine. installation;

Receive the service version installation progress and/or installation log fed back by the Ansible installation module through the VNFM.

Preferably, in the embodiment of the present invention, when the service version of the virtual machine is upgraded, the following processing is performed:

Register the upgrade package on the VNFM, where the upgrade package includes: upgrade product package, and configuration information required for VNFM upgrade;

VNFM sends the upgrade product package to the Ansible installation module, and creates a business version installation task in the Ansible directory through the Ansible installation module;

VNFM obtains the customized parameter file and upgrade script file of the virtual machine to be upgraded according to the upgrade product package, and configures the required parameters according to the customized parameter file.

The VNFM sends the customized parameter file and the upgrade script file to the directory of the service version installation task corresponding to Ansible.

Call the installation interface of the Ansible installation module, install the custom parameter file and the upgrade script file in the task directory according to the service version in the Ansible directory, and the version file and installation information in the product package, and perform the service version on the virtual machine to be upgraded. upgrade;

It should be noted that, in the embodiment of the present invention, the product package specifically includes:

The custom parameter file, the version file, the installation information, and the script file of each logical device, wherein the custom parameter file includes: a baseline common parameter template, and a logical device installation sequence file, wherein the baseline common parameter template includes: a logical device basic Information and logic device common parameters.

The product package is integrated in such a way that one or more baseline packages form a logical device package, and one or more logical device packages form a production package.

Furthermore, in an embodiment of the invention, the product package satisfies the following packaging rules:

The version files and installation information of each baseline package included in the logical device package under the product package are saved in the roles directory under the product package;

The baseline common parameter template of each baseline package included in the logical device package under the product package is saved in the group_vars directory under the product package;

The script file of each baseline package included in the logical device package under the product package is saved in the playbook directory under the product package;

The logical device installation order file of the product package is saved to the device_order.yml directory under the product package;

If the product package is a multi-product package, place the product package execution order file pack_order.yml in a directory alongside the product package.

The above technical solutions of the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

The embodiment of the present invention uses Ansible to install the service version, and has the following requirements for the directory and file name of the version package:

The integration mode of the product package in the version package is shown in Figure 3. The product package consists of a hierarchical relationship of the baseline package - logical device package - product package. According to the logical device type packaging mode, the packaged product package needs to provide group_vars, roles, device_order.yml and script templates for each logical device. In Figure 3:

Ansible: The root directory of the ansible version package;

Product1, product2: product package name;

Pack_order.yml: product package execution sequence file;

Hosts: virtual machine address, grouping, and login information configuration files;

Group_vars: the directory where the logical device subordinate baseline public parameter template is placed;

Roles: the baseline version placement directory;

Device_template: the script template placement directory;

Deviceinfo.yml: Whether the logical device supports resiliency and executes the sequence template file;

Ommagt, sdfv, httpv: baseline directory;

Site_scp_tmpl.yml: Script template file.

The package meets the following packaging rules as follows:

1. As shown in Figure 4, the role of each baseline package (baseline version) of the logical device belonging to the product package is placed in the roles directory under the product. When multiple logical device versions have the same baseline version, the product is The integration side summarizes to ensure the uniqueness of the baseline package. In Figure 4:

Role: the baseline directory;

Files: the baseline version directory;

Vars: the baseline parameter file;

Templates: the baseline template directory, the directory is the jinja2 file;

Task: task directory, the main.yml file in the directory will be called during installation, the main.yml content is the specific installation steps of the baseline version;

Handlers: placed in this directory is the content configuration file that needs to be executed after the baseline installation is completed, such as Mobile services, etc.

Meta: The configuration file directory that depends on other baselines. The main.yml under this directory is configured with configuration information that depends on other baselines.

2. As shown in Figure 5, the baseline public parameter template of each logical device belonging to the product package is placed in the group_vars directory. The baseline common parameter template is divided into two parts: basic information and logical device common parameters: in Figure 5,

Roles: the baseline version placement directory;

Ommagt, sdfv, httpv: baseline directory;

Site_scp_tmpl.yml: Script template file.

(1) The file name of the basic information template is: ivlm_vars_zh_tmpl.yml, and the field structure cannot be modified.

(2) The naming convention of the baseline public parameter template of the logical device, named after the logical device name + "_vars_" + "language" + "tmpl.yml", with SCP logical device as an example: scp_vars_zh_tmpl.yml and scp_vars_en_tmpl.yml respectively correspond to Chinese And English templates.

3. As shown in FIG. 6, the script template (planning file) of each logical device to which the product belongs is stored in the playbook directory, specifically:

(1) The logical device installation script template naming mode is: "site_" + logical device name + "_tmpl.yml" file, taking scp as an example: site_scp_tmpl.yml.

(2) Logical device installation script template content as shown in Figure 6, pay attention to the order of execution of each baseline role, in the template must be written in sequence.

In Figure 7:

Plan_result: the root directory where the plan file is placed;

Res_install_info.yml: The logical device planning information file, which contains the planned inelastic/elastic logical device information and the virtual machine name installed by the logical device;

Playbook: the script file placement directory;

Site_vm1_scp_1.yml: the script file after planning;

Vars: The parameter file placement directory for the plan.

4. The format of the execution order file deviceinfo.yml file of each logical device belonging to the product package is as shown in FIG. 8. It should be noted that the content of the deviceinfo.yml file and the content of the device_order.yml file are The same, the difference is deviceinfo.yml for the execution order file of each logical device after planning, device_order.yml is the execution order file of each logical device before planning.

As shown in FIG. 8, the order field indicates the execution priority of the logical device. The smaller the priority, the higher the priority is executed, and the logical device type of the priority is executed in parallel. The isScaleout field indicates whether the logical device type supports elastic expansion. If the elastic expansion is supported, it is true.

5. If the product package is a multi-product package, you need to provide an additional execution order file of the product package, that is, the pack_order.yml file, as shown in Figure 9.

The installation process of the service version of the embodiment of the present invention is described in detail below.

Ansible installs the service version in the instantiated virtual machine, as shown in Figure 10. Specifically, it includes the following processing:

Step 1, first register the version package on the VNFM;

Step 2: The VNFM sends the product package in the version package to the ansible control node, corresponding to creating the role of the role;

Step 3: Perform resource scheduling on the VNFM to generate an ade resource file.

Step 4: Perform software programming on the VNFM to generate a custom parameter file and a script file of the instantiated virtual machine; wherein each virtual machine has a different custom parameter file and a script file.

Step 5: Deliver a custom parameter file and a script file to the role role directory corresponding to ansible;

Step 6. The lifecycle process initiates an instantiation process to create an instantiated resource.

Step 7: After the resource is successfully created, the controlled version of the service version is installed to invoke the script of the corresponding node to install the service version.

In step 8, Ansible returns to the installation log in real time.

Ansible installs and expands the service version in the VM, as shown in Figure 11, which includes the following processing:

Step 1: The VNFM generates a script file and a custom parameter file according to the software layout of the elastic scaling group, wherein the custom parameter file includes the elastic scaling common parameter;

Step 2: The VNFM triggers the expansion process and creates resources.

Step 3: After the resource is successfully created, the pre-processing request is sent to the OMU, and the virtual machine resource information and the version path information are added.

Step 4, the OMU uploads some custom files that need to be generated to the corresponding role directory of the ansible;

Step 5: Trigger the Ansible command to install the script, and Ansible installs the roles one by one according to the script configuration;

Step 6, Ansible returns the installation log to VNFM in real time.

Ansible upgrades the service version in the VM. As shown in Figure 12, the following operations are included:

Step 1. Register the upgrade package on the VNFM. The upgrade package structure needs to be packaged.

Step 2: The VNFM sends the upgrade package to the ansible.

Step 3: Configure the parameters required for the upgrade, and the VNFM sends the set parameter configuration file to the ansible.

Step 4: The life cycle process triggers the corresponding upgrade script of the ansible operation, and the ansible upgrades the node that needs to be upgraded according to the upgrade script, and returns the installation log to the VNFM in real time.

In summary, by using the technical solution of the embodiment of the present invention, by using the open source Ansible and developing the installation module based on the Ansible version, controlling the installation sequence and feeding back the installation progress and the log, the prior art is solved for the simultaneous The service version is installed on a large number of VMs. The connection is time-consuming and resource-intensive. In the case of concurrency, the version fails to be delivered. This reduces the cost of network resources. The service version is installed on a large number of VMs quickly and efficiently. And the success rate is high.

Device embodiment

According to an embodiment of the present invention, a device for installing a service version on a virtual machine is provided, which is disposed in a virtualized network function module manager VNFM, and FIG. 13 is a structure of a device for installing a service version on a virtual machine according to an embodiment of the present invention. As shown in FIG. 13 , the apparatus for installing a service version on a virtual machine according to an embodiment of the present invention specifically includes an instantiation module 130 and an installation module 132. The modules of the embodiments of the present invention are described in detail below.

The instantiation module 130 is configured to instantiate the virtual machine through the virtualized network function module manager VNFM, and send the VNFM product package to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM; the instantiation module 130 is specifically used to:

Register the version package on the VNFM, send the product package in the version package to the operation and maintenance service installation module; perform resource scheduling and software orchestration on the VNFM, and obtain software programming files of each logical device according to the software programming result and the product package, and The software orchestration file is delivered to the operation and maintenance service; the virtual machine is instantiated by the VNFM according to the configuration information file required for the VNFM instantiation in the resource orchestration package and the version package.

The installation module 132 is configured to invoke the operation and maintenance service installation module of the VNFM to obtain the service version installation file in the product package and the software orchestration file in the operation and maintenance service, and perform a service version on each virtual machine according to the service version installation file and the software layout file. installation. The installation module 132 is specifically configured to:

Call the installation interface of the operation and maintenance service installation module, install the custom parameter file and script file under the task directory according to the service version in the operation and maintenance service directory, and the version file and installation information in the product package, for each virtual The machine is installed for the business version.

Preferably, the above apparatus further comprises:

The detection module is configured to invoke the operation and maintenance service installation module of the VNFM to perform link detection of the virtual machine, and determine that all links are detected normally.

The capacity expansion module is used to perform software orchestration according to the capacity expansion of the VNFM, and generates a unified software orchestration file for the expansion of the virtual machine, and delivers the software orchestration file to the operation and maintenance service; the VNFM triggers the expansion process, creates resources, and The network element management system OMU sends a pre-processing request, receives configuration data that needs to be parsed and read when the OMU installs the service version generated according to the pre-processing request, and uploads the configuration data to the operation and maintenance service; and invokes the installation interface of the operation and maintenance service installation module. The service version of the expansion VM is installed according to the software layout files, configuration data, and service version installation files in the product package.

The upgrade module is used to register the upgrade package on the VNFM, and send the upgrade package in the upgrade package to the operation and maintenance service installation module; obtain the software layout file of the virtual machine to be upgraded according to the upgrade product package through the VNFM, and arrange the software according to the software. The file configuration parameters are upgraded, and the software orchestration file is delivered to the operation and maintenance service; the operation and maintenance service installation module is invoked, and the software layout files of the virtual machine that need to be upgraded according to the operation and maintenance service are upgraded, and the service version in the upgrade product package is upgraded. Install the file to upgrade the service version of the VM that needs to be upgraded.

The receiving module is configured to receive, by using the VNFM, a service version installation progress and/or an installation log fed back by the automatic operation and maintenance service installation module.

The package meets the following packaging rules:

Preferably, in the embodiment of the present invention, the automatic operation and maintenance service includes: an Ansible service.

The above technical solution of the embodiment of the present invention will be described below by taking the Ansible service as an example.

FIG. 14 is a schematic structural diagram of an apparatus for installing a service version on a virtual machine according to an embodiment of the present invention. As shown in FIG. 14, the apparatus for installing a service version on a virtual machine in an NFV framework according to an embodiment of the present invention includes: a deployment module 140, The instantiation module 142, and the calling module 144.

a deployment module 140, configured to deploy an Ansible service on the virtualized network function module manager VNFM;

The instantiation module 142 is configured to perform instantiation of the virtual machine by using the VNFM; the instantiation module 122 is specifically configured to:

Registering a version package on the VNFM, where the version package includes: a product package, a configuration information file required for VNFM instantiation;

Send the product package to the Ansible installation module, and create a business version installation task in the Ansible directory through the Ansible installation module;

Perform resource scheduling on the VNFM, generate an ade resource file, and perform software orchestration on the VNFM, and obtain a customized parameter file and a script file of each logical device according to the product package;

And sending the customized parameter file and the script file to a directory of a service version installation task corresponding to Ansible;

The virtual machine is instantiated according to the ade resource file and the configuration information file required when the VNFM is instantiated.

The calling module 144 is configured to perform link detection of the virtual machine by using the link detection interface of the Ansible installation module by using the VNFM. When all links are detected to be normal, the installation interface of the Ansible installation module is invoked according to the product package for each virtual machine. Performing installation of the service version; the calling module 144 is specifically configured to:

Calling the installation interface of the Ansible installation module, installing the custom parameter file and the script file in the task directory according to the service version in the Ansible directory, and the version file and installation information in the product package, and performing virtual machine on each virtual machine. Installation of the business version.

Preferably, the apparatus of the embodiment of the present invention may further include: a receiving module, configured to receive, by using the VNFM, a service version installation progress and/or an installation log fed back by the Ansible installation module.

Preferably, in the embodiment of the present invention, the foregoing apparatus further includes:

The expansion module is used to perform software orchestration according to the capacity expansion and generate a script file for expanding the virtual machine. And the custom parameter file, and the customized parameter file and the script file are sent to the directory of the service version installation task corresponding to the Ansible; the expansion process is triggered, the resource is created, and after the resource is successfully created, the network element is created. The management system OMU sends a pre-processing request; receives the configuration data that needs to be parsed and read when the OMU generates the service version generated according to the pre-processing request, and uploads the configuration data to the directory of the service version installation task corresponding to the Ansible; The installation interface of the installation module is installed according to the custom parameter file and the script file, the configuration data, and the version file and installation information in the product package in the task directory of the service version in the Ansible directory. The virtual machine performs the installation of the service version; the VNFM receives the service version installation progress and/or installation log fed back by the Ansible installation module.

The upgrade module is configured to register an upgrade version package on the VNFM, where the upgrade version package includes: an upgrade product package, and configuration information required for the VNFM upgrade; sending the upgrade product package to the Ansible installation module, and The Ansible installation module creates a service version installation task in the Ansible directory; obtains a custom parameter file and an upgrade script file of the virtual machine to be upgraded according to the upgrade product package, and configures parameters required for the upgrade according to the customized parameter file. And sending the customized parameter file and the upgrade script file to the directory of the service version installation task corresponding to Ansible; calling the installation interface of the Ansible installation module, and installing the task directory according to the service version in the Ansible directory. Defining the parameter file and the upgrade script file, and the version file and the installation information in the product package, and upgrading the service version of the virtual machine to be upgraded; receiving the service version installation progress and/or feedback of the Ansible installation module through the VNFM. Installation log.

In summary, the embodiment of the present invention solves the problem of installing the module on the basis of an Ansible and developing the installation module on the basis of the Ansible version, controlling the installation sequence and feeding back the installation progress and logs, and solving the problem in the prior art for installing on a large number of virtual machines at the same time. The service version has a long connection time and consumes resources. In the case of concurrency, the issue of the failed version is reduced. The network resources are reduced. The service version is installed on a large number of VMs quickly and efficiently. The success rate is high.

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general purpose systems can also be used with the teaching based on the teachings herein. The structure required to construct such a system is apparent from the above description. Moreover, the invention is not directed to any particular programming language. It will be appreciated that the teachings of the invention described herein can be implemented in a variety of programming languages, and the description of the particular language above is described. It is intended to disclose the preferred embodiment of the invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that the embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures, and techniques are not shown in detail so as not to obscure the understanding of the description.

Similarly, the various features of the invention are sometimes grouped together into a single embodiment, in the above description of the exemplary embodiments of the invention, Figure, or a description of it. However, the method disclosed is not to be interpreted as reflecting the intention that the claimed invention requires more features than those recited in the claims. Rather, as the following claims reflect, inventive aspects reside in less than all features of the single embodiments disclosed herein. Therefore, the claims following the specific embodiments are hereby explicitly incorporated into the embodiments, and each of the claims as a separate embodiment of the invention.

Those skilled in the art will appreciate that the modules in the client in the embodiment can be adaptively changed and placed in one or more clients different from the embodiment. The modules in the embodiments can be combined into one module, and further they can be divided into a plurality of sub-modules or sub-units or sub-components. In addition to such features and/or at least some of the processes or units being mutually exclusive, any combination of the features disclosed in the specification, including the accompanying claims, the abstract and the drawings, and any methods so disclosed, or All processes or units of the client are combined. Each feature disclosed in this specification (including the accompanying claims, the abstract and the drawings) may be replaced by alternative features that provide the same, equivalent or similar purpose.

In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features that are included in other embodiments and not in other features, combinations of features of different embodiments are intended to be within the scope of the present invention. Different embodiments are formed and formed. For example, in the following claims, any one of the claimed embodiments can be used in any combination.

The various component embodiments of the present invention may be implemented in hardware, or in a software module running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or digital signal processor (DSP) may be used in practice to implement some or all of the functionality of some or all of the components loaded with the ordered web address in accordance with an embodiment of the present invention. . The invention can also be implemented as a device or device program (e.g., a computer program and a computer program product) for performing some or all of the methods described herein. Such a program implementing the invention may be stored on a computer readable medium or may be in the form of one or more signals. Such signals can be downloaded from the Internet website or The carrier signal is provided on, or provided in any other form.

For example, an embodiment of the present invention further provides an apparatus for installing a service version on a virtual machine, including:

processor;

a memory for storing processor executable instructions;

Wherein the processor is configured to:

The virtual machine is instantiated by the virtualized network function module manager VNFM, and the product package of the VNFM is sent to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM;

And acquiring, by the VNFM, an operation and maintenance service installation module, a service version installation file in the product package, and a software orchestration file in the operation and maintenance service, and the virtual machine according to the service version installation file and the software layout file. Perform the installation of the business version.

The processor can also be configured to perform other steps in the above methods.

It is to be noted that the above-described embodiments are illustrative of the invention and are not intended to be limiting, and that the invention may be devised without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as a limitation. The word "comprising" does not exclude the presence of the elements or steps that are not recited in the claims. The word "a" or "an" The invention can be implemented by means of hardware comprising several distinct elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means can be embodied by the same hardware item. The use of the words first, second, and third does not indicate any order. These words can be interpreted as names.

Industrial applicability

The method and apparatus of the present application are applicable to the field of mobile communications. By adopting the automatic operation and maintenance service and developing the installation module based on the automatic operation and maintenance service, the installation sequence and the feedback of the installation progress and the log are controlled, and the installation time is improved in the prior art for installing the service version on a large number of virtual machines at the same time. Long and resource-intensive, in the case of concurrency, it will cause the problem of the failed version, reduce the cost of network resources, and install the service version on a large number of virtual machines at the same time quickly and efficiently, with a high success rate.

Claims

A method for installing a service version on a virtual machine, including:

The virtual machine is instantiated by the virtualized network function module manager VNFM, and the product package of the VNFM is sent to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM;

And acquiring, by the VNFM, an operation and maintenance service installation module, a service version installation file in the product package, and a software orchestration file in the operation and maintenance service, and the virtual machine according to the service version installation file and the software layout file. Perform the installation of the business version.
The method of claim 1, wherein after the instantiating the virtual machine by the VNFM, the method further comprises:

The operation and maintenance service installation module is invoked by the VNFM to perform link detection of the virtual machine, and it is determined that all links are detected normally.
The method of claim 1, wherein the virtual machine is instantiated by the virtualized network function module manager VNFM, and the sending the VNFM product package to the operation and maintenance service installation module comprises:

Registering a version package on the VNFM, and sending the product package in the version package to the operation and maintenance service installation module;

Performing resource scheduling and software orchestration on the VNFM, and acquiring a software orchestration file of each logical device according to the software programming result and the product package, and delivering the software programming file to the operation and maintenance service;

The virtual machine is instantiated by the VNFM according to a resource configuration and a configuration information file required for instantiation of the VNFM in the version package.
The method of claim 3, wherein, according to the product package, the operation and maintenance service installation module is invoked by the VNFM to obtain a service version installation file in the product package and a software layout file in the operation and maintenance service, according to the method. The business version installation file and the software orchestration file are installed on the service version of each virtual machine, including:

Calling the installation interface of the operation and maintenance service installation module, and installing the custom parameter file and the script file in the task directory according to the service version in the operation and maintenance service directory, and the version file and installation information in the product package, for each virtual The machine is installed for the business version.
The method of claim 1 wherein the method further comprises:

The software is arranged according to the capacity of the VNFM, and a unified software orchestration file of the virtual machine is generated, and the software orchestration file is delivered to the operation and maintenance service;

The VNFM triggers the capacity expansion process, creates a resource, and sends a pre-processing request to the network element management system OMU, and receives configuration data that needs to be parsed and read when the OMU installs the service version generated according to the pre-processing request, and The configuration data is uploaded to the operation and maintenance service;

The installation interface of the operation and maintenance service installation module is invoked, and the business version of the expansion virtual machine is installed according to the software layout file, the configuration data, and the service version installation file in the product package.
The method of claim 1 wherein the method further comprises:

Registering an upgrade version package on the VNFM, and sending the upgrade product package in the upgrade version package to the operation and maintenance service installation module;

Obtaining, by the VNFM, the software orchestration file of the virtual machine that needs to be upgraded according to the upgrade product package, configuring the required parameters for the upgrade according to the software orchestration file, and delivering the software orchestration file to the operation and maintenance service;

Invoking the operation and maintenance service installation module, performing the service on the virtual machine to be upgraded according to the software orchestration file of the virtual machine to be upgraded in the operation and maintenance service, and the service version installation file in the upgrade product package Version upgrade.
The method of any of claims 1 to 6, wherein the product package comprises:

a custom parameter file, a version file, and installation information of each logical device, and a script file, where the custom parameter file includes: a baseline common parameter template, and a logical device installation sequence file, wherein the baseline common parameter template includes : Logical device basic information and logical device common parameters.
The method of claim 7 wherein said product package is integrated by one or more baseline packages forming a logical device package and one or more logical device packages forming a production package.
The method of claim 7 wherein said product package satisfies the following packaging rules:

The version files and installation information of each baseline package included in the logical device package under the product package are saved in the roles directory under the product package;

The baseline common parameter template of each baseline package included in the logical device package under the product package is saved in the group_vars directory under the product package;

The script file of each baseline package included in the logical device package under the product package is saved in the playbook directory under the product package;

The logical device installation order file of the product package is saved in the device_order.yml directory under the product package;

If the product package is a multi-product package, the package execution order file pack_order.yml is placed in a directory alongside the product package.
The method of claim 1 wherein the method further comprises:

Receive the service version installation progress and/or installation log fed back by the automatic operation and maintenance service installation module through the VNFM.
The method of claim 1 wherein said automated operation and maintenance service comprises: Ansible service.
A device for installing a service version on a virtual machine, where the device is disposed in a virtualized network function module manager VNFM, and the device includes:

The instantiating module is configured to perform the instantiation of the virtual machine by using the virtualized network function module manager VNFM, and send the product package of the VNFM to the operation and maintenance service installation module, where the operation and maintenance service is set on the VNFM;

The installation module is configured to acquire, by using the VNFM, an operation and maintenance service installation module, a service version installation file in the product package, and a software orchestration file in the operation and maintenance service, according to the service version installation file and the software arrangement The file is installed for each virtual machine.
A device for installing a service version on a virtual machine, comprising:

processor;

a memory for storing processor executable instructions;

The processor is configured to perform the steps in the method according to any one of claims 1 to 11.
A computer readable storage medium for storing a program, wherein the program is executed to cause a device on a virtual machine to install a service version to perform the steps in the method of any one of claims 1 to 11.