CN114461346A - Micro-service system based on Docker container - Google Patents

Micro-service system based on Docker container Download PDF

Info

Publication number
CN114461346A
CN114461346A CN202210121145.1A CN202210121145A CN114461346A CN 114461346 A CN114461346 A CN 114461346A CN 202210121145 A CN202210121145 A CN 202210121145A CN 114461346 A CN114461346 A CN 114461346A
Authority
CN
China
Prior art keywords
docker
service
micro
host
microservice
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
Application number
CN202210121145.1A
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.)
Xian Chaoyue Shentai Information Technology Co Ltd
Original Assignee
Xian Chaoyue Shentai Information 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 Xian Chaoyue Shentai Information Technology Co Ltd filed Critical Xian Chaoyue Shentai Information Technology Co Ltd
Priority to CN202210121145.1A priority Critical patent/CN114461346A/en
Publication of CN114461346A publication Critical patent/CN114461346A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing

Landscapes

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

Abstract

The invention discloses a micro-service system based on a Docker container, which comprises: when a user acquires new equipment or needs to add new services, the Docker registration server acquires a target Docker micro-service image from the Docker image warehouse according to the equipment identification of the new equipment or the service number of the new services, and deploys the target Docker micro-service image into a target Docker container of the host. Therefore, on the basis of providing standard services, value-added services are developed to meet the requirements of different user groups.

Description

