CN112925604B - Virtualization management platform and implementation method - Google Patents

Virtualization management platform and implementation method Download PDF

Info

Publication number
CN112925604B
CN112925604B CN201911141172.XA CN201911141172A CN112925604B CN 112925604 B CN112925604 B CN 112925604B CN 201911141172 A CN201911141172 A CN 201911141172A CN 112925604 B CN112925604 B CN 112925604B
Authority
CN
China
Prior art keywords
license
virtual machines
management platform
virtualization management
platform
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201911141172.XA
Other languages
Chinese (zh)
Other versions
CN112925604A (en
Inventor
高良伟
王力
陈海林
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Huayao Technology Co ltd
Original Assignee
Beijing Huayao Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Huayao Technology Co ltd filed Critical Beijing Huayao Technology Co ltd
Priority to CN201911141172.XA priority Critical patent/CN112925604B/en
Publication of CN112925604A publication Critical patent/CN112925604A/en
Application granted granted Critical
Publication of CN112925604B publication Critical patent/CN112925604B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/4557Distribution of virtual machine instances; Migration and load balancing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45579I/O management, e.g. providing access to device drivers or storage

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to a virtualization management platform and an implementation method. The virtual machine comprises a virtualization platform formed by a command line interface and a daemon, N (N > 1) virtual machines and information interaction channels inside the N virtual machines and the virtualization platform, wherein: the virtualization management platform starts N virtual machines, correspondingly generates matched serial device parameter files in the N virtual machines respectively, sends License requests to the virtualization management platform through information interaction channels communicated with the inside of the virtualization platform, responds to the requests according to the currently recorded License states of the virtual machines after the virtualization management platform receives the requests, and then the virtual machines execute corresponding License actions and return results to the virtualization management platform for back display. According to the invention, the virtual machine is allocated according to the resource limitation as required under the condition of not depending on network communication and not adding hardware, so that convenience and flexibility of license management of the virtual machine are improved.

Description

Virtualization management platform and implementation method
Technical Field
The invention relates to the technical field of cloud computing and virtualization management, in particular to a virtualization management platform and a management method.
Background
In the virtualization management platform, management of virtual machines is a basic function, and in particular, flexibility and convenience in configuring and using virtual machines are a big standard for user experience. The management of the virtual machine license is an important item in the management work of the virtual machine. In the prior art, a virtualization management platform generally adopts a LICENSE SERVER management mode, and the method is to build a LICENSE SERVER to which a virtual machine applies or verifies license, for example, chinese patent CN103207965a discloses a "method and device for license authentication in a virtual environment", and the method comprises the following steps:
Step1, when application software on a virtual machine starts to be used, a License authentication request message of the application software is sent to a License authentication center by calling an interface of a Hypervisor;
And step 2, receiving a response message of the License authentication center about the authentication result, and determining whether application software on the virtual machine can be used according to the authentication result.
The license authentication center described in the above method is "LICENSE SERVER". In the existing LICENSE SERVER manner, a method for managing license of the virtual machine has to build a LICENSE SERVER, directly or indirectly ensure that the network between the virtual machine and LICENSE SERVER is reachable, and let the virtual machine know LICENSE SERVER addresses and some other basic information by a configuration manner.
In the prior art, the license is directly imported according to the design of the virtual machine, such as: it is necessary to log in the virtual machine system, import license through the tools provided by the system application and verify.
Regardless of the manner in which the allocation of virtual machine licenses is accomplished, its associated configuration and operation is a "complex" process for the user in that configuring each virtual machine or manually importing a license greatly increases the user's workload if the number of virtual machines is numerous. Even though the configuration of the virtual machines can be uniformly completed in the virtual templates, if configuration information is changed, the templates must be replaced and all the virtual machines must be recreated. If the user owns a small number of virtual machines, one LICENSE SERVER is also built for the virtual machines. Moreover, whether the virtual machine is allocated with license cannot be intuitively seen on the virtualization management platform, so that the working efficiency and the user experience are reduced, and the flexibility is greatly reduced.
Disclosure of Invention
In order to overcome the problems in the prior art, the invention provides and designs a virtualization management platform and a management method, which aim to allocate virtual machines according to resource limitation on demand under the condition of not depending on network communication and not needing to add hardware so as to improve convenience and flexibility of license management of the virtual machines.
A virtualized management platform is composed of a virtualized platform composed of a user interface, a command line interface and daemon processes, N (N > 1) virtual machines and information interaction channels inside the N virtual machines and the virtualized platform, wherein:
when the virtualization management platform starts N virtual machines, an administrator respectively adds serial device parameters of the N virtual machines on the virtualization management platform, correspondingly generates matched serial device parameter files in the N virtual machines respectively, sends License requests to the virtualization management platform through information interaction channels communicated with the inside of the virtualization platform, responds to the requests according to the currently recorded License states of the virtual machines, and then the virtual machines execute corresponding License actions and return results to the virtualization management platform for back display.
The virtualization management platform can simultaneously manage at least two states of the N virtual machine license.
The two states of the virtual machine license may be PACKAGE LICENSE states formed by virtual machines with the same functional requirements and individual license states formed by virtual machines with different functional requirements.
The virtualization management platform may further define a virtual machine state to which No License is allocated as a No License state.
On the basis of the virtualized management platform, the management method for realizing the virtualized management platform comprises the following steps:
Step 1, generating license with certain resource limitation according to the self demand of the virtual machine and the total amount of platform resources;
And step 2, distributing license for the virtual machine according to the requirement, wherein the license is limited by the certain resource limit.
The virtual machines with the same management function requirements of the virtualization management platform are uniformly managed by adopting the states of the virtual machines PACKAGE LICENSE, and the implementation method is as follows:
step 1, generating PACKAGE LICENSE with a certain resource limit according to the self demand of the virtual machine and the total amount of platform resources;
step 2, allocating PACKAGE LICENSE to the virtual machine.
The virtual machines with different management function requirements of the virtualization management platform are managed by adopting states of the virtual machines Individual License, and the implementation method is as follows:
step 1, applying N Individual license for N virtual machines correspondingly, and starting the virtual machines;
And step 2, distributing Individual license to the virtual machine through a virtualization management platform.
The virtual machine state without License allocation can be defined as a No License state and managed.
The management method of the virtualization management platform can also update the virtual machines distributed with PACKAGE LICENSE uniformly by updating PACKAGE LICENSE of the platform, so that the virtual machines license in PACKAGE LICENSE state are updated uniformly in batches.
The management method of the virtualization management platform can also check license states distributed by all virtual machines in the platform through the virtualization management platform.
The PACKAGE LICENSE has resource limitations and can be shared for use by multiple virtual machines.
The invention has the following advantages: the use and the construction of the original network environment do not need to be changed or configured by other hardware, and only PACKAGE LICENSE is needed to be imported on the original virtualization platform; the communication between the virtual machine and the virtualization management platform is realized by utilizing the serial port of the virtual machine without depending on network transmission; PACKAGE LICENSE can be applied for repeated use once, and repeated application and importing along with the creation and deletion of the virtual machine are not needed; PACKAGE LICENSE may be in manual mode or automatic mode depending on the user's own field of use Jing Xuanzi; the virtual machine sharing PACKAGE LICENSE has the same license characteristics, and is convenient and flexible to use and manage; under the condition that the limit of PACKAGE LICENSE resources is not exceeded, the virtual machine can be allocated to different virtual machines for use as required; the method has the advantages that the license of all the distributed PACKAGE LICENSE virtual machines is automatically updated, and batch unified updating of the license is realized; the behavior is uniformly operated in the virtualization management platform, and the license state of the virtual machine is visible in the virtualization management platform, so that the operation and maintenance are convenient to manage; the original virtual machine license is reserved in individual license mode, so that virtual machines with the same requirements can be used PACKAGE LICENSE, and virtual machines with different requirements can be allocated individual license.
Drawings
FIG. 1 is a schematic diagram of a virtualization management platform according to the present invention;
FIG. 2 is a flow chart of a certain virtual machine in a virtualization management platform acquiring license;
FIG. 3 is a flow chart of a virtualization management platform for license allocation;
fig. 4 is a schematic diagram illustrating an embodiment of a usage state PACKAGE LICENSE according to the present invention.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. It will be understood by those skilled in the art that the present application may be practiced without these specific details and with various changes and modifications from the embodiments that follow.
As shown in fig. 1, a virtualization management platform is formed by a virtualization platform 20 formed by a user interface 10, a command line interface 21, a daemon 22, N (N > 1) virtual machines 30, and information interaction channels 24 inside the N virtual machines and the virtualization platform, wherein: when the virtualization management platform starts N virtual machines, an administrator respectively adds serial device parameters of the N virtual machines on the virtualization management platform, and correspondingly, matched serial device parameter files are respectively generated in the N virtual machines. N virtual machines send License requests to the virtualization management platform through information interaction channels communicated with the inside of the virtualization platform, the virtualization management platform responds according to the currently recorded License state of the virtual machines after receiving the information, then the virtualization management platform judges the License state and returns the information after License judgment to the virtual machines, and the virtual machines execute the corresponding License importing actions and return the results to the virtualization management platform for back display.
As shown in fig. 2, the virtualization management platform can manage at least two states of the N virtual machine license at the same time. The virtualization management platform may define the newly created virtual machine License state as a No License state. The two states of the virtual machine license can be PACKAGE LICENSE states consisting of virtual machines with the same functional requirements and individual license states consisting of virtual machines with different functional requirements; the individual license state is individual license state of the virtual machine itself.
On the basis of the virtualized management platform, the management method for realizing the virtualized management platform comprises the following steps:
Step 1, generating license with certain resource limitation according to the self demand of the virtual machine and the total amount of platform resources;
And step 2, distributing license for the virtual machine according to the requirement, wherein the license is limited by the certain resource limit.
The virtual machines with the same management function requirements of the virtualization management platform are uniformly managed by adopting the states of the virtual machines PACKAGE LICENSE, and the implementation method is as follows:
step 1, generating PACKAGE LICENSE with a certain resource limit according to the self demand of the virtual machine and the total amount of platform resources;
step 2, allocating PACKAGE LICENSE to the virtual machine.
The virtual machines with different management function requirements of the virtualization management platform are managed by adopting states of the virtual machines Individual License, and the implementation method is as follows:
step 1, applying N Individual license for N virtual machines correspondingly, and starting the virtual machines;
And step 2, distributing Individual license to the virtual machine through a virtualization management platform.
The virtual machine state without License allocation can be defined as a No License state and managed.
The management method of the virtualization management platform can also update the virtual machines distributed with PACKAGE LICENSE uniformly by updating PACKAGE LICENSE of the platform, so that the virtual machines license in PACKAGE LICENSE state are updated uniformly in batches.
The management method of the virtualization management platform can also check license states distributed by all virtual machines in the platform through the virtualization management platform.
The PACKAGE LICENSE has resource limitations and can be shared for use by multiple virtual machines.
As shown in FIG. 2, the virtualization management platform can record and manage at least two license states, PACKAGE LICENSE states and Individual License states, for a virtual machine.
As shown in fig. 1, when the virtual machine 30 is turned on, a module running inside the virtual machine, such as an Agent module, sends a license event message to the virtualization management platform, and after receiving the message, the daemon of the virtualization management platform makes a corresponding response according to the license state of the virtual machine currently recorded, if the daemon answers yes according to the judgment that the license has been allocated by the virtualization management platform, the daemon further judges the license state; if the license state is PACKAGE LICENSE, the daemon of the virtualization management platform returns PACKAGE LICENSE information to the Agent of the virtual machine, and the Agent of the virtual machine executes the action of importing PACKAGE LICENSE and returns the result to the virtualization management platform for back display; if the license status is further determined to be "Individual License", the daemon process of the virtualization management platform returns "empty" license information to the virtual machine Agent, the virtual machine Agent does not perform any license-related action, and the virtual machine extends the currently existing Individual License.
Continuing to see FIG. 2, after the virtual machine is started, an Agent running inside the virtual machine sends a License request event message to the virtualization management platform, when the daemon process of the virtualization management platform checks that the License state of the virtual machine recorded currently is "No License is allocated," i.e. answer "No", the virtual machine state of the type is defined as No License state, at this time, the daemon process further judges whether "resource limitation" is full, "yes" is returned directly, "No" is entered into a "PACKAGE LICENESE" branch, and continues to judge whether the License state can pass through the PACKAGE LICENSE automatic allocation mode, and further if PACKAGE LICENSE can be allocated automatically, i.e. answer "yes", the "License" is returned to the virtual machine; if not, the virtual machine is directly returned to restart the allocation.
The virtualization management platform defines the state of the virtual machine without License as the No License state. When the License state of the virtual machine is the No License state, the virtualization management platform returns a License event clearing message to the virtual machine Agent, and if the License exists in the virtual machine, the License event message is cleared.
As shown in fig. 3, when a license is allocated to a virtual machine at a virtualization management platform, if the virtual machine is in an on state, the virtualization management platform sends a license event message to an Agent in the virtual machine through the process, the license is imported after the Agent of the virtual machine receives the license information, and the result is returned to the virtualization management platform for back display, and meanwhile, the virtualization management platform records the license states of all the current virtual machines. If the virtual machine is in the off state, allocation individual license is not allowed, because individual license is a virtual machine private license, the virtualization management platform does not save, and needs to be transferred into the virtual machine in the state that the virtual machine is turned on.
For the purpose of making the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.
Example 1,
Step 1, based on an Array virtualization management platform, applying for the number 4 of PACKAGE LICENSE virtual machines allowed to be owned simultaneously, wherein the resource limitation of the platform is as follows: virtual site (the maximum number of virtual sites that the platform allows to create) is 10,concurrent user (the maximum number of users that the platform allows to log in simultaneously) is 100,site to site tunnel (the maximum number of point-to-point tunnels that the platform allows to create) is PACKAGE LICENSE of 20 and imported into the platform.
Step 1.1, introduction PACKAGE LICENSE: LICENSE AG < LICENSE KEY >
Step 1.2, view PACAKGE LICENSE the show LICENSE AG LICENSE information is as follows:
Step 2, creating 4 virtual machines (vm 1-vm 4), respectively allocating PACKAGE LICENSE to the 4 virtual machines, and checking license state information:
Step 2.1, creating a virtual machine: VA INSTANCE < va name > < va size > < starting port > [ NUMA domain ] [ va image ]
Step 2.2, assigning virtual machines package license:va license ag<va name><Virtual Sites><Concurrent Users><Site2Site Tunnels>
Step 2.3, checking the license state of the virtual machine at the virtualization management platform: show VA LICENSE < ag)
VA Name License Type Virtual Sites Concurrent Users Site2Site Tunnels
vm1 Package 1 10 5
vm2 Package 5 60 10
vm3 Package 2 20 5
vm4 Package 3 10 0
Step 3, starting 4 virtual machines, and entering the virtual machines to check license of the virtual machines:
step 3.1, starting a virtual machine: va start < va name ]
Step 3.2, entering a virtual machine: va control < va name ]
Step 3.3, viewing license: show version
Step 4, updating PACKAGE LICENSE on the device, and checking license of 4 virtual machines:
step 4.1, update PACKAGE LICENSE, import PACKAGE LICENSE with reference to step 1.1
Step 4.2, checking the license of the virtual machine, and referring to step 3;
as shown in fig. 4, in step 5, a virtual machine vm5 is created and started, and applied individual license for it and imported into the virtual machine and viewed:
step 5.1, creating a virtual machine (refer to step 2.1);
step 5.2, starting the virtual machine (refer to step 3.1);
Step 5.3, import individual license: VA LICENSE index < va name > < LICENSE KEY >
Step 5.4, checking license inside the virtual machine (refer to step 3.2 and step 3.3);
step 5.5, checking the license state of the virtual machine on the virtualization management platform: referring to step 2.3:
VA Name License Type Virtual Sites Concurrent Users Site2Site Tunnels
vm1 Package 1 10 5
vm2 Package 5 60 10
vm3 Package 2 20 5
vm4 Package 3 10 0
Vm5 Individual
in the second embodiment, the serial port of the virtual machine is used as a channel, the Agent can be configured correspondingly in the virtual machine, the configuration includes a command "+" executable file ", the virtualization management platform provides a unified interface call, a command" + "parameter" is sent to the interior of the virtual machine, after the Agent receives a message, if the command is checked to be configured, the corresponding executable file is executed and the corresponding parameter is transmitted, after the result is obtained, the result is returned to the virtualization management platform for result feedback, and if the command is not configured, error information is returned directly. This approach not only allows for more flexible configuration of license, but even other commands.
The detailed steps are as follows:
step 1, configuring corresponding commands and corresponding executable files in the virtual machine, for example:
set_port=/usr/bin/setPort.sh
set_ip=/usr/bin/setIP.sh
set_license=/usr/bin/setLicense.sh
step 2, the virtualization management platform sends command messages to agents in the virtual machine through a specific interface, such as:
va run vm1“set_license tD2Lt+3M-PZ7zzBxu-2QzkwyFc-v3c=#131-4d67a9ab-a9cf1831”
va run vm1“set_port-p 5903-t 10”
Step 3, when the Agent of the virtual machine receives the command message and detects that the set_port is configured with the command, executing the corresponding executable file, for example:
/usr/bin/setPort.sh-p 5903-t 10
/usr/bin/setLicense.sh tD2Lt+3M-PZ7zzBxu-2QzkwyFc-v3c=#131-4d67a9ab-a9cf1831
And 4, after the command is executed, returning an execution result to the AVX virtualization management platform for result feedback, for example: completed Successfully-!
The method applies for and manages the license of the virtual machine in a centralized manner by using PACKAGE LICENSE, realizes communication between the virtual machine and the virtualization management platform by using the mode of serial port equipment and Agent of the virtual machine, does not depend on network communication, and does not need to add a new interface to the Hypervisor. PACKAGE LICENSE can be manually distributed to the needed virtual machines within the range of resource limitation, all operations of distributing the license to the virtual machines are completed on a virtualization management platform, the license state of the virtual machines can be checked on a virtualization management platform, the whole operation process is simplified, and meanwhile, the original license of the virtual machines is compatible in a individual license mode. The method simplifies the management work of the license of the virtual machine, increases the flexibility of license management, greatly reduces the workload of users, is convenient for operation and maintenance, and improves the user experience. In addition, PACKAGE LICENSE may be set on a virtualization management platform as an automatic allocation mode, in which, in the mode, resources occupied by each virtual machine during automatic allocation are set, a virtualization management platform may ensure that a virtual machine is started to obtain PACKAGE LICENSE within a range limited by PACKAGE LICENSE resources, and occupies corresponding resources, and a shutdown may release PACKAGE LICENSE resources. This approach is much like LICENSE SERVER, but still does not require configuration of the virtual machine and still does not rely on the network. The user may select PACKAGE LICENSE a usage mode based on his own usage scenario.
It should be noted that, in the embodiments of the present invention, each unit mentioned in each device is a logic unit, and in physical aspect, one logic unit may be a physical unit, or may be a part of one physical unit, or may be implemented by a combination of multiple physical units, where the physical implementation manner of the logic units is not the most important, and the combination of functions implemented by the logic units is a key for solving the technical problem posed by the present invention. Furthermore, in order to highlight the innovative part of the present invention, the present invention does not introduce the above-described device embodiments and units less closely related to solving the technical problems posed by the present invention, but this does not indicate the absence of the above-described device embodiments and other related implementation units.
While the invention has been shown and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.

