CN108279967A - A kind of virtual machine and container mixed scheduling method - Google Patents

A kind of virtual machine and container mixed scheduling method Download PDF

Info

Publication number
CN108279967A
CN108279967A CN201711016482.XA CN201711016482A CN108279967A CN 108279967 A CN108279967 A CN 108279967A CN 201711016482 A CN201711016482 A CN 201711016482A CN 108279967 A CN108279967 A CN 108279967A
Authority
CN
China
Prior art keywords
virtual machine
container
configuration
cpu
strategy
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.)
Withdrawn
Application number
CN201711016482.XA
Other languages
Chinese (zh)
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.)
G Cloud Technology Co Ltd
Original Assignee
G Cloud 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 G Cloud Technology Co Ltd filed Critical G Cloud Technology Co Ltd
Priority to CN201711016482.XA priority Critical patent/CN108279967A/en
Publication of CN108279967A publication Critical patent/CN108279967A/en
Withdrawn legal-status Critical Current

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/45562Creating, deleting, cloning virtual machine instances
    • 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/45587Isolation or security of virtual machine instances

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 present invention relates to field of cloud computer technology, a kind of virtual machine and container mixed scheduling method are particularly related to.The method of the invention be created container as the built-in application of virtual machine on a virtual machine, meanwhile, assign container and virtual machine elasticity configuration strategy;The configuration or migration of container and virtual machine are created according to elastic configuration strategy.The method of the present invention creates container on a virtual machine, as the built-in application of virtual machine, that is, has ensured the safety problem between container and virtual machine, and combine the flexible scheduling strategy of virtual machine, has improved physical resource utilization rate;Container availability can be improved in the method for the present invention, using the flexible scheduling of virtual machine avoid container transition process halting problem.

Description