Micro-service system based on Docker container
Technical Field
The invention relates to the technical field of computers, in particular to a micro-service system based on a Docker container.
Background
With the development of communication technology and internet, automation plants are used as the main sites of production activities, on one hand, the automation plants need to be able to enjoy various professional services, and on the other hand, due to the confidentiality of the environment where the production sites are located, the security of data is particularly important. At present, the whole data and service functions in the traditional service are provided by a service provider, so that the functional coupling of the application in the traditional service is very strong, the customization can not be carried out according to the user requirements, and the data security can not be ensured.
Disclosure of Invention
The invention provides a micro-service system based on a Docker container, which can develop value-added services on the basis of providing standard services and meet the requirements of different user groups.
Based on the above purpose, an aspect of the embodiments of the present invention provides a micro service system based on a Docker container, which specifically includes:
each first device corresponds to one Docker micro-service mirror image;
a Docker mirror image warehouse, wherein a Docker micro-service mirror image corresponding to each first device is registered in the Docker mirror image warehouse;
the system comprises a host machine, a plurality of Docker containers are operated on the host machine, and each Docker container corresponds to a Docker micro-service mirror image;
when a user acquires a second device or needs to add a first service, the Docker registration server obtains a first target Docker micro-service image from the Docker image warehouse according to a device identifier of the second device or a service number of the first service, and deploys the first target Docker micro-service image into a first target Docker container of the host.
In some embodiments, the host comprises a hardware host, a NAS storage device, a host operating system, a Docker container engine, a Docker microservice set;
the Docker micro service set comprises Docker micro service images corresponding to the first devices.
In some embodiments, the Docker microservice set further includes a storage microservice and a communication microservice; the storage microservice is used for storing data into the NAS equipment; the communication micro-service is used for communication and management between the Docker micro-service image and the device.
In some embodiments, when a user accesses a first target device by using a terminal, a Docker microservice set calls a Docker microservice image corresponding to the first target device, and sends data including a device identifier and a control instruction of the first target device to the terminal through a communication microservice, so as to control or access the first target device.
In some embodiments, the NAS storage device is used to store device information and/or logs.
In some embodiments, a hardware host is provided with a gateway module; the hardware host communicates with an external network through the gateway module.
In some embodiments, a hardware host is provided with a communication module; the hardware host communicates with the plurality of first devices through the communication module.
In some embodiments, the hardware host communicates wirelessly as follows: ZigBee, mobile hotspot Wi-Fi and Bluetooth.
In some embodiments, the host operating system employs a Linux system.
In some embodiments, when a host is upgraded, a Docker micro-service image on the host is migrated to a cache unit through a Docker image warehouse, and after the upgrade is completed, the Docker micro-service image is redeployed to a Docker container of the host.
In the embodiment of the invention, when a user acquires new equipment or needs to add new services, the Docker registration server acquires a target Docker micro-service image from the Docker image warehouse according to the equipment identification of the new equipment or the service number of the new services, and deploys the target Docker micro-service image into a target Docker container of a host. Therefore, on the basis of providing standard services, value-added services are developed to meet the requirements of different user groups.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
Fig. 1 is a schematic structural diagram of a micro service system based on a Docker container according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a Docker microservice set in a microservice system based on a Docker container according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
The LXC is short for Linux Container, and is a kernel virtualization technology of an LXC Container, which can provide lightweight virtualization so as to isolate processes and resources. Docker is a new container developed based on LXC technology, which can be understood as a sandbox. An application is independently run in each container, different containers are isolated from each other, and a communication mechanism can be established between the containers. The creation and stopping of the Docker container may be accomplished on the order of seconds. Meanwhile, the Docker container has little demand on system resources, and thousands of Docker containers can be operated on one host at the same time. The isolation of Docker determines that only a container with a new function needs to be added when a function is added on a server, and the container is deployed and migrated at the same time.
The invention provides an embodiment of a micro-service system based on a Docker container. As shown in fig. 1, the system may include: a plurality of first devices, a Docker mirror repository, and a host. Each first device in the plurality of first devices corresponds to one Docker micro-service mirror image. The Docker mirror image warehouse is registered with Docker micro-service mirror images corresponding to each first device. And a host runs a plurality of Docker containers, and each Docker container corresponds to one Docker micro-service mirror image. When a user acquires a second device or needs to add a first service, the Docker registration server obtains a first target Docker micro-service image from the Docker image warehouse according to a device identifier of the second device or a service number of the first service, and deploys the first target Docker micro-service image into a first target Docker container of the host.
The second device may be understood as a newly added device, which may be the same as or different from the first device.
As shown in fig. 1, the plurality of first devices may include device 1, device 2, device 3, and the like. The host may be a factory host as shown in FIG. 1. The factory host corresponds to each factory in the whole park, and the host architecture of each factory is the same. The Docker image repository may be the facilitator Docker image repository shown in fig. 1.
When a factory user purchases new equipment or needs to add additional corresponding services, the micro-service mirror image is obtained from the corresponding mirror image warehouse through the Docker registration server according to the equipment identification or the service number, and is deployed into the Docker container of the host machine. This selection on demand allows customization. Meanwhile, because the Docker mirror image runs in the container, the Docker mirror image can be constructed and run everywhere once only by developing and configuring the Docker mirror image according to standards and specifications. A Docker micro service provider can develop value-added services on the basis of providing standard services for users, and meet the requirements of different user groups.
In some embodiments, a host may include a hardware host, a NAS storage device, a host operating system, a Docker container engine, a Docker microservice set. The Docker micro service set comprises Docker micro service images corresponding to the first devices.
In some embodiments, the NAS storage device is used to store device information and/or logs. Each host machine adopts the NAS storage equipment of the host machine to store various data generated by tenants instead of storing the data on a public network server, so that the safety of the data is ensured.
In the embodiment of the invention, the storage microservice is responsible for storing the device information, logs and the like acquired by the device microservice on the NAS storage device, and each user is provided with the independent storage microservice and the NAS storage device on the host machine of the user, so that the safety of data privacy can be ensured.
In some embodiments, the Docker microservice set may also include storage microservices and communication microservices. The storage microservice is used to store data into the NAS device. The communication micro-service is used for communication and management between the Docker micro-service image and the device. As shown in fig. 2, each microservice corresponds to a Docker container mirror, and since dockers consume very little system resources, thousands of Docker containers can be run on each host, thereby implementing management and access to a plurality of devices. Wherein the storage microserver is primarily responsible for storing data into the NAS device. The communication microservice is responsible for communication and management between device microservices and devices.
In the embodiment of the present invention, the Docker microservice set is responsible for managing each device. The method comprises the steps of ensuring the normal operation of each device, calling the micro service of the corresponding device when a factory user accesses the device by adopting a mobile terminal such as a mobile phone or a webpage, and then sending data containing information such as device identification, control instructions and the like to the corresponding device through the communication micro service so as to control or access the device. Each Docker device microservice corresponds to a device identifier. And the efficient and single management of the equipment is ensured.
In some embodiments, when a user accesses a first target device by using a terminal, a Docker microservice set calls a Docker microservice image corresponding to the first target device, and sends data including a device identifier and a control instruction of the first target device to the terminal through a communication microservice, thereby controlling or accessing the first target device.
In some embodiments, a hardware host is provided with a gateway module; the hardware host machine communicates with an external network through the gateway module.
In some embodiments, a hardware host is provided with a communication module; the hardware host communicates with the plurality of first devices through the communication module.
In some embodiments, the hardware host communicates wirelessly as follows: ZigBee, mobile hotspot Wi-Fi and Bluetooth.
In some embodiments, the host operating system employs a Linux system. For example, Ubuntu, Fedora, CentOS, etc.
In some embodiments, when a host is upgraded, a Docker micro-service image on the host is migrated to a cache unit through a Docker image warehouse, and after the upgrade is completed, the Docker micro-service image is redeployed to a Docker container of the host.
In the embodiment of the invention, when a tenant upgrades a host machine, a Docker mirror image on an original host machine can be migrated through a private warehouse of a Docker microservice provider, and is relocated to a Docker container of the original host machine after the upgrade is finished.
In summary, in the embodiment of the present invention, a micro service system is implemented by using a Docker. And deploying the containers on the host machine through a Docker mirror image provided by a Docker micro service provider. In this way, efficient, decentralized microservices are achieved. Different users are independent of each other and can be located on different service providers. The system is completely controlled by the user. Each set of system is composed of a series of tiny services.
Finally, it should be understood by those skilled in the art that all or part of the processes in the system implementing the embodiments described above can be implemented by instructing the relevant hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when executed, the program can include the processes of the embodiments of the systems described above. The storage medium of the program may be a magnetic disk, an optical disk, a Read Only Memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described system embodiments corresponding thereto.
The foregoing are exemplary embodiments of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the system claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, where the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant only to be exemplary, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.