Claims (7)

1. A virtualized management platform is composed of a virtualized platform composed of a user interface, a command line interface and daemon processes, N (N is more than 1) virtual machines and information interaction channels between the N virtual machines and the inside of the virtualized platform, and is characterized in that:
When the virtualization management platform starts N virtual machines, an administrator respectively adds serial device parameters of the N virtual machines on the virtualization management platform, correspondingly generates matched serial device parameter files in the N virtual machines respectively, sends license requests to the virtualization management platform through information interaction channels communicated with the inside of the virtualization platform, responds to the virtualization management platform according to the currently recorded license states of the virtual machines after the requests are received, then the virtual machines execute corresponding license actions and return results to the virtualization management platform for back display, wherein the two states of the virtual machines license are PACKAGE LICENSE states formed by virtual machines with the same functional requirements and individual license states formed by virtual machines with different functional requirements.
2. The virtualization management platform of claim 1, wherein the virtualization management platform further defines a virtual machine state to which No License has been assigned as a No License state.
3. A method implemented by the virtualization management platform of claim 1, characterized by the steps of:
If the virtual machine PACKAGE LICENSE is uniformly managed by adopting the state of the virtual machine PACKAGE LICENSE when the virtual machines with the same management function requirements are managed by the virtualization management platform, the implementation method is as follows:
step 1, generating PACKAGE LICENSE with a certain resource limit according to the self demand of the virtual machine and the total amount of platform resources;
step 2, distributing PACKAGE LICENSE to the virtual machine according to the requirement, limited by the license with certain resource limitation,
If the virtual machines with different management function requirements of the virtualization management platform are managed by adopting states of the virtual machines Individual License, the implementation method is as follows:
step 1, applying N Individual license for N virtual machines correspondingly, and starting the virtual machines;
And step 2, distributing Individual license to the virtual machine through a virtualization management platform.
4. A method according to claim 3, characterized in that: the virtual machine state which is not allocated with license currently is defined as NoLicense state by the management of the virtualization management platform, and management is performed.
5. A method according to claim 3, characterized in that: by updating PACKAGE LICENSE of the platform, the virtual machines that have been assigned PACKAGE LICENSE are uniformly updated, so that the virtual machines license in PACKAGELICENSE state are uniformly updated in batches.
6. A method according to claim 3, characterized in that: and checking license states distributed by all virtual machines in the platform through the virtualization management platform.
7. A method according to claim 3, characterized in that: the PACKAGELICENSE has resource limitations and is shared for use by multiple virtual machines.
CN201911141172.XA 2019-11-20 2019-11-20 Virtualization management platform and implementation method Active CN112925604B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911141172.XA CN112925604B (en) 2019-11-20 2019-11-20 Virtualization management platform and implementation method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911141172.XA CN112925604B (en) 2019-11-20 2019-11-20 Virtualization management platform and implementation method