A kind of virtual machine and container mixed scheduling method
Technical field
The present invention relates to field of cloud computer technology, a kind of virtual machine and container mixed scheduling method are particularly related to.
Background technology
It had been considered as once virtualization technology by the container technique of representative of Docker with the development of cloud computing technology Substitute, however be not implacable between both technologies.With the gradual maturation of container technique, container and virtual machine And it deposits and has become a kind of certainty.Since sex chromosome mosaicism is isolated in container itself, many public cloud producers are currently to create container Inside virtual machine, other virtual machines are impacted for completely cutting off.There are also producers to create container and virtual machine simultaneously The utilization rate of physical resource is improved with this on same physical server, there are following drawbacks for these modes:
(1) more stiff, container is created mode on a virtual machine by public cloud, lacks scheduling, only it is simple for Family provides container service, can not effectively improve physical resource utilization rate.
(2) safety is poor, and establishment will necessarily influence each other in same physical server simultaneously for container and virtual machine, especially Be container isolation it is poor, the case where causing to fight for resources of virtual machine.
For this reason, it may be necessary to which a kind of scheduling strategy, uses virtual machine and container and improves object while making user safe Manage the solution of resource utilization.
Invention content
Present invention solves the technical problem that being to provide a kind of virtual machine and container mixed scheduling method, conventional method is solved Existing deficiency provides one kind to the user while can be safe and using virtual machine and container and improves physical resource utilization The solution of rate.
The present invention solve above-mentioned technical problem technical solution be:
The method be created container as the built-in application of virtual machine on a virtual machine, meanwhile, assign container and void Quasi- machine elasticity configuration strategy;The configuration or migration of container and virtual machine are created according to elastic configuration strategy.
The method specifically comprises the following steps:
Step 1:Virtual machine elasticity configuration strategy is set, container elasticity configuration strategy is set;
Step 2:Create carrier of the virtual machine as container, configuration selection resilience strategy;
Step 3:Container group is created on a virtual machine, container resilience strategy is selected;
Step 4:Physical machine load where monitoring virtual machine, according to virtual machine elasticity configuration strategy, dynamic adjusts virtual machine Configuration migrates virtual machine to other physical nodes;
Step 5:Virtual machine load is monitored, according to container elasticity configuration strategy, dynamic adjusts container and runs quantity.
The container, container provide the running space of isolation for application program:In each container solely comprising one The whole user environment space enjoyed, and the variation in a container does not interfere with the running environment of other containers;In order to reach To this effect, the mechanism that container technique has used a series of system level is such as carried out using Linux namespaces Space is isolated, and determines which file container can access by the mount point of file system, is determined by cgroups each Container can utilize how many resource.Same system kernel is shared between this outer container, in this way when the same library is by multiple containers In use, the service efficiency of memory can get a promotion.
The carrier of the container, i.e. container create virtual machine institute on an operating system, be equal with other virtual machines, appearance Device is intended only as the special applications of virtual machine to treat;
The container group refers to the set of multiple containers, can single application cluster container, can also be multiple, create When can limit container group inner chamber minimax number.
The setting virtual machine elasticity configuration strategy, refers to the utilization rate tune according to place physical server CPU, memory The strategy of whole virtual machine CPU, memory size;
When creating virtual machine, setting virtual machine minimum CPU, minimum memory and maximum CPU, maximum memory;Work as physical machine When cpu busy percentage is less than 30%, virtual machine CPU sizes add 1, and data are configurable;It is empty when physical machine memory usage is more than 80% Quasi- machine memory size subtracts 2G, and data are configurable;
It, can be in a manner of preferential configuration emigration virtual machine when encountering reduction virtual machine configuration;That is object where current virtual machine Reason server load it is higher need reduce virtual machine configuration when, can check whether that other physical servers have enough resources to carry It is used for existing virtual machine, migration monitoring mode again may be used if having.
The container elasticity configuration strategy, mainly determines according to the configuring condition of virtual machine, is creating container group When can be arranged that container group is minimum and maximum quantity, currently run quantity;When virtual machine configuration increases, appropriate increase is held Device quantity suitably reduces number of containers when virtual machine configuration reduces;
If it is compute-intensive applications, the requirement for CPU is with regard to relatively high;After virtual machine CPU increases, increase container Numerical value the case where just should suitably reducing, avoid that virtual machine configuration is caused to overload;
The compute-intensive applications, i.e. programming system it is most of calculate, logic judgment, cycle cause CPU to account for With the very high application of rate.
The method of the present invention creates container on a virtual machine, as the built-in application of virtual machine, that is, has ensured container and void Safety problem between quasi- machine, and the flexible scheduling strategy of virtual machine is combined, improve physical resource utilization rate;Side of the present invention Method improve container availability, using the flexible scheduling of virtual machine avoid container transition process halting problem.
Description of the drawings
The following further describes the present invention with reference to the drawings:
Fig. 1 is the flow chart of the present invention;
Fig. 2 is implementation framework figure of the present invention.
Specific implementation mode
To keep the purpose, technical scheme and advantage of this discovery clearer, below in conjunction with attached drawing and with actual implementation case Example is made further to explain in detail, and as shown in Figure 1, 2, specific implementation process is as follows:
1, virtual machine elasticity configuration strategy is set, container elasticity configuration strategy is set;
The setting virtual machine elasticity configuration strategy refers to the strategy for adjusting virtual machine CPU, memory size, is creating When virtual machine, virtual machine resilience strategy is arranged, mainly in setting virtual machine minimum CPU, minimum memory and maximum CPU, maximum memory According to place physical server load be adjusted, such as physical machine cpu busy percentage be less than 30% when, virtual machine CPU sizes add 1, data are configurable;For example physical machine memory usage, when being more than 80%, virutal machine memory size subtracts 2G, and data are configurable.Institute Some configuration strategies are adjusted all in accordance with the utilization rate of physical services CPU, memory, are finally to improve physical resource profit It can be in a manner of preferential configuration emigration virtual machine when encountering reduction virtual machine configuration with rate.
Physical server load is higher where the preferential configuration emigration virtual machine strategy, i.e. current virtual machine needs to drop When low virtual machine configuration, it can check whether that other physical servers have enough resources to provide existing virtual machine and use, if having Migration monitoring mode again then may be used.
Arrange parameter is as follows:
/*
* name String are
* type application types (template type) String cluster (application cluster) | deploy (application deployment) is
* description remarks String is no
* cpu number int of instance.cpu exemplary configurations
* instance.memory exemplary configurations memory size (M) int
* type string Local of instance.attachVolumeType carries cloud disk | RBD
* instance.instanceStorageType storage classes int 0 | 1 | 2
* instance.isFloating virtual machines floating ip binds int (0,1)
* it is no to bind int (0,1) by loadbalance.isFloating floatings ip
* loadbalance.type load balancing type string " new "
* scaling_policy.policyType extended modes String scaleOutFirst are laterally preferential, ScaleUpFirst is longitudinally preferential
#scaleout transverse directions #scaleup is longitudinal
* scaling_policy.minInst minimums virtual machine number int
* scaling_policy.maxInst maximums virtual machine number int
* scaling_policy.cpu_resize extends cpu check figures int every time
* scaling_policy.max_cpu extends cpu maximum values int
* each exented memory size (G) int of scaling_policy.mem_resize
* scaling_policy.max_mem exented memories maximum value (G) int
* alarmTypelist [n] expansion condition strategy List<String>pu_util”,”disk_io_read”,” disk_io_write”
*/
The container elasticity configuration strategy, mainly determines according to the configuring condition of virtual machine, is creating container group When can be arranged that container group is minimum and maximum quantity, currently run quantity, it is appropriate to increase appearance when virtual machine configuration increases Device quantity suitably reduces number of containers when virtual machine configuration reduces.This block needs the operation run according to container to determine, Such as if it is compute-intensive applications, the requirement for CPU after this when of virtual machine CPU increases, increases and holds with regard to relatively high The case where numerical value of device just should suitably reduce, avoid that virtual machine configuration is caused to overload.
2, carrier of the virtual machine as container, configuration selection resilience strategy are created;
3, container group is created on a virtual machine, selects container resilience strategy;
Initialization container group inner pressurd vessel quantity, is arranged container scheduling strategy, and setting container expansion reduces strategy:
4, physical machine load where monitoring virtual machine, according to virtual machine elasticity configuration strategy, dynamic adjusts virtual machine configuration Or virtual machine is migrated to other physical nodes;
5, monitoring virtual machine load, according to container elasticity configuration strategy, dynamic adjusts container and runs quantity.
{ region_id }/monitor_resource/info.do interfaces are called to obtain physical load situation

Claims (6)

1. a kind of virtual machine and container mixed scheduling method, it is characterised in that:The method is using container as in virtual machine It sets using establishment on a virtual machine, meanwhile, assign container and virtual machine elasticity configuration strategy;It is created and is held according to elastic configuration strategy The configuration or migration of device and virtual machine.
2. according to the method described in claim 1, it is characterized in that:The method specifically comprises the following steps:
Step 1:Virtual machine elasticity configuration strategy is set, container elasticity configuration strategy is set;
Step 2:Create carrier of the virtual machine as container, configuration selection resilience strategy;
Step 3:Container group is created on a virtual machine, container resilience strategy is selected;
Step 4:Physical machine load where monitoring virtual machine, according to virtual machine elasticity configuration strategy, dynamic adjusts virtual machine configuration Or virtual machine is migrated to other physical nodes;
Step 5:Virtual machine load is monitored, according to container elasticity configuration strategy, dynamic adjusts container and runs quantity.
3. according to the method described in claim 2, it is characterized in that:
The container, container provide the running space of isolation for application program:It is exclusively enjoyed comprising one in each container Whole user environment space, and the variation in a container does not interfere with the running environment of other containers;
The carrier of the container, i.e. container create virtual machine institute on an operating system, be equal with other virtual machines, container It is to be treated as the special applications of virtual machine;
The container group refers to the set of multiple containers, can single application cluster container, can also be multiple, establishment when Time can limit container group inner chamber minimax number.
4. according to the method described in claim 2, it is characterized in that:
The setting virtual machine elasticity configuration strategy refers to adjusting void according to the utilization rate of place physical server CPU, memory The strategy of quasi- machine CPU, memory size;
When creating virtual machine, setting virtual machine minimum CPU, minimum memory and maximum CPU, maximum memory;When physical machine CPU profits When being less than 30% with rate, virtual machine CPU sizes add 1, and data are configurable;When physical machine memory usage is more than 80%, virtual machine Memory size subtracts 2G, and data are configurable;
It, can be in a manner of preferential configuration emigration virtual machine when encountering reduction virtual machine configuration;Physics clothes i.e. where current virtual machine Business device load is higher when needing to reduce virtual machine configuration, and it is existing can to check whether that other physical servers have enough resource to provide There is virtual machine use, migration monitoring mode again may be used if having.
5. according to the method described in claim 3, it is characterized in that:
The setting virtual machine elasticity configuration strategy refers to adjusting void according to the utilization rate of place physical server CPU, memory The strategy of quasi- machine CPU, memory size;
When creating virtual machine, setting virtual machine minimum CPU, minimum memory and maximum CPU, maximum memory;When physical machine CPU profits When being less than 30% with rate, virtual machine CPU sizes add 1, and data are configurable;When physical machine memory usage is more than 80%, virtual machine Memory size subtracts 2G, and data are configurable;
It, can be in a manner of preferential configuration emigration virtual machine when encountering reduction virtual machine configuration;Physics clothes i.e. where current virtual machine Business device load is higher when needing to reduce virtual machine configuration, and it is existing can to check whether that other physical servers have enough resource to provide There is virtual machine use, migration monitoring mode again may be used if having.
6. method according to any one of claims 1 to 5, it is characterised in that:
The container elasticity configuration strategy, mainly determines according to the configuring condition of virtual machine, create container group when Container group minimum and maximum quantity can be arranged in time, currently run quantity;It is appropriate to increase container number when virtual machine configuration increases Amount, when virtual machine configuration reduces, suitably reduces number of containers;
If it is compute-intensive applications, the requirement for CPU is with regard to relatively high;After virtual machine CPU increases, increase the number of container The case where value just should suitably reduce, avoid that virtual machine configuration is caused to overload;
The compute-intensive applications, i.e. programming system it is most of calculate, logic judgment, cycle lead to CPU usage Very high application.
CN201711016482.XA 2017-10-25 2017-10-25 A kind of virtual machine and container mixed scheduling method Withdrawn CN108279967A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711016482.XA CN108279967A (en) 2017-10-25 2017-10-25 A kind of virtual machine and container mixed scheduling method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711016482.XA CN108279967A (en) 2017-10-25 2017-10-25 A kind of virtual machine and container mixed scheduling method