Claims (10)

1. A Docker container-based microservice system, comprising:
each first device corresponds to one Docker micro-service mirror image;
a Docker mirror image warehouse, in which Docker micro-service mirror images corresponding to each first device are registered;
the host machine runs a plurality of Docker containers, and each Docker container corresponds to one Docker micro-service mirror image;
when a user acquires a second device or needs to add a first service, the Docker registration server acquires a first target Docker micro-service image from the Docker image warehouse according to a device identifier of the second device or a service number of the first service, and deploys the first target Docker micro-service image to a first target Docker container of the host.
2. The system of claim 1, wherein the host comprises a hardware host, a NAS storage device, a host operating system, a Docker container engine, a Docker microservice set;
the Docker micro-service set comprises a plurality of Docker micro-service mirror images corresponding to the first equipment.
3. The system of claim 2, wherein the Docker microservice set further comprises a storage microservice and a communication microservice; the storage microservice is used for storing data into the NAS device; the communication micro-service is used for communication and management between the Docker micro-service mirror image and the equipment.
4. The system according to claim 3, wherein when the user accesses the first target device by using a terminal, the Docker microservice set calls a Docker microservice image corresponding to the first target device, and sends data including a device identifier and a control instruction of the first target device to the terminal through the communication microservice, thereby controlling or accessing the first target device.
5. The system of claim 2, wherein the NAS storage device is configured to store device information and/or logs.
6. The system of claim 2, wherein the hardware host is provided with a gateway module; and the hardware host machine is communicated with an external network through the gateway module.
7. The system according to claim 2 or 6, wherein the hardware host is provided with a communication module; the hardware host machine communicates with the plurality of first devices through the communication module.
8. The system of claim 7, wherein the hardware host communicates wirelessly as follows: ZigBee, mobile hotspot Wi-Fi and Bluetooth.
9. The system of claim 2, wherein the host operating system is a Linux system.
10. The system of claim 1, wherein when the host is upgraded, the Docker microservice image on the host is migrated to a cache unit through the Docker image warehouse, and after the upgrade is completed, the Docker microservice image is redeployed to the Docker container of the host.
CN202210121145.1A 2022-02-09 2022-02-09 Micro-service system based on Docker container Pending CN114461346A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210121145.1A CN114461346A (en) 2022-02-09 2022-02-09 Micro-service system based on Docker container

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210121145.1A CN114461346A (en) 2022-02-09 2022-02-09 Micro-service system based on Docker container

