CN117170804A - Virtualized container management platform and method - Google Patents
Virtualized container management platform and method Download PDFInfo
- Publication number
- CN117170804A CN117170804A CN202311099561.7A CN202311099561A CN117170804A CN 117170804 A CN117170804 A CN 117170804A CN 202311099561 A CN202311099561 A CN 202311099561A CN 117170804 A CN117170804 A CN 117170804A
- Authority
- CN
- China
- Prior art keywords
- container
- creation
- module
- management
- unit
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 19
- 238000012217 deletion Methods 0.000 claims description 21
- 230000037430 deletion Effects 0.000 claims description 21
- 238000012544 monitoring process Methods 0.000 claims description 14
- 230000036541 health Effects 0.000 claims description 9
- 238000004458 analytical method Methods 0.000 claims description 8
- 241000322338 Loeseliastrum Species 0.000 claims description 7
- 238000013475 authorization Methods 0.000 claims description 3
- 230000009467 reduction Effects 0.000 claims description 2
- 238000007726 management method Methods 0.000 abstract description 96
- 230000006870 function Effects 0.000 description 12
- 238000005516 engineering process Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 8
- 230000000694 effects Effects 0.000 description 6
- 240000007087 Apium graveolens Species 0.000 description 3
- 235000015849 Apium graveolens Dulce Group Nutrition 0.000 description 3
- 235000010591 Appio Nutrition 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 230000008602 contraction Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 241000282326 Felis catus Species 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 239000000523 sample Substances 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a virtualized container management platform and a method, which belong to the field of network management and comprise the following steps: the external access layer is used for receiving a container request instruction and generating a container creation instruction according to the received container request instruction; the standard business layer is used for carrying out container creation according to the container creation instruction to obtain an creation result; and the parallel platform layer is used for carrying out container management on the creation result to obtain a container management result. The application builds a rapid and stable elastic telescopic container management platform, reduces delivery time, risk, infrastructure cost and labor cost, and improves the usability and the scalability of the platform.
Description
Technical Field
The application mainly relates to the technical field of network management, in particular to a virtualized container management platform and a virtualized container management method.
Background
The existing virtualized container management platform is built based on the traditional k8s, the starting speed is low, the elasticity is poor, the container access mode is single, the access mode cannot be exposed to the public network or a student end, the access mode can only be set for access, the dynamic domain name is not supported, ssh and nc access are not carried out, meanwhile, the hardware resources of a machine in the traditional mode are required to be determined in advance, the subsequent capacity expansion is difficult, and the utilization of idle resources is poor.
Disclosure of Invention
The application aims to solve the technical problem of providing a virtualized container management platform and a virtualized container management method aiming at the defects of the prior art.
The technical scheme for solving the technical problems is as follows: a virtualized container management platform, comprising: for the outer access layer, standard service layer and parallel platform layer,
the external access layer is used for receiving a container request instruction and generating a container creation instruction according to the received container request instruction;
the standard business layer is used for carrying out container creation according to the container creation instruction to obtain a creation result;
and the parallel platform layer is used for carrying out container management on the creation result to obtain a container management result.
The other technical scheme for solving the technical problems is as follows: a virtualized container management method comprising the steps of:
receiving a container request instruction, and generating a container creation instruction according to the received container request instruction;
performing container creation according to the container creation instruction to obtain a creation result;
and carrying out container management on the creation result to obtain a container management result.
The beneficial effects of the application are as follows: by receiving the container request instruction, generating a container creation instruction according to the received container request instruction, creating a container according to the container creation instruction to obtain a creation result, and managing the creation result to obtain a container management result, a quick and stable elastic telescopic container management platform is built, the delivery time, risk, infrastructure cost and labor cost are reduced, and the availability and the retractility of the platform are improved.
Drawings
FIG. 1 is a block diagram of a virtualized container management platform in accordance with an embodiment of the application;
FIG. 2 is a block diagram of a virtualized container management platform in accordance with an embodiment of the application;
fig. 3 is a flow chart of a container scheduling method according to an embodiment of the application.
Detailed Description
The principles and features of the present application are described below with reference to the drawings, the examples are illustrated for the purpose of illustrating the application and are not to be construed as limiting the scope of the application.
FIG. 1 is a block diagram illustrating a virtualized container management platform according to an embodiment of the application.
As shown in fig. 1, a virtualized container management platform includes: for the outer access layer, standard service layer and parallel platform layer,
the external access layer is used for receiving a container request instruction and generating a container creation instruction according to the received container request instruction;
the standard business layer is used for carrying out container creation according to the container creation instruction to obtain a creation result;
and the parallel platform layer is used for carrying out container management on the creation result to obtain a container management result.
It should be understood that the external access layer is responsible for receiving the operations of container creation, destruction, system configuration management and the like (i.e. the container request instruction), and the management background and the API SDK service are realized by adopting the load balancing +Django +Celery technology.
Specifically, the standard service layer is responsible for service functions such as container scheduling, mirror image management, mirror image cache creation, container access (dynamic domain name, forwarding agent, websocket, ssh) and the like, uses kubourants sdk technology to realize container issuing service, uses nginx+etcd+coredns+websocket to realize dynamic domain name access and websocket access service, and uses netcat technology to realize forwarding agent and ssh service.
It should be appreciated that the parallel platform layer is responsible for underlying container network creation, container creation, storage of container images, and storage of business data.
In the above embodiment, the container creation instruction is generated according to the received container request instruction by receiving the container request instruction, the container creation is performed according to the container creation instruction to obtain the creation result, and the container management is performed on the creation result to obtain the container management result, so that a rapid and stable elastic telescopic container management platform is created, the delivery time, the risk, the infrastructure cost and the labor cost are reduced, and the availability and the scalability of the platform are improved.
Alternatively, as an embodiment of the present application, as shown in fig. 1 and 2, the external access layer includes a web portal management module, a receiving module, a task management module and a system configuration module,
the portal management module is used for displaying and managing the container list, the mirror image list and the port list;
the receiving module is used for receiving a container request instruction and sending the container request instruction to the task management module, wherein the container request instruction comprises a container creation request instruction and a container deletion request instruction;
the task management module is used for generating a container creation instruction according to the container creation request instruction and/or the container deletion request instruction;
the system configuration module is used for configuring the basic information of the container.
It should be appreciated that task management (i.e., task management module) involves container creation all state processing (creation success, creation failure), and that system configuration (i.e., system configuration module) includes mirroring and container port configuration.
Specifically, the web portal (i.e. a portal management module) is used for managing background page display, and comprises a container list, a mirror list and a port list; the api module (i.e. receiving module) is responsible for receiving the request call of creating and deleting the container initiated by the user terminal and transmitting the information to the task management module through the queue; task management (i.e., a task management module) receives asynchronous tasks through a queue and initiates a business layer container management module to create scheduling tasks; system configuration (i.e., system configuration module) is responsible for system initialization stage basic information (i.e., container basic information) configuration.
In the above embodiment, by receiving the container request instruction and generating the container creation instruction according to the received container request instruction, a quick and stable flexible container management platform is created, the delivery time, risk, infrastructure cost and labor cost are reduced, and the availability and flexibility of the platform are improved.
Optionally, as an embodiment of the present application, the standard service layer includes a public cloud access module, a private cloud access module, and a service routing module, and the container creation instruction includes a public cloud creation instruction and a private cloud creation instruction;
the public cloud access module is used for receiving the public cloud creation instruction, generating public cloud creation information according to the public cloud creation instruction, and sending the public cloud creation information to the service routing module;
the private cloud access module is used for receiving the private cloud creation instruction, generating private cloud creation information according to the private cloud creation instruction, and sending the private cloud creation information to the service routing module;
and the service routing module is used for carrying out container creation according to the public cloud creation information and/or the private cloud creation information to obtain a creation result.
It should be understood that the public cloud access module and the private cloud access module are both mainly responsible for receiving access of service traffic.
In the embodiment, the container is created according to the container creation instruction to obtain the creation result, so that the effects of elastic expansion and simplicity and easiness in use can be achieved, meanwhile, the container issuing speed is high, rich container access modes and private cloud deployment are supported, a rapid and stable elastic expansion container management platform is built, and the usability and the flexibility of the platform are improved.
Optionally, as an embodiment of the present application, the public cloud access module includes a public cloud kube-apiserver unit, a public cloud etcd unit, a public cloud coredns unit and a public cloud nginx unit,
the public cloud kube-apiserver unit is used for managing the public cloud creation instruction;
the public cloud etcd unit is used for storing all public cloud dynamic domain name information and all public cloud intranet ip information;
the public cloud coredns unit is used for analyzing all public cloud dynamic domain names and all public cloud intranet ip information to obtain a public cloud analysis result;
the public cloud nginx unit is used for receiving public cloud dynamic domain name access flow, obtaining public cloud intranet address information according to the public cloud analysis result, and sending the public cloud intranet address information and the public cloud dynamic domain name access flow to the service routing module.
It should be understood that kube-apiserver (i.e., public cloud kube-apiserver unit) accepts access of traffic such as container creation deletion and the like and distributes the access to the parallel platform layer; etcd+coredns+nginx (i.e., public cloud etcd units, public cloud coredns units, and public cloud nginx units) is responsible for accepting access traffic for a container.
Specifically, kube-apiserver (namely public cloud kube-apiserver unit) is responsible for all traffic processing work of operations related to containers and plays a role of an api gateway; etcd (i.e. public cloud etcd unit) is in charge of storing dynamic domain name and intranet ip corresponding information of the whole cluster; coredns (i.e., public cloud coredns units) responsible for resolving dynamic domain name records and intranet ips created within etcd (i.e., public cloud etcd units); the nginx (i.e. public cloud ginx unit) is responsible for receiving the dynamic domain name access flow, resolving and taking the real intranet address according to coredns (i.e. public cloud coredns unit), and forwarding to intranet container service.
In the above embodiment, public cloud creation information is generated according to the public cloud creation instruction, so that the api gateway can be used, the effects of elasticity, simplicity and easiness in use can be achieved, meanwhile, the container issuing speed is high, rich container access modes and private cloud deployment are supported, a quick and stable elastic telescopic container management platform is built, and the usability and the stretchability of the platform are improved.
Optionally, as an embodiment of the present application, the private cloud access module includes a private cloud kube-apiserver unit, a private cloud etcd unit, a private cloud coredns unit and a private cloud nginx unit,
the private cloud kube-apiserver unit is used for managing the private cloud creation instruction;
the private cloud etcd unit is used for storing all private cloud dynamic domain name information and all private cloud intranet ip information;
the private cloud coredns unit is used for resolving all the private cloud dynamic domain names and all the private cloud intranet ip information to obtain a private cloud resolving result;
the private cloud ginx unit is used for receiving private cloud dynamic domain name access flow, obtaining private cloud intranet address information according to the private cloud analysis result, and sending the private cloud intranet address information and the private cloud dynamic domain name access flow to the service routing module.
It should be understood that kube-apiserver (i.e., private cloud kube-apiserver unit) accepts access of traffic such as container creation deletion and distribution to the parallel platform layer; etcd+coredns+nginx (i.e., private cloud etcd units, private cloud coredns units, and private cloud nginx units) is responsible for accepting access traffic for a container.
Specifically, kube-apiserver (namely a private cloud kube-apiserver unit) is responsible for all traffic processing work related to the container and plays a role of an api gateway; etcd (namely a private cloud etcd unit) is in charge of storing dynamic domain names and intranet ip corresponding information of the whole cluster; coredns (i.e., private cloud coredns units) responsible for resolving dynamic domain name records and intranet ips created within etcd (i.e., private cloud etcd units); the nginx (i.e. private cloud ginx unit) is responsible for receiving the dynamic domain name access traffic, resolving and taking the real intranet address according to coredns (i.e. private cloud coredns unit), and forwarding to intranet container service.
In the embodiment, the private cloud creation information is generated according to the private cloud creation instruction, so that the effects of elasticity, simplicity and easiness in use can be achieved, meanwhile, the container issuing speed is high, and rich container access modes and private cloud deployment are supported.
Optionally, as an embodiment of the present application, the service routing module includes a dynamic domain name unit, a forwarding agent unit, a websocket access unit, a ssh access unit, a container management unit, a mirror management unit, and a node management unit,
the dynamic domain name unit is used for accessing the public cloud creation information and/or the private cloud creation information according to domain name information;
the forwarding agent unit is used for accessing the public cloud creation information and/or the private cloud creation information according to port forwarding information;
the websocket access unit is used for accessing the public cloud creation information and/or the private cloud creation information according to a websocket protocol;
the ssh access unit is used for accessing the public cloud creation information and/or the private cloud creation information according to a ssh protocol;
the container management unit is used for carrying out container creation, container deletion and container log viewing according to the public cloud creation information and/or the private cloud creation information to obtain an initial container;
the image management unit is used for carrying out image creation and image deletion according to the public cloud creation information and/or the private cloud creation information;
the node management unit is used for carrying out node addition and node deletion according to the public cloud creation information and/or the private cloud creation information.
It should be understood that the container management module (i.e., container management unit) includes functions such as container creation, deletion, log viewing, remote linking, etc.; the mirror image management module (namely a mirror image management unit) comprises a mirror image, and a mirror image group creation and deletion function; the dynamic domain name function comprises a creation function and a deletion function of dynamic domain name resolution; the dynamic domain name module (namely dynamic domain name unit) adopts etcd+coredns+nginx to realize the http access function to the container; the forwarding agent and the ssh module (i.e. forwarding agent unit and ssh access unit) are an access mode for implementing the ip agent port of the external network by adopting nc port monitoring technology.
Specifically, container management (i.e., a container management unit) is responsible for processing business logic such as container creation, deletion, log viewing and the like; mirror image management (namely a mirror image management unit) is responsible for the processing of service logic such as creation, deletion and the like of a mirror image; node management (namely a node management unit) is responsible for processing business logic such as node addition and deletion; dynamic domain name (i.e., dynamic domain name unit), an access mode responsible for providing access to container services in the domain name mode; a forwarding agent (i.e., forwarding agent unit), which is responsible for providing a container service access mode for port forwarding access; websocket access (i.e., websocket access unit), which is responsible for providing an access mode of websocket protocol access to container services; ssh access (i.e., ssh access unit), an access mode responsible for providing ssh protocol access to container services.
In the embodiment, the container is created according to the public cloud creation information and/or the private cloud creation information to obtain the creation result, so that a quick and stable elastic telescopic container management platform is created, the delivery time, the risk, the infrastructure cost and the labor cost are reduced, and the availability and the scalability of the platform are improved.
Optionally, as an embodiment of the present application, the parallel platform layer includes a calico module, a k8s server module, a capacity expansion service module, a mirror service module, a redis module, and a mysql module,
the calico module is used for constructing a virtualized network according to the creation result;
the k8s server module is used for constructing a virtual node container according to the creation result;
the capacity expansion service module is used for carrying out node addition, node expansion, node capacity reduction and node deletion on the virtual node container;
the mirror image service module is used for carrying out mirror image storage and mirror image management on the creation result;
the redis module is used for constructing a cache database;
the mysql module is configured to store the creation result in the cache database.
It should be understood that the application adopts serverless kuberents and calico networks and automatic capacity expansion technology to realize elastic expansion and rapid capacity expansion (container memory priority type scheduling and node cloudy probe activity scheduling) of a container platform, and adopts redis+mysql to realize the storage of service data.
Specifically, the calico (i.e. the calico module) is used for network connection before a container, a virtual machine and a host machine, and is a pure three-layer virtualized network solution, each node is regarded as a virtual router, and the Pod on each node is regarded as a terminal device behind the node router and is allocated with an IP address. Each node router generates a routing rule through BGP protocol, thereby realizing communication between Pods on the non-communication nodes; the k8s server (namely a k8s server module) is a virtual node container scheme which improves the resource utilization rate, has elastic expansion and strong isolation, and is charged according to the quantity and is automatic in operation and maintenance; the automatic capacity expansion service (namely a capacity expansion service module) is a cluster expansion service integrating detection and early warning, strategy analysis and automatic capacity expansion, and is mainly responsible for the addition and deletion of k8s node nodes and the capacity expansion and contraction of access load balancing nodes; the mirror image service (namely a mirror image service module) is a Docker mirror image private Registry server and is responsible for storing and managing the mirror image; redis (i.e., redis module) is used as a cache database of the service platform; mysql (i.e., mysql module) is used as a data store for a business platform.
In the embodiment, the container management is performed on the creation result to obtain the container management result, so that the resource utilization rate is improved, and the container has elasticity, strong isolation, metering by volume and operation and maintenance automation.
Optionally, as an embodiment of the present application, the virtualized container management platform further comprises a base resource layer, wherein the base resource layer comprises an object storage module, an HDFS module, a physical server and a virtual server,
the object storage module is used for storing the container management result;
the HDFS module is used for constructing a file storage system;
the entity server is used for carrying out main node management on the container management result;
and the virtual server is used for carrying out node capacity expansion and load balancing management on the container management result.
It should be appreciated that the underlying resource layer is used to store container management results.
It should be understood that the underlying resource layer: the system comprises object storage, HDFS, an entity server and a virtual server which form a basic resource environment bearing platform.
Specifically, the object storage (i.e. the object storage module) is used for storing the mounting storage resources required by the container and backing up the cluster data resource storage; HDFS (i.e., HDFS module), a distributed file storage system, is a highly fault tolerant system suitable for deployment on inexpensive machines. HDFS can provide high throughput data access, well suited for applications on large-scale data sets; the entity server adopts an off-line machine room to build an entity cluster and bears the service of a service main node; and the virtual server adopts an online cloud manufacturer cloud host to provide capacity expansion and load balancing capability for the nodes.
In the embodiment, by storing the container management result, high-throughput data access is provided, and the method is suitable for application on a large-scale data set and is also suitable for being deployed on an inexpensive machine, so that the cost is saved.
Optionally, as an embodiment of the present application, the virtualized container management platform further comprises a common component layer, the common component layer comprises log monitoring, rights control, data warehouse, alarm center, operation record and account management,
the log monitoring is used for collecting container logs from the external access layer, the standard service layer and the parallel platform layer and inquiring the container logs;
the right control is used for logging in the user account and managing the right;
the data warehouse is used for storing historical data, inquiring the historical data and generating a report;
the alarm center is used for obtaining a service health state and a node health state from the external access layer, the standard service layer and the parallel platform layer;
monitoring and analyzing the service health state and the node health state to obtain a monitoring and analyzing result, and alarming the monitoring and analyzing result;
the operation record is used for storing an operation log;
the account management is used for carrying out RAM authorization management and RBAC authority management on the user account.
Specifically, log monitoring is responsible for collecting overall logs of a platform and providing a page query container log; authority control, which is responsible for login account and authority management control; the data warehouse is responsible for the functions of historical data backup, report generation by historical data query and the like; the alarm center is used for monitoring the health state of the service and the node and comprises the functions of collection, analysis, monitoring, alarm and the like; an operation record and a platform operation log record function; account management, a unified account management function, forms RAM (Resource Access Management) authorization and RBAC (Role-Based Access Control) rights management.
In the above embodiment, the external access layer, the standard service layer and the parallel platform layer are managed, so that a rapid and stable flexible container management platform is created, the delivery time, the risk, the infrastructure cost and the labor cost are reduced, and the availability and the flexibility of the platform are improved.
Optionally, as another embodiment of the application, the application adopts the k8s server and other technologies, mainly aims to solve the problem of supporting parallel issuing and starting of mass containers, builds a quick and stable elastic telescopic container management platform for protecting and navigating various safety events, and simultaneously, the container distribution platform adopting the k8 ssserver technology has the characteristics of elastic telescopic property, strong isolation, metering according to the quantity, operation and maintenance automation and the like, thereby bringing the core advantages of reducing the delivery time, reducing the risk, reducing the cost of infrastructure, reducing the labor cost and the like.
Alternatively, as another embodiment of the present application, the effects of the present application are as follows:
1. and carrying the management page and receiving the call task of the execution container by adopting a Django+cell technology. 2. The system can be deployed in a cloudy environment, and can provide elastic expansion and contraction by combining a container and Severless Kuberents service, so that burst traffic can be easily handled. 3. In order to increase the starting speed of the container, a mirror image caching technology is adopted to further accelerate the starting speed of the container. 4. The rich container access mode can hardly be accessed directly or through domain names by the traditional container, and the container of the system supports public networks ssh and nc access and supports dynamic domain name resolution access.
Alternatively, as another embodiment of the present application, the advantages of the present application are as follows:
1. elastic expansion management of container resources in a multi-cloud platform environment;
2. unified management and acceleration of mirror images and mirror image caches;
3. the container access supports public network ssh and nc access and dynamic domain name resolution access.
Optionally, as another embodiment of the present application, the present application is based on the optimization solution of new technologies such as mirror cache and Serverless kuberents, and can support real-time dynamic expansion across multiple cloud platforms, and provide dynamic domain name access and ssh public network access by the coreds+nginx+nc proxy mode.
Alternatively, as another embodiment of the present application, the flow of the present application is as follows:
input- > to outer access layer- > standard service layer- > parallel platform layer- > basic resource layer.
Optionally, as another embodiment of the present application, the present application may support dynamic expansion and contraction capacity, support multi-cloud deployment, support dynamic domain name access of a container, support ssh access of a container, support nc access of a container, and also be used to reduce load of a single machine, improve availability and scalability of the whole system by using the multi-cloud platform, determine the central processing unit availability and memory availability and server status of each server, and obtain a server ordering list with minimum memory availability according to a positive order of a memory priority principle.
Alternatively, as another embodiment of the present application, the present application has the following advantageous effects:
the method has the advantages of elasticity, simplicity, easiness in use, high container issuing speed, support of rich container access modes and support of private cloud deployment.
Alternatively, as another embodiment of the present application, the noun of the present application is explained as follows:
django is a Web application framework of open source code written by Python.
Celery, celery, is an asynchronous task queue/distributed messaging-based job queue. It focuses on real-time operation, but also works well for scheduling support.
Nc, ncat is Netcat. Netcat is used to read or send network data from a TCP/UDP connection. The cat is a command in Linux to view or connect files, so netcat is meant to view file content from the network. While Netcat's author Hobbit adds a very rich functionality to it, making it almost capable of performing a wide variety of operations in network operations, netcat is known in the field of network security as the "Swiss saber of TCPIP" ("Swiss-army knife forTCP/IP").
Dynamic domain name: the dynamic domain name can bind any translated IP address to a fixed secondary domain name. Regardless of the change in the IP address of the line, the internet user can use the fixed domain name to access or log into a server established with the dynamic domain name.
Infrastructure: a set of infrastructure and systems that support application sustainable functions.
A container: an isolated environment in which applications can run, packaged inside based on all necessary components and dependencies.
Containerization is the process of packaging applications into containers and filling them with everything necessary for perfect operation.
Microservices are a complex program or design method of services that break up a system into separate servlets and components.
Kubernetes (k 8 s) is a tool for managing and launching containerized applications in a declared container configuration framework.
Fig. 3 is a flow chart of a container scheduling method according to an embodiment of the application.
Alternatively, as another embodiment of the present application, as shown in fig. 3, a virtualized container management method includes the steps of:
receiving a container request instruction, and generating a container creation instruction according to the received container request instruction;
performing container creation according to the container creation instruction to obtain a creation result;
and carrying out container management on the creation result to obtain a container management result.
Alternatively, another embodiment of the present application provides a virtualized container management platform comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, which when executed by the processor, implements a virtualized container management method as described above. The system may be a computer or the like.
Alternatively, another embodiment of the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the virtualized container management method as described above.
It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the apparatus and units described above may refer to corresponding procedures in the foregoing method embodiments, which are not described herein again.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present application.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. For such understanding, the technical solution of the present application is essentially or part of what contributes to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The present application is not limited to the above embodiments, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the present application, and these modifications and substitutions are intended to be included in the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (10)
1. A virtualized container management platform, comprising: for the outer access layer, standard service layer and parallel platform layer,
the external access layer is used for receiving a container request instruction and generating a container creation instruction according to the received container request instruction;
the standard business layer is used for carrying out container creation according to the container creation instruction to obtain a creation result;
and the parallel platform layer is used for carrying out container management on the creation result to obtain a container management result.
2. The virtualized container management platform of claim 1, wherein the external access layer comprises a web portal management module, a receiving module, a task management module, and a system configuration module,
the portal management module is used for displaying and managing the container list, the mirror image list and the port list;
the receiving module is used for receiving a container request instruction and sending the container request instruction to the task management module, wherein the container request instruction comprises a container creation request instruction and a container deletion request instruction;
the task management module is used for generating a container creation instruction according to the container creation request instruction and/or the container deletion request instruction;
the system configuration module is used for configuring the basic information of the container.
3. The virtualized container management platform of claim 1, wherein the standard business layer comprises a public cloud access module, a private cloud access module, and a business routing module, the container creation instructions comprising public cloud creation instructions and private cloud creation instructions;
the public cloud access module is used for receiving the public cloud creation instruction, generating public cloud creation information according to the public cloud creation instruction, and sending the public cloud creation information to the service routing module;
the private cloud access module is used for receiving the private cloud creation instruction, generating private cloud creation information according to the private cloud creation instruction, and sending the private cloud creation information to the service routing module;
and the service routing module is used for carrying out container creation according to the public cloud creation information and/or the private cloud creation information to obtain a creation result.
4. The virtualized container management platform of claim 3, wherein the public cloud access module comprises a public cloud kube-apiserver unit, a public cloud etcd unit, a public cloud coredns unit, and a public cloud nginx unit,
the public cloud kube-apiserver unit is used for managing the public cloud creation instruction;
the public cloud etcd unit is used for storing all public cloud dynamic domain name information and all public cloud intranet ip information;
the public cloud coredns unit is used for analyzing all public cloud dynamic domain names and all public cloud intranet ip information to obtain a public cloud analysis result;
the public cloud nginx unit is used for receiving public cloud dynamic domain name access flow, obtaining public cloud intranet address information according to the public cloud analysis result, and sending the public cloud intranet address information and the public cloud dynamic domain name access flow to the service routing module.
5. The virtualized container management platform of claim 3, wherein the private cloud access module comprises a private cloud kube-apiserver unit, a private cloud etcd unit, a private cloud coredns unit, and a private cloud nginx unit,
the private cloud kube-apiserver unit is used for managing the private cloud creation instruction;
the private cloud etcd unit is used for storing all private cloud dynamic domain name information and all private cloud intranet ip information;
the private cloud coredns unit is used for resolving all the private cloud dynamic domain names and all the private cloud intranet ip information to obtain a private cloud resolving result;
the private cloud ginx unit is used for receiving private cloud dynamic domain name access flow, obtaining private cloud intranet address information according to the private cloud analysis result, and sending the private cloud intranet address information and the private cloud dynamic domain name access flow to the service routing module.
6. The virtualized container management platform of claim 3, wherein the traffic routing module comprises a dynamic domain name unit, a forwarding agent unit, a websocket access unit, a ssh access unit, a container management unit, a mirror management unit, and a node management unit,
the dynamic domain name unit is used for accessing the public cloud creation information and/or the private cloud creation information according to domain name information;
the forwarding agent unit is used for accessing the public cloud creation information and/or the private cloud creation information according to port forwarding information;
the websocket access unit is used for accessing the public cloud creation information and/or the private cloud creation information according to a websocket protocol;
the ssh access unit is used for accessing the public cloud creation information and/or the private cloud creation information according to a ssh protocol;
the container management unit is used for carrying out container creation, container deletion and container log viewing according to the public cloud creation information and/or the private cloud creation information to obtain an initial container;
the image management unit is used for carrying out image creation and image deletion according to the public cloud creation information and/or the private cloud creation information;
the node management unit is used for carrying out node addition and node deletion according to the public cloud creation information and/or the private cloud creation information.
7. The virtualized container management platform of claim 1, wherein the parallel platform layer comprises a calico module, a k8s server module, a capacity expansion service module, a mirror service module, a redis module, and a mysql module,
the calico module is used for constructing a virtualized network according to the creation result;
the k8s server module is used for constructing a virtual node container according to the creation result;
the capacity expansion service module is used for carrying out node addition, node expansion, node capacity reduction and node deletion on the virtual node container;
the mirror image service module is used for carrying out mirror image storage and mirror image management on the creation result;
the redis module is used for constructing a cache database;
the mysql module is configured to store the creation result in the cache database.
8. The virtualized container management platform of any one of claims 1-7, further comprising a base resource layer comprising an object storage module, an HDFS module, a physical server, and a virtual server,
the object storage module is used for storing the container management result;
the HDFS module is used for constructing a file storage system;
the entity server is used for carrying out main node management on the container management result;
and the virtual server is used for carrying out node capacity expansion and load balancing management on the container management result.
9. The virtualized container management platform of claim 1, further comprising a common component layer comprising log monitoring, rights control, data warehouse, alarm center, operation records, and account management,
the log monitoring is used for collecting container logs from the external access layer, the standard service layer and the parallel platform layer and inquiring the container logs;
the right control is used for logging in the user account and managing the right;
the data warehouse is used for storing historical data, inquiring the historical data and generating a report;
the alarm center is used for obtaining a service health state and a node health state from the external access layer, the standard service layer and the parallel platform layer;
monitoring and analyzing the service health state and the node health state to obtain a monitoring and analyzing result, and alarming the monitoring and analyzing result;
the operation record is used for storing an operation log;
the account management is used for carrying out RAM authorization management and RBAC authority management on the user account.
10. A method of virtualized container management, comprising the steps of:
receiving a container request instruction, and generating a container creation instruction according to the received container request instruction;
performing container creation according to the container creation instruction to obtain a creation result;
and carrying out container management on the creation result to obtain a container management result.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311099561.7A CN117170804A (en) | 2023-08-29 | 2023-08-29 | Virtualized container management platform and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311099561.7A CN117170804A (en) | 2023-08-29 | 2023-08-29 | Virtualized container management platform and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117170804A true CN117170804A (en) | 2023-12-05 |
Family
ID=88931190
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311099561.7A Pending CN117170804A (en) | 2023-08-29 | 2023-08-29 | Virtualized container management platform and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117170804A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107426034A (en) * | 2017-08-18 | 2017-12-01 | 国网山东省电力公司信息通信公司 | A kind of extensive container scheduling system and method based on cloud platform |
| CN108683747A (en) * | 2018-06-11 | 2018-10-19 | 华为技术有限公司 | Resource acquisition, distribution, method for down loading, device, equipment and storage medium |
| CN112199164A (en) * | 2020-10-19 | 2021-01-08 | 国网新疆电力有限公司信息通信公司 | Method for ensuring container mirror image consistency |
| CN112953908A (en) * | 2021-01-28 | 2021-06-11 | 中国工商银行股份有限公司 | Network isolation configuration method, device and system |
| CN114584511A (en) * | 2020-11-30 | 2022-06-03 | 瞻博网络公司 | Extending software-defined networks between public cloud computing infrastructures and data centers |
| CN114995841A (en) * | 2022-07-18 | 2022-09-02 | 浩鲸云计算科技股份有限公司 | Method and system for realizing extremely simple upgrading of database cloud service |
-
2023
- 2023-08-29 CN CN202311099561.7A patent/CN117170804A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107426034A (en) * | 2017-08-18 | 2017-12-01 | 国网山东省电力公司信息通信公司 | A kind of extensive container scheduling system and method based on cloud platform |
| CN108683747A (en) * | 2018-06-11 | 2018-10-19 | 华为技术有限公司 | Resource acquisition, distribution, method for down loading, device, equipment and storage medium |
| CN112199164A (en) * | 2020-10-19 | 2021-01-08 | 国网新疆电力有限公司信息通信公司 | Method for ensuring container mirror image consistency |
| CN114584511A (en) * | 2020-11-30 | 2022-06-03 | 瞻博网络公司 | Extending software-defined networks between public cloud computing infrastructures and data centers |
| CN112953908A (en) * | 2021-01-28 | 2021-06-11 | 中国工商银行股份有限公司 | Network isolation configuration method, device and system |
| CN114995841A (en) * | 2022-07-18 | 2022-09-02 | 浩鲸云计算科技股份有限公司 | Method and system for realizing extremely simple upgrading of database cloud service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032755B (en) | Container service hosting system and method for providing container service | |
| CN107707393B (en) | Multi-active system based on Openstack O version characteristics | |
| US11095534B1 (en) | API-based endpoint discovery of resources in cloud edge locations embedded in telecommunications networks | |
| US11368407B2 (en) | Failover management using availability groups | |
| CN105554065A (en) | Method, conversion unit and application unit for message processing | |
| WO2004109500A2 (en) | Tree based memory structure | |
| CN111314450B (en) | Data transmission method and device, electronic equipment and computer storage medium | |
| CN104901923A (en) | Virtual machine access device and method | |
| US20190372835A1 (en) | Private network mirroring | |
| CN111338893A (en) | Process log processing method and device, computer equipment and storage medium | |
| US11494130B2 (en) | Operation data accessing device and accessing method thereof | |
| KR100834361B1 (en) | Effiviently supporting multiple native network protocol implementations in a single system | |
| CN112882792B (en) | Information loading method, computer device and storage medium | |
| US8543680B2 (en) | Migrating device management between object managers | |
| CN111209364A (en) | Mass data access processing method and system based on crowdsourcing map updating | |
| US11743325B1 (en) | Centralized load balancing of resources in cloud edge locations embedded in telecommunications networks | |
| US9106676B1 (en) | Grid-based server messaging infrastructure | |
| CN111225003B (en) | NFS node configuration method and device | |
| CN101309148B (en) | Software watchdog system | |
| CN113315853B (en) | Cloud protection node scheduling method, system and storage medium | |
| EP3977707B1 (en) | Hardware load balancer gateway on commodity switch hardware | |
| CN117170804A (en) | Virtualized container management platform and method | |
| CN114500450B (en) | Domain name resolution method, device and computer readable storage medium | |
| CN106790521B (en) | System and method for distributed networking by using node equipment based on FTP | |
| CN111176782B (en) | Online experiment method and device |
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 |