Publications (2)

Publication Number Publication Date
CN112925604A CN112925604A (en) 2021-06-08
CN112925604B true CN112925604B (en) 2024-04-19

Family

ID=76160724

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911141172.XA Active CN112925604B (en) 2019-11-20 2019-11-20 Virtualization management platform and implementation method

Country Status (1)

Country Link
CN (1) CN112925604B (en)

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101754466A (en) * 2008-12-10 2010-06-23 运软网络科技(上海)有限公司 Mobile virtualization base installation and mobile virtualization base platform
CN103207965A (en) * 2013-03-13 2013-07-17 杭州华三通信技术有限公司 Method and device for License authentication in virtual environment
CN103257683A (en) * 2013-05-07 2013-08-21 华为技术有限公司 Method and device of cloud calculation service expansion and contraction
US8667500B1 (en) * 2006-10-17 2014-03-04 Vmware, Inc. Use of dynamic entitlement and adaptive threshold for cluster process balancing
WO2014138148A2 (en) * 2013-03-06 2014-09-12 Siemens Aktiengesellschaft File based license management system in virtualization environment
CN104092661A (en) * 2014-06-10 2014-10-08 深圳市深信服电子科技有限公司 Serial port communication method and apparatus of virtual machines
CN104111863A (en) * 2014-07-17 2014-10-22 湖南昇云科技有限公司 Method and system for managing virtual machines in different virtual platforms
CN105577381A (en) * 2014-10-24 2016-05-11 中兴通讯股份有限公司 License management method and device under virtualization
US9697019B1 (en) * 2006-10-17 2017-07-04 Manageiq, Inc. Adapt a virtual machine to comply with system enforced policies and derive an optimized variant of the adapted virtual machine
CN108255598A (en) * 2016-12-28 2018-07-06 华耀(中国)科技有限公司 The virtual management platform resource distribution system and method for performance guarantee
CN109257201A (en) * 2017-07-14 2019-01-22 华为技术有限公司 A kind of sending method and device of License
CN109933959A (en) * 2017-12-19 2019-06-25 华为技术有限公司 A kind of licence control method and relevant device

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8667500B1 (en) * 2006-10-17 2014-03-04 Vmware, Inc. Use of dynamic entitlement and adaptive threshold for cluster process balancing
US9697019B1 (en) * 2006-10-17 2017-07-04 Manageiq, Inc. Adapt a virtual machine to comply with system enforced policies and derive an optimized variant of the adapted virtual machine
CN101754466A (en) * 2008-12-10 2010-06-23 运软网络科技(上海)有限公司 Mobile virtualization base installation and mobile virtualization base platform
WO2014138148A2 (en) * 2013-03-06 2014-09-12 Siemens Aktiengesellschaft File based license management system in virtualization environment
CN103207965A (en) * 2013-03-13 2013-07-17 杭州华三通信技术有限公司 Method and device for License authentication in virtual environment
CN103257683A (en) * 2013-05-07 2013-08-21 华为技术有限公司 Method and device of cloud calculation service expansion and contraction
CN104092661A (en) * 2014-06-10 2014-10-08 深圳市深信服电子科技有限公司 Serial port communication method and apparatus of virtual machines
CN104111863A (en) * 2014-07-17 2014-10-22 湖南昇云科技有限公司 Method and system for managing virtual machines in different virtual platforms
CN105577381A (en) * 2014-10-24 2016-05-11 中兴通讯股份有限公司 License management method and device under virtualization
CN108255598A (en) * 2016-12-28 2018-07-06 华耀(中国)科技有限公司 The virtual management platform resource distribution system and method for performance guarantee
CN109257201A (en) * 2017-07-14 2019-01-22 华为技术有限公司 A kind of sending method and device of License
CN109933959A (en) * 2017-12-19 2019-06-25 华为技术有限公司 A kind of licence control method and relevant device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"云环境下的绿色服务组合方法研究";包若;《中国优秀硕士学位论文全文数据库信息科技辑》;全文 *