Publications (1)

Publication Number Publication Date
CN108279967A true CN108279967A (en) 2018-07-13

Family

ID=62801326

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711016482.XA Withdrawn CN108279967A (en) 2017-10-25 2017-10-25 A kind of virtual machine and container mixed scheduling method

Country Status (1)

Country Link
CN (1) CN108279967A (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109213561A (en) * 2018-09-14 2019-01-15 珠海国芯云科技有限公司 The equipment scheduling method and device of virtual desktop based on container
CN109697105A (en) * 2018-12-11 2019-04-30 广东石油化工学院 A kind of container cloud environment physical machine selection method and its system, virtual resource configuration method and moving method
CN110874468A (en) * 2018-08-31 2020-03-10 华为技术有限公司 Application program safety protection method and related equipment
CN111124660A (en) * 2018-11-01 2020-05-08 百度在线网络技术(北京)有限公司 Method and device for allocating idle resources in virtual machine

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102096461B (en) * 2011-01-13 2013-06-19 浙江大学 Energy-saving method of cloud data center based on virtual machine migration and load perception integration
CN103885812A (en) * 2012-12-21 2014-06-25 华为技术有限公司 Virtual machine specification adjustment method and virtual machine specification adjustment device
CN107209682A (en) * 2014-12-05 2017-09-26 亚马逊技术有限公司 The automatic management of resource adjustment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102096461B (en) * 2011-01-13 2013-06-19 浙江大学 Energy-saving method of cloud data center based on virtual machine migration and load perception integration
CN103885812A (en) * 2012-12-21 2014-06-25 华为技术有限公司 Virtual machine specification adjustment method and virtual machine specification adjustment device
CN107209682A (en) * 2014-12-05 2017-09-26 亚马逊技术有限公司 The automatic management of resource adjustment

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110874468A (en) * 2018-08-31 2020-03-10 华为技术有限公司 Application program safety protection method and related equipment
CN110874468B (en) * 2018-08-31 2024-02-09 华为技术有限公司 Application program security protection method and related equipment
CN109213561A (en) * 2018-09-14 2019-01-15 珠海国芯云科技有限公司 The equipment scheduling method and device of virtual desktop based on container
CN111124660A (en) * 2018-11-01 2020-05-08 百度在线网络技术(北京)有限公司 Method and device for allocating idle resources in virtual machine
CN111124660B (en) * 2018-11-01 2024-01-05 百度在线网络技术(北京)有限公司 Method and device for allocating idle resources in virtual machine
CN109697105A (en) * 2018-12-11 2019-04-30 广东石油化工学院 A kind of container cloud environment physical machine selection method and its system, virtual resource configuration method and moving method

Similar Documents

Publication Publication Date Title
US11740921B2 (en) Coordinated container scheduling for improved resource allocation in virtual computing environment
US9268394B2 (en) Virtualized application power budgeting
JP4084765B2 (en) How to automatically allocate computing resources
US8762999B2 (en) Guest-initiated resource allocation request based on comparison of host hardware information and projected workload requirement
US8694679B2 (en) Control device, method and program for deploying virtual machine
CN108279967A (en) A kind of virtual machine and container mixed scheduling method
CN110098946B (en) Method and device for deploying virtualized network element equipment
US20210027401A1 (en) Processes and systems that determine sustainability of a virtual infrastructure of a distributed computing system
US9032180B2 (en) Managing CPU resources for high availability micro-partitions
CN111078363A (en) NUMA node scheduling method, device, equipment and medium for virtual machine
US9244825B2 (en) Managing CPU resources for high availability micro-partitions
US20200019426A1 (en) Techniques for container scheduling in a virtual environment
US11012316B2 (en) Methods and apparatus to generate and manage workload domains in virtual server racks
US9043575B2 (en) Managing CPU resources for high availability micro-partitions
US10866738B2 (en) Performance attributes for memory
CN103106112A (en) Method and device based on maximum load and used for load balancing scheduling
US11561843B2 (en) Automated performance tuning using workload profiling in a distributed computing environment
CN105208111A (en) Information processing method and physical machine
US10157066B2 (en) Method for optimizing performance of computationally intensive applications
CN107766122B (en) Method and device for setting available memory space of host machine
CN103562852B (en) A kind of method and apparatus for ensureing cloud application procedure service quality
CN109002347A (en) A kind of virutal machine memory distribution method, apparatus and system
CN114090257B (en) Scheduling method and device of virtual machine, storage medium and equipment
KR102214782B1 (en) Hardware Resource Classification and Allocation Method for the Virtual Machine Performance Optimization
WO2024220268A1 (en) Mapping virtual processor cores to heterogeneous physical processor cores

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
WW01 Invention patent application withdrawn after publication

Application publication date: 20180713

WW01 Invention patent application withdrawn after publication