Publications (1)

Publication Number Publication Date
CN114461346A true CN114461346A (en) 2022-05-10

Family

ID=81413120

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210121145.1A Pending CN114461346A (en) 2022-02-09 2022-02-09 Micro-service system based on Docker container

Country Status (1)

Country Link
CN (1) CN114461346A (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105955771A (en) * 2016-04-27 2016-09-21 浪潮集团有限公司 Method, device and system for realizing operating system
CN109714358A (en) * 2019-01-15 2019-05-03 广东工业大学 A kind of injection molding MES cloud platform of micro services
CN112468337A (en) * 2020-11-19 2021-03-09 安徽江淮汽车集团股份有限公司 Deployment method, device, equipment and storage medium of Internet of vehicles microservice

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105955771A (en) * 2016-04-27 2016-09-21 浪潮集团有限公司 Method, device and system for realizing operating system
CN109714358A (en) * 2019-01-15 2019-05-03 广东工业大学 A kind of injection molding MES cloud platform of micro services
CN112468337A (en) * 2020-11-19 2021-03-09 安徽江淮汽车集团股份有限公司 Deployment method, device, equipment and storage medium of Internet of vehicles microservice

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
付琳琳等: "微服务容器化部署的研究", 《计算技术与自动化》, 31 December 2019 (2019-12-31), pages 151 - 155 *
姚世峰编: "《城市轨道交通云计算应用指南》", 31 December 2020, 北京：中国铁道出版社, pages: 51 - 61 *

Similar Documents

Publication Publication Date Title
US11968100B2 (en) Service enabler function
US10089106B2 (en) Communications network, computer architecture, computer-implemented method and computer program product for development and management of femtocell-based applications
US9439025B1 (en) Multi-step mobile device initiation with intermediate partial reset
US9208513B1 (en) Automated branding of generic applications
CN111475170B (en) Multi-screen application enablement and distribution service
US9913132B1 (en) System and method of mobile phone customization based on universal manifest
CN111726399B (en) Docker container secure access method and device
JP2018510517A (en) Dynamic subscriber identification module
US11102646B1 (en) Triggering electronic subscriber identity module activation
CN107430512A (en) Machine is managed to the application relation in machine system
CN112130866A (en) Application deployment method and related device
US11611861B2 (en) Internet of Things communication service
CN115525396A (en) Application management method and device based on cloud protogenesis
US9198045B1 (en) Mobile communication device remote unlock system and method
JP2021511688A (en) Network slice configuration method and equipment, computer storage medium
CN114461346A (en) Micro-service system based on Docker container
CN117251177A (en) Micro-service deployment method and device based on containerization technology and electronic equipment
US11190523B1 (en) Post-activation installation of custom applications with system privileges
Jerónimo Bañuelos et al. An Application Programming Interface for Android to support dedicated 5G network slicing
Namiot et al. On Data Program Interfaces
CN113703798A (en) Distributed service updating method and device, computer equipment and storage medium
Room Multi-Access Edge Computing
Bahtovski et al. Interoperability of Cloud and Mobile Services
Bahtovski et al. Interoperability Standards Impact on the Cloud Virtualization
Namiot et al. 2 On Software Standards

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