Also Published As

Publication number Publication date
CN112925604A (en) 2021-06-08

Similar Documents

Publication Publication Date Title
CN108536519B (en) Method for automatically building Kubernetes main node and terminal equipment
US10176019B2 (en) Dynamic management of computing platform resources
CN102571698B (en) Access authority control method, system and device for virtual machine
KR101116615B1 (en) Resource management system and method for applications and threads in JAVA Virtual Machine
KR101253560B1 (en) System for managing a virtualization solution and Apparatus and Method for managing the same
US11388224B2 (en) Method for managing user information of application, device, and system
CN107291456B (en) Multi-screen display control method and system
US10223170B2 (en) Dynamic management of computing platform resources
US11336521B2 (en) Acceleration resource scheduling method and apparatus, and acceleration system
CN102317907B (en) Working environment generation system, working environment generation method, and storage medium
US20110004687A1 (en) Information processing apparatus, information processing system, setting program transmission method and server setting program
CN110489126B (en) Compiling task execution method and device, storage medium and electronic device
US10666573B2 (en) Dynamic management of computing platform resources
WO2018040525A1 (en) Method, device, and equipment for processing resource pool
CN109995814B (en) Cloud host resource migration method and device, communication equipment and storage medium
KR102140730B1 (en) Method and system for providing develop environment of deep learning based gpu
EP3358795B1 (en) Method and apparatus for allocating a virtual resource in network functions virtualization (nfv) network
CN104714823A (en) New mainframe configuration method based on OpenStack
US11500685B2 (en) Mixed instance catalogs
JP5606476B2 (en) Client management system, client management method and program
CN112925604B (en) Virtualization management platform and implementation method
KR20090070933A (en) Device and method for hosting service using virtual machine
WO2018103372A1 (en) Driver management method and host machine
US10771430B1 (en) Dynamic resource configuration system and method for distributed computing environments
CN108287762B (en) Distributed computing interactive mode use resource optimization method and computer equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant