CN109039686B

CN109039686B - Method and device for business mixed arrangement

Info

Publication number: CN109039686B
Application number: CN201710438631.5A
Authority: CN
Inventors: 许亨; 高静; 孙琼华
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2017-06-12
Filing date: 2017-06-12
Publication date: 2022-11-08
Anticipated expiration: 2037-06-12
Also published as: CN109039686A

Abstract

The embodiment of the invention provides a method and a device for business mixed arrangement, wherein the method comprises the following steps: performing logic association on one or more components in the service virtualization component corresponding to the first virtual platform and/or performing logic association on one or more components in the service containerization component corresponding to the second virtual platform according to the service received by the first virtual platform and/or the second virtual platform; logically associating one or more components of the common component with one or more of the business virtualization components and/or one or more of the business containerization components; and deploying the services according to the logic association of each component in the service virtualization component and/or the logic association of each component in the service containerization component, and the logic association of the common component and the service virtualization component and/or the logic association of the common component and the logic association of the service containerization component, so that the problem of service mixing arrangement of the first virtual platform and the second virtual platform is solved.

Description

Service mixing arrangement method and device

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for service mix orchestration.

Background

A Virtualized Data Center (VDC) is a new Data Center model that applies the cloud computing concept to IDC (Internet Data Center). By combining the traditional IDC service and the cloud computing technology, a unified innovative VDC operation management system is built, virtualization, automatic deployment and other technologies are applied, a telescopic virtualization infrastructure is built, and a basic IT facility scheme and service of one-point acceptance and whole-network service are provided for users by adopting a centralized management and distributed service mode. VDC is mainly distinguished from traditional IDC in that the infrastructure is provided as a service by technical means; physical resources are abstractly integrated through a virtualization technology, and service capacity is enhanced; the resource utilization capacity and the service reliability are improved through dynamic resource allocation and scheduling; the method has the advantages that automatic service opening capacity is provided, operation and maintenance cost is reduced, and convenient user experience is provided; more security mechanisms and reliability mechanisms are provided, and the security standard of enterprise-level application is met.

In a traditional virtualization environment, most resource carriers for running cloud applications are virtual machines, and after a novel virtualization technology of a container is introduced, the cloud applications can be migrated to the container. The traditional virtual technology has larger performance loss, and the container has the advantages of not only being capable of being deployed quickly, but also being capable of reducing the load of memory resources, network resources and storage resources and improving the performance and the resource use efficiency. However, in the cloud application management system, the deployment system of the virtual machine usage and the deployment system of the container are different from each other, for example, the deployment system of the virtual machine mainly deviates from the IaaS (Infrastructure as a Service) level, and the container is only one branch of the computing part, and there is far no IaaS excellence in processing the storage and network subsystems. For example, the virtual platform of Openstack orchestrates services using ADT (Abstract Data Type) technology, and is not consistent with pages, modes, and network element components of the virtual platform of kubernets orchestration of services, how to effectively merge these two orchestration systems together without needing to care whether the bottom layer is a virtual machine or a container, which is a problem to be solved.

Disclosure of Invention

In order to solve the above technical problem, embodiments of the present invention provide a method and an apparatus for service mixing arrangement. The method and the device for business mixing arrangement can solve the problem that business mixing arrangement cannot be realized due to the fact that the page, mode and network element components of business arrangement of the first virtual platform for business virtualization and the second virtual platform for business containerization are not consistent.

According to an aspect of the embodiments of the present invention, there is provided a method for arranging service mixes, including: according to the service received by a first virtual platform of service virtualization and/or a second virtual platform of service containerization, performing logic association on one or more components in service virtualization components corresponding to the first virtual platform and/or performing logic association on one or more components in service containerization components corresponding to the second virtual platform;

logically associating one or more components of a common component with one or more of the business virtualization components and/or one or more of the business containerization components;

deploying the service received by the first virtual platform and/or the second virtual platform according to the logic association of one or more components in the service virtualization components and/or the logic association of one or more components in the service containerization components, and the logic association of one or more components of the common components with one or more components in the service virtualization components and/or with one or more components in the service containerization components.

Optionally, one or more of the service virtualization components include at least: a physical machine component, a virtual machine component and/or a first portal component;

logically associating one or more of the business virtualization components corresponding to the first virtual platform, including:

logically associating a physical machine component of the service virtualization component with a physical machine; and/or

Performing logical association on a virtual machine component in the service virtualization component and a mirror image warehouse, and creating a virtual machine corresponding to the virtual machine component in the service virtualization component through a first mirror image file acquired from the mirror image warehouse;

and logically associating the first internet access component of the service virtualization component with the virtual machine component of the service virtualization component.

Optionally, the service virtualization component further includes: the main and standby dual-machine components and/or the service self-healing component;

logically associating one or more of the business virtualization components corresponding to the first virtual platform, further comprising:

performing logical association on a main/standby dual-machine component of the service virtualization component and a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing main/standby dual-machine service for the service virtualization component and/or the service containerization component through the main/standby dual-machine component of the service virtualization component; and/or

And logically associating the service self-healing component of the service virtualization component with a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing service self-healing service for the service virtualization component and/or the service containerization component through the service self-healing component of the service virtualization component.

Optionally, one or more components of the service containerization component include at least: a container node component, one or more container components, and/or a second portal component;

logically associating one or more of the business containerized components corresponding to the second virtual platform, including:

deploying, by a container node component of the traffic containerization component, one or more container components of the traffic containerization component onto a same node of container node components;

and logically associating one or more container components of the business containerization component with an image warehouse, and creating a container corresponding to the one or more container components through a second image file acquired from the image warehouse.

Optionally, the service containerization component further includes: one or more container port assemblies corresponding to the one or more container assemblies;

logically associating one or more of the service containerization components corresponding to the second virtual platform, further comprising:

logically associating a container port component of the service containerization component with one or more container components of a service containerization component;

and logically associating the container port component of the service containerization component with a second internet access component of the service containerization component, and performing reverse proxy on one or more container components through the container port component and the second internet access component.

Optionally, one or more components of the common components comprise at least: network components and/or middleware components;

logically associating one or more components of a common component with one or more of the business virtualization components and/or one or more of the business containerization components, comprising:

the network component of the public component is logically associated with the first internet access component of the service virtualization component and/or the second internet access component of the service containerization component, and the virtual machine component and/or the service containerization component are respectively communicated with the network covered by the tenant permission corresponding to the virtual machine component and/or the container node component through the network component;

and logically associating the middleware component of the common component with the virtual machine component and/or the container node component, and logically associating the business virtualization component and/or the business containerization component with the middleware covered by the tenant permission corresponding to the virtual machine component and/or the container node component in a service market through the middleware component of the common component.

Optionally, the common component further comprises: an application component, a load balancing component and/or an elastic telescopic component;

logically associating one or more components of a common component with one or more of the business virtualization components and/or one or more of the business containerization components, further comprising:

logically associating the application component of the common component with the virtual machine component, the container node component and/or the physical machine component, and acquiring application software covered by tenant permissions corresponding to the service virtualization component, the service containerization component and/or the physical machine component from a software warehouse connected with the application component of the common component through the application component of the common component; and/or

Performing logic association on the load balancing component of the common component and the virtual machine component and/or the container node component, and performing load balancing on the service of the virtual machine component and/or the container node component through the load balancing component; and/or

And logically associating the elastic expansion component of the common component with the virtual machine component and/or the container node component, wherein the elastic expansion component of the common component depends on the load balancing component of the common component, and an elastic expansion strategy of the service of the virtual machine component and/or the container node component is set through the elastic expansion component of the common component.

According to another aspect of the embodiments of the present invention, there is also provided an apparatus for service mix orchestration, including:

the first logic association module is used for performing logic association on one or more components in the service virtualization component corresponding to the first virtual platform and/or performing logic association on one or more components in the service containerization component corresponding to the second virtual platform according to the service received by the first virtual platform for service virtualization and/or the second virtual platform for service containerization;

a second logical association module for logically associating one or more components of a common component with one or more of the service virtualization components and/or one or more of the service containerization components;

and the service deployment module is used for deploying the service received by the first virtual platform and/or the second virtual platform according to the logic association of one or more components in the service virtualization components and/or the logic association of one or more components in the service containerization components, and the logic association of one or more components of the common component with one or more components in the service virtualization components and/or the logic association of one or more components in the service containerization components.

Optionally, one or more components of the service virtualization component at least include: a physical machine component, a virtual machine component and/or a first portal component;

the first logical association module comprising:

the first logic association unit is used for logically associating the physical machine component of the service virtualization component with a physical machine; and/or

The second logic association unit is used for logically associating the virtual machine assembly in the service virtualization assembly with the mirror image warehouse and creating a virtual machine corresponding to the virtual machine assembly in the service virtualization assembly through the first mirror image file acquired from the mirror image warehouse;

and the third logic association unit is used for performing logic association on the first internet access component of the service virtualization component and the virtual machine component of the service virtualization component.

the first logical association module further comprises:

a fourth logical association unit, configured to logically associate the active/standby dual-machine component of the service virtualization component with the virtual machine component of the service virtualization component or the container node component of the service containerization component, and provide the active/standby dual-machine service for the service virtualization component and/or the service containerization component through the active/standby dual-machine component of the service virtualization component; and/or

And the fifth logic association unit is used for logically associating the service self-healing component of the service virtualization component with the virtual machine component of the service virtualization component or the container node component of the service containerization component, and providing service self-healing service for the service virtualization component and/or the service containerization component through the service self-healing component of the service virtualization component.

Optionally, one or more of the service containerization components include at least: a container node component, one or more container components, and/or a second portal component;

the first logical association module further comprises:

a sixth logical association unit, configured to deploy, by a container node component of the service containerization components, one or more container components of the service containerization components onto a same node of the container node components;

and the seventh logical association unit is used for logically associating one or more container components of the service containerization component with the mirror image warehouse and creating a container corresponding to the one or more container components through a second mirror image file acquired from the mirror image warehouse.

the first logical association module further comprises:

an eighth logical association unit, configured to logically associate a container port component of the service containerization component with one or more container components of a service containerization component;

a ninth logical association unit, configured to perform logical association between the container port component of the service containerization component and a second portal component of the service containerization component, and perform reverse proxy on one or more container components through the container port component and the second portal component.

Optionally, one or more of the common components include at least: network components and/or middleware components;

the second logical association module includes:

a tenth logical association unit, configured to logically associate the network component of the common component with the first portal component of the service virtualization component and/or the second portal component of the service containerization component, and communicate, through the network component, the virtual machine component and/or the service containerization component with a network covered by a tenant right corresponding to the virtual machine component and/or the container node component, respectively;

and the eleventh logic unit is configured to logically associate the middleware component of the common component with the virtual machine component and/or the container node component, and logically associate the service virtualization component and/or the service containerization component with the middleware covered by the tenant right corresponding to the virtual machine component and/or the container node component in the service market through the middleware component of the common component.

Optionally, the common component further comprises: the system comprises an application component, a load balancing component and/or an elastic telescopic component;

the second logical association module further comprises:

a twelfth logic unit, configured to logically associate an application component of the common component with the virtual machine component, the container node component, and/or the physical machine component, and obtain, through the application component of the common component, application software covered by tenant permissions corresponding to the service virtualization component, the service containerization component, and/or the physical machine component from a software repository connected to the application component of the common component; and/or

A thirteenth logic unit, configured to logically associate a load balancing component of the common component with the virtual machine component and/or the container node component, and perform load balancing on a service of the virtual machine component and/or the container node component through the load balancing component; and/or

A fourteenth logic unit, configured to logically associate the elastic stretching component of the common component with the virtual machine component and/or the container node component, where the elastic stretching component of the common component relies on the load balancing component of the common component, and sets an elastic stretching policy for a service of the virtual machine component and/or the container node component through the elastic stretching component of the common component.

According to another aspect of the embodiments of the present invention, there is also provided an apparatus for service mix orchestration, including: a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of service mix orchestration as described above when executing the program.

According to still another aspect of the embodiments of the present invention, there is further provided a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps in the method of service mix orchestration as described above.

The embodiment of the invention has the following beneficial effects:

firstly, according to the tasks received by the first virtual platform and/or the second virtual platform, one or more components of the service virtualization component and/or one or more components of the service containerization component are respectively logically associated, wherein the service virtualization component and the service containerization component are independent when being arranged. In this embodiment, the common component is listed separately, and when service deployment is performed, the service virtualization component and the service containerization component may share the common component, and the purpose of multi-party interaction is achieved by logically associating one or more components of the common component with one or more components in the service virtualization component and/or one or more components in the service containerization component. The method for service mixing and arranging in the embodiment can solve the problem that service mixing and arranging can not be realized on the two virtual platforms because the pages, modes and network element components of service arranging of the first virtual platform for service virtualization and the second virtual platform for service containerization are not consistent.

Secondly, the service virtualization component, the service containerization component and the public component can uniformly adopt a jsPlumb + avalon architecture, so that specific services can be patterned, the logic association of each component can be realized by clicking and dragging the graph corresponding to each component to connect, and each component is visual and convenient in service binding and deployment.

Drawings

Fig. 1 is a flowchart of a method for service mix orchestration according to an embodiment of the present invention;

fig. 2 is a flowchart of a method for service mix orchestration according to another embodiment of the present invention;

fig. 3 is a flowchart illustrating a method for service orchestration under SDN according to an embodiment of the present invention;

fig. 4 is a schematic structural diagram of a service mix orchestration apparatus according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a device for arranging service mixes according to another embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments.

The terms first, second and the like in the description and in the claims of the present invention are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein.

Fig. 1 is a flowchart of a method for arranging service mixes according to an embodiment of the present invention, and referring to fig. 1, the method specifically includes the following steps:

s101, according to the service received by a first virtual platform of service virtualization and/or a second virtual platform of service containerization, performing logic association on one or more components in the service virtualization component corresponding to the first virtual platform and/or performing logic association on one or more components in the service containerization component corresponding to the second virtual platform.

In this embodiment, the first virtual platform is an open-source cloud computing management platform or the first virtual platform may be an open platform for managing computing, storage, and/or network resource data center cloud computing. The first virtual platform can provide a deployment cloud operating platform or a tool set, can construct a cloud of virtual computing or storage cloud service, can be a public cloud or a private cloud, and can provide extensible and flexible cloud computing for big clouds and small clouds. Optionally, the first virtual platform may be an OpenStack virtual platform, but is not limited thereto.

The first virtual platform is combined by several main components to complete specific work. The service virtualization component corresponding to the first virtual platform comprises one or more components, and after the service received by the first virtual platform, the one or more components of the service virtualization component are logically associated according to the task received by the first virtual platform.

Optionally, one or more of the service virtualization components at least include: a physical machine component, a virtual machine component, and/or a first portal component. After the service received by the first virtual platform, the physical machine component, the virtual machine component and/or the first internet access component may be logically associated according to the task received by the first virtual platform. It should be noted that, in the present embodiment, the kind of one or more components of the service virtualization component is not specifically limited.

In this embodiment, the second virtual platform is an open-source container cluster management platform. The second virtual platform can provide a series of complete functions such as deployment and operation, resource scheduling, service discovery and dynamic scaling for containerized applications, and convenience in large-scale container cluster management can be improved. Optionally, the second virtual platform may be a kubernets virtual platform, but is not limited thereto.

The second virtual platform also needs to be combined by several main components to complete specific work. And after the second virtual platform receives the task, performing logic association on one or more components of the service containerization component according to the task received by the second virtual platform.

Optionally, one or more components of the service containerization component include at least: a container node component, one or more container components, and/or a second portal component. After the second virtual platform receives the task, the container node component, the one or more container components and/or the second portal component are logically associated according to the task received by the second virtual platform. It should be noted that, in the present embodiment, the kind of one or more components of the service containerization component is not particularly limited.

It should be noted that there may be many ways for performing logical association on one or more components in the service virtualization component corresponding to the first virtual platform and/or performing logical association on one or more components in the service containerization component corresponding to the second virtual platform, for example, a jspsmb + avalon architecture may be adopted, and the logical association between the components is implemented by graphing the one or more components in the service virtualization component and the one or more components in the service containerization component and by connecting wires. It should be noted that the embodiment of the present invention does not specifically limit the manner of logical association.

S102, logically associating one or more components of the common components with one or more components in the service virtualization components and/or one or more components in the service containerization components.

Specifically, logically associating one or more components of a common component with one or more components of the business virtualization components and/or one or more components of the business containerization components comprises:

associating one or more components of the common component and/or logically associating one or more components of the common component with one or more components of the business virtualization components according to the task received by the first virtual platform; and/or

And logically associating one or more components of the common component and/or logically associating one or more components of the common component with one or more components of the business containerization components according to the task received by the second virtual platform.

Optionally, one or more of the common components include at least: network components and/or middleware components. Logically associating a network component and/or a middleware component with one or more of the service virtualization components and/or one or more of the service containerization components based on the tasks received by the first virtual platform and/or the second virtual platform. It should be noted that the kind of one or more components of the common components is not particularly limited in this embodiment.

S103, deploying the service received by the first service virtualization platform and/or the second service containerization platform according to the logic association of one or more components in the service virtualization components and/or the logic association of one or more components in the service containerization components, and the logic association of one or more components in the common component and one or more components in the service virtualization components and/or one or more components in the service containerization components.

It should be noted that, the service received by the first virtual platform may be deployed on a virtual machine or a physical machine, and the task received by the second virtual platform may be deployed in a container, which is not limited to this.

In this embodiment, after the second virtual platform and the second virtual platform receive the task, according to the task received by the first virtual platform and/or the second virtual platform, the one or more components of the service virtualization component and/or the one or more components of the service containerization component are respectively logically associated, where the service virtualization component and the service containerization component are independent from each other when being arranged. In this embodiment, the common component is listed separately, and when service deployment is performed, the service virtualization component and the service containerization component may share the common component, and the purpose of multi-party interaction is achieved by logically associating one or more components of the common component with one or more components in the service virtualization component and/or one or more components in the service containerization component. The method for service mixing and arranging in the embodiment can solve the problem that service mixing and arranging cannot be realized due to the fact that the page, mode and network element components of service arranging of the first virtual platform for service virtualization and the second virtual platform for service containerization are not consistent.

In another embodiment of the present invention, the one or more components of the service virtualization component include at least: a physical machine component, a virtual machine component (which may be referred to simply as a VM component), and a first portal component. Wherein the physical machine components are used to bind the actual physical machines. The virtual machine component is used for establishing a virtual machine corresponding to the virtual machine component. The first portal component is used for the entry of a virtual network, for example, the first portal component is connected with a network component of a common component, and then the virtual network is provided for the virtual machine component through the first portal component.

In another embodiment of the present invention, one or more of the components of the service containerization component include at least: a container node component, one or more container components, and a second portal component. The container node component is used for providing a basic unit for one or more container components, and one or more container components below the container node component are guaranteed to be deployed on the same node. The one or more container components are used to create a container corresponding to the one or more container components. The second portal component is for ingress to a virtual network of container node components and/or provides a reverse proxy for one or more container components.

In another embodiment of the invention, one or more of the common components comprise at least: network components and middleware components. The network component is used for binding a network covered by tenant authority corresponding to the first virtual platform and/or the second virtual platform in the network center and providing a network for the VM component and/or the container node component. The middleware component is used for binding each middleware covered by the tenant permission corresponding to the first virtual platform and/or the second virtual platform in the service market. The middleware may be an application program or a database, but is not limited thereto.

Fig. 2 is a flowchart of a method for arranging service mixes according to another embodiment of the present invention, and referring to fig. 2, the specific steps include:

s201, according to a service received by a first virtual platform of service virtualization and/or a second virtual platform of service containerization, performing logical association on a physical machine component, a virtual machine component, and a first network interface component of a service virtualization component and/or performing logical association on a container node component, one or more container components, and a second network interface component of a service containerization component.

After the service received by the first virtual platform, performing logical association on the physical machine component, the virtual machine component, and/or the first portal component according to the task received by the first virtual platform, specifically including:

Logically associating a virtual machine assembly in the service virtualization assembly with a mirror image warehouse, and creating a virtual machine corresponding to the virtual machine assembly in the service virtualization assembly through a first mirror image file acquired from the mirror image warehouse;

Specifically, after the second virtual platform receives the task, performing logical association on the container node component, the one or more container components, and/or the second portal component according to the task received by the second virtual platform, specifically including:

And S202, performing logic association on the network component and the middleware component of the common component with a physical machine component, a virtual machine component and a first internet access component in the service virtualization component and/or performing logic association with a container node component, one or more container components and a second internet access component in the service container component.

Specifically, logically associating a network component and/or a middleware component with a physical machine component, a virtual machine component, and a first portal component in the service virtualization component and/or logically associating with a container node component, one or more container components, and a second portal component in the service containerization component specifically includes:

S203, deploying the service received by the first virtual platform and/or the second virtual platform according to the logical association of the physical machine component, the virtual machine component, and the first internet access component of the service virtualization component and/or the logical association of the container node component, the one or more container components, and the second internet access component of the service container component, and the logical association of the network component and the middleware component of the common component with the physical machine component, the virtual machine component, and the first internet access component of the service virtualization component and/or the logical association with the container node component, the one or more container components, and the second internet access component of the service container component.

In this embodiment, after the second virtual platform and the second virtual platform receive the task, according to the task received by the first virtual platform and/or the second virtual platform, the physical machine component, the virtual machine component, and the first internet access component of the service virtualization component are logically associated and/or the container node component, the one or more container components, and/or the second internet access component of the service containerization component are logically associated, respectively, where the service virtualization component and the service containerization component are independent from each other when being arranged. In this embodiment, the network component and the middleware component of the common component are listed separately, and when service deployment is performed, the service virtualization component and the service containerization component may share the common component, and the purpose of multi-party interaction is achieved by logically associating the network component and the middleware component of the common component with a physical machine component, a virtual machine component and a first portal component in the service virtualization component and/or with a container node component, one or more container components and a second portal component of the service containerization component. The method for arranging service mixing in the embodiment can solve the problem that the service mixing arrangement cannot be realized because the pages, modes and network element components of the service arrangement of the first virtual platform for service virtualization and the second virtual platform for service containerization are not consistent.

Optionally, on the basis of another embodiment provided by the present invention, the service virtualization component may further implement a host-standby dual-machine service and/or a service self-healing service. At this time, the service virtualization component includes, in addition to: the service virtualization component can further comprise: the system comprises a main and standby dual-computer assembly and/or a service self-healing assembly, wherein the main and standby dual-computer assembly and/or the service self-healing assembly are service assemblies. The main/standby dual-computer component is used for providing main/standby dual-computer service for the virtual machine component or the container node component, and the main/standby dual-computer component can better ensure service deployment capability through the cooperation of the main computer and the standby computer. The service self-healing component is used for service self-healing service for the main and standby dual-machine components and/or the service self-healing component, when failure faults occur, the service self-healing component does not need human intervention, can automatically recover carried services from the failure faults in a short time, and can also better ensure service deployment capacity.

At this time, performing logical association on one or more components in the service virtualization component corresponding to the first virtual platform, further includes:

performing logical association between a main/standby dual-machine component of the service virtualization component and a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing main/standby dual-machine service for the service virtualization component or the service containerization component through the main/standby dual-machine component of the service virtualization component; and/or

And logically associating the service self-healing component of the service virtualization component with a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing service self-healing service for the service virtualization component or the service containerization component through the service self-healing component of the service virtualization component.

Optionally, on the basis of another embodiment provided by the present invention, the service containerization component may further include: and one or more container port components corresponding to the one or more container components, and realizing reverse proxy for the one or more container components through the logical association of the one or more container port components and the second internet access component so that the one or more container components are communicated with the network bound by the network component.

At this time, performing logical association on one or more components in the service containerization component corresponding to the second virtual platform further includes:

Optionally, on the basis of another embodiment provided by the present invention, the common component may further include: the system comprises an application component, a load balancing component and/or an elastic telescopic component; the application component is used for binding the application software covered by the tenant authority corresponding to the service virtualization component, the service containerization component and/or the physical machine component in the software warehouse. The load balancing component is used for binding a specific load balancing scheme. The elastic telescopic assembly is used for setting an elastic telescopic strategy and needs to depend on the load balancing assembly.

At this time, logically associating one or more components of the common component with one or more components of the service virtualization components and/or one or more components of the service containerization components further includes:

Logically associating the load balancing component of the common component with the virtual machine component and/or the container node component, and carrying out load balancing on the service of the virtual machine component and/or the container node component through the load balancing component; and/or

And logically associating the elastic telescopic component of the common component with the virtual machine component and/or the container node component, wherein the elastic telescopic component of the common component is dependent on the load balancing component of the common component, and an elastic telescopic strategy of the service of the virtual machine component and/or the container node component is set through the elastic telescopic component of the common component.

To facilitate further understanding of the method of service mixing orchestration, a description is given below of how the method of service mixing orchestration is implemented under SDN (Software Defined Network).

For example, the first virtual platform is an Openstack virtual platform, and the second virtual platform is a kubernets virtual platform.

The Openstack virtual platform is an open-source cloud computing management platform, supports almost all types of cloud environments, and is a cloud computing management platform which is simple to implement, capable of being expanded in a large scale, rich and unified in standard.

The Kubernets virtual platform is an open-source container cluster management platform. On the basis of a Docker (an open source application container engine) technology, a series of complete functions such as deployment and operation, resource scheduling, service discovery, dynamic scaling and the like are provided for containerized application, and convenience in large-scale container cluster management is improved.

The Openstack virtual platform and the Kubernetes virtual platform operate based on an iROS platform (a unified cloud service platform). The iROS platform can provide centralized, flexible and high-reliability resources such as calculation, storage, network and the like, and can uniformly manage, distribute according to needs, rent out services and the like.

In order to solve the problem of service mixing arrangement of the Openstack virtual platform and the Openstack virtual platform, service arrangement pages of the Openstack virtual platform and a Kubernetes virtual platform need to be combined. The Openstack virtual platform arranges the ADT technology used by the service, the ADT technology is not consistent with the page, mode and network element assembly of the Kubernets virtual platform for arranging the service, and the ADT technology is in a table form, so that the service is not intuitive or inconvenient to bind and arrange.

Referring to fig. 3, a service virtualization component corresponding to the Openstack virtual platform includes: the system comprises a physical machine component, a VM component (or called as a virtual machine component), a first internet access component, a main/standby dual-machine component and a service self-healing component. The service containerization component corresponding to the Kubernetes virtual platform comprises: a Pod component (or referred to as a Container node component), one or more Container components (or referred to as Container components), a Nic component (or referred to as a second portal component), and one or more EndPoint components (or referred to as Container port components) corresponding to the one or more Container components. The common component includes: the system comprises a network component, a load balancing component, an elastic telescopic component, an application component and a middleware component.

The business mixing arrangement method mainly comprises the following steps:

step 1, combining the service virtualization components according to the actual service scene. The method specifically comprises the following steps:

and clicking the physical machine component, the VM component, the first network port component, the main/standby dual-machine component and the service self-healing component in sequence, binding the physical machine component and a physical machine managed under the virtualized data center respectively, binding the VM component and the mirror image warehouse, logically associating the first network port component and the VM component and setting a main/standby dual-machine and/or service self-healing mode.

Step 2: and combining the service containerization components according to the actual service scene. The method specifically comprises the following steps:

and clicking the Point component, the Container component, the EndPoint component and the Nic component in sequence, binding the Point component with a managed mirror warehouse under the virtualized data center to create a Container, carrying out logic association on the Container component and the EndPoint component, and carrying out logic association on the EndPoint component and the Nic component to preset reverse proxy.

And step 3: the method for combining the public components according to the actual service scene specifically comprises the following steps:

clicking the network component to bind each network covered by the tenant authority corresponding to the service virtualization component and/or the service containerization component in the network center; clicking a load balancing component to bind a specific load balancing scheme; the elastic telescopic component depends on the load balancing component, and an elastic telescopic strategy can be set by clicking the elastic telescopic component; clicking each application covered by the tenant authority corresponding to the service virtualization component and/or the service containerization component in the application component binding software warehouse; and clicking each middleware covered by the tenant permission corresponding to the service virtualization component and/or the service containerization component in the middleware component binding service market.

And 4, step 4: combining the common component with the service containerization component and/or the service virtualization component according to the actual service scene, specifically comprising:

clicking and dragging the first internet access component and/or the Nic component to generate a connection line, wherein the other end of the connection line can be logically associated with the arranged network component, so that the VM component and/or the Pod component are communicated with the network after deployment is completed; clicking and dragging the VM component, the physical machine component and/or the Pod component to generate a connecting line, wherein the other end of the connecting line allows logic to be associated with the programmed application component and the programmed middleware component, so that the VM component, the physical machine component and/or the Pod component interact with the middleware component; clicking and dragging the VM component and/or the Pod component generates a connection line, and the other end of the connection line allows logic to be associated to the arranged elastic telescopic component, so that the elastic telescopic strategy is effective.

And 5: creating a Container corresponding to a virtual machine and/or a Container component corresponding to the virtual machine component, and issuing a task for creating a VM component and/or a Pod component (or a Container component) associated network through an agent node according to an orchestration logic; after the task is completed, the agent node starts to transmit the application software to the VM component and/or the Pod component (specifically, the Container component) from the software warehouse for installation, and after the installation is completed, deployment of a load balancing scheme and an elastic expansion scheme can be performed; finally, the middleware component can interact with the middleware of the service market.

In this embodiment, the service virtualization component, the service containerization component, and the common component are uniformly configured with a jsplimb + avalon architecture, so that specific services can be patterned, logical association of each component can be realized by clicking and dragging a graph corresponding to each component to connect, and each component is intuitive and convenient to bind and deploy services.

Fig. 4 is a schematic structural diagram of a service mix orchestration apparatus according to an embodiment of the present invention, and referring to fig. 4, the service mix orchestration apparatus 400 includes: a first logical association module 401, a second logical association module 402, and a service deployment module 403.

The first logical association module 401 is configured to perform logical association on one or more components in a service virtualization component corresponding to a first virtual platform and/or perform logical association on one or more components in a service containerization component corresponding to a second virtual platform according to a service received by the first virtual platform for service virtualization and/or the second virtual platform for service containerization;

the second logical association module 402 is configured to logically associate one or more components of the common component with one or more components of the service virtualization components and/or one or more components of the service containerization components.

The service deployment module 403 is configured to deploy a service received by the first virtual platform and/or the second virtual platform according to a logical association of one or more components in service virtualization components and/or a logical association of one or more components in service containerization components, and a logical association of one or more components of a common component with one or more components in the service virtualization components and/or a logical association with one or more components in the service containerization components.

In another embodiment of the invention, the one or more components of the business virtualization component include at least: a physical machine component, a virtual machine component, and/or a first portal component. In this case, the first logical association module 401 includes: a first logical association unit, a second logical association unit, and/or a third logical association unit.

And the first logic association unit is used for logically associating the physical machine component of the service virtualization component with a physical machine.

And the second logic association unit is used for logically associating the virtual machine component in the service virtualization component with the mirror image warehouse, and creating the virtual machine corresponding to the virtual machine component in the service virtualization component through the first mirror image file acquired from the mirror image warehouse.

On the basis of another embodiment of the present invention, the service virtualization component may further include: the main/standby dual-machine component and/or the service self-healing component. In this case, the first logical association module 401 further includes: a fourth logical association unit and/or a fifth logical association unit.

The fourth logical association unit is configured to logically associate the active/standby dual-computer component of the service virtualization component with the virtual machine component of the service virtualization component or the container node component of the service containerization component, and provide an active/standby dual-computer service for the service virtualization component and/or the service containerization component through the active/standby dual-computer component of the service virtualization component.

In another embodiment of the invention, one or more of the components of the service containerization component include at least: a container node component, one or more container components, and/or a second portal component. In this case, the first logical association module 401 further includes: a sixth logical association unit and/or a seventh logical association unit.

The sixth logical association unit is configured to deploy, by a container node component of the service containerization component, one or more container components of the service containerization component to a same node of the container node components.

The seventh logical association unit is configured to logically associate one or more container components of the service containerization component with the mirror repository, and create a container corresponding to the one or more container components through a second mirror image file acquired from the mirror repository.

On the basis of another embodiment of the present invention, the service containerization component may further include: one or more container port assemblies corresponding to the one or more container assemblies. In this case, the first logic associating module 401 further includes: an eighth logical association unit and/or a ninth logical association unit.

The eighth logical association unit is configured to logically associate a container port component of the service containerization component with one or more container components of the service containerization component.

The ninth logical association unit is configured to logically associate a container port component of the service containerization component with a second portal component of the service containerization component, and perform reverse proxy on one or more container components through the container port component and the second portal component.

In another embodiment of the invention, one or more of the common components comprise at least: network components and/or middleware components. In this case, the second logical association module 402 includes: a tenth logical association unit and/or an eleventh logical unit.

The tenth logical association unit is configured to logically associate the network component of the common component with the first portal component of the service virtualization component and/or the second portal component of the service containerization component, and communicate the virtual machine component and/or the service containerization component with a network covered by tenant permissions corresponding to the virtual machine component and/or the container node component through the network component.

The eleventh logic unit is configured to logically associate a middleware component of the common component with the virtual machine component and/or the container node component, and logically associate the service virtualization component and/or the service containerization component with a middleware covered by a tenant right corresponding to the virtual machine component and/or the container node component in a service market through the middleware component of the common component.

On the basis of another embodiment of the present invention, the common component may further include: an application component, a load balancing component and/or an elastic telescopic component; in this case, the second logical association module 402 further includes: a twelfth logic unit, a thirteenth logic unit, and/or a fourteenth logic unit.

The twelfth logic unit is configured to logically associate the application component of the common component with the virtual machine component, the container node component, and/or the physical machine component, and acquire, by the application component of the common component, application software covered by tenant permissions corresponding to the service virtualization component, the service containerization component, and/or the physical machine component from a software repository connected to the application component of the common component.

The thirteenth logic unit is configured to logically associate the load balancing component of the common component with the virtual machine component and/or the container node component, and perform load balancing on services of the virtual machine component and/or the container node component through the load balancing component.

The fourteenth logic unit is configured to logically associate the elastic stretching component of the common component with the virtual machine component and/or the container node component, where the elastic stretching component of the common component relies on the load balancing component of the common component, and sets an elastic stretching policy for a service of the virtual machine component and/or the container node component through the elastic stretching component of the common component.

The device for service mix orchestration provided in this embodiment may execute the above method embodiments, and the implementation principle and technical effect are similar, which is not described herein again.

In this embodiment, after the second virtual platform and the second virtual platform receive the task, according to the task received by the first virtual platform and/or the second virtual platform, the first logical association module 401 respectively performs logical association on one or more components of the service virtualization component and/or one or more components of the service containerization component, where the service virtualization component and the service containerization component are independent from each other when being arranged. In this embodiment, the common components are listed individually, when service deployment is performed, the service virtualization component and the service containerization component may share the common component, and the second logical association module 402 performs logical association on one or more components of the common component with one or more components in the service virtualization component and/or one or more components in the service containerization component, so as to achieve the purpose of multi-party interaction. Through the cooperation of the first logic association module 401, the second logic association module 402 and the service deployment module 403, the method for service mixing and orchestration in this embodiment can solve the problem that service mixing and orchestration cannot be realized because the pages, modes and network element components of service orchestration of the first virtual platform for service virtualization and the second virtual platform for service containerization are not consistent.

Fig. 5 is a schematic structural diagram of a service mix orchestration apparatus according to another embodiment of the present invention. As shown in fig. 5, the apparatus 500 for orchestrating service mix shown in fig. 5 comprises: at least one processor 501, a memory 502. The various components in the service mix orchestration apparatus 500 are coupled together by a bus system 505. It is understood that the bus system 505 is used to enable connection communications between these components. The bus system 505 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 505 in FIG. 5.

It is to be understood that the memory 502 in embodiments of the present invention may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (ddr Data Rate SDRAM, ddr SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 502 of the subject systems and methods described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

In some embodiments, memory 502 stores elements, executable modules or data structures, or a subset or expanded set of them as follows: an operating system 5021 and application programs 5022.

The operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application 5022 includes various applications, such as a Media Player (Media Player), a Browser (Browser), and the like, for implementing various application services. A program for implementing the method according to the embodiment of the present invention may be included in the application program 5022.

In the embodiment of the present invention, the processor 501 may execute the service mixing orchestration method by calling a program or an instruction stored in the memory 502, specifically, a program or an instruction stored in the application 5022.

The method disclosed by the above-mentioned embodiments of the present invention may be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 501. The Processor 501 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the method in combination with the hardware.

It is to be understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the Processing units may be implemented within one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), general purpose processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.

For a software implementation, the techniques described in this disclosure may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described in this disclosure. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.

In this embodiment, the processor 501 is specifically configured to: according to the service received by a first virtual platform of service virtualization and/or a second virtual platform of service containerization, performing logic association on one or more components in service virtualization components corresponding to the first virtual platform and/or performing logic association on one or more components in service containerization components corresponding to the second virtual platform; logically associating one or more components of a common component with one or more of the business virtualization components and/or one or more of the business containerization components; deploying the service received by the first virtual platform and/or the second virtual platform according to the logic association of one or more components in the service virtualization components and/or the logic association of one or more components in the service containerization components, and the logic association of one or more components of the common components with one or more components in the service virtualization components and/or with one or more components in the service containerization components.

Optionally, the processor 501 is specifically configured to: logically associating a physical machine component of the service virtualization component with a physical machine; and/or logically associating a virtual machine component in the service virtualization component with a mirror image warehouse, and creating a virtual machine corresponding to the virtual machine component in the service virtualization component through a first mirror image file acquired from the mirror image warehouse; and logically associating the first internet access component of the service virtualization component with the virtual machine component of the service virtualization component.

Optionally, the processor 501 is specifically configured to: performing logical association on a main/standby dual-machine component of the service virtualization component and a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing main/standby dual-machine service for the service virtualization component and/or the service containerization component through the main/standby dual-machine component of the service virtualization component; and/or logically associating the service self-healing component of the service virtualization component with a virtual machine component of the service virtualization component or a container node component of the service containerization component, and providing service self-healing service for the service virtualization component and/or the service containerization component through the service self-healing component of the service virtualization component.

Optionally, the processor 501 is specifically configured to: deploying, by a container node component of the traffic containerization component, one or more container components of the traffic containerization component onto a same node of container node components; and logically associating one or more container components of the business containerization component with an image warehouse, and creating a container corresponding to the one or more container components through a second image file acquired from the image warehouse.

Optionally, the processor 501 is specifically configured to: logically associating a container port component of the service containerization component with one or more container components of a service containerization component; and logically associating the container port component of the service containerization component with a second internet access component of the service containerization component, and performing reverse proxy on one or more container components through the container port component and the second internet access component.

Optionally, the processor 501 is specifically configured to: the network component of the public component is logically associated with the first internet access component of the service virtualization component and/or the second internet access component of the service containerization component, and the virtual machine component and/or the service containerization component are respectively communicated with the network covered by the tenant permission corresponding to the virtual machine component and/or the container node component through the network component; and logically associating the middleware component of the common component with the virtual machine component and/or the container node component, and logically associating the service virtualization component and/or the service containerization component with the middleware covered by the tenant authority corresponding to the virtual machine component and/or the container node component in the service market through the middleware component of the common component.

Optionally, the processor 501 is specifically configured to: logically associating the application component of the common component with the virtual machine component, the container node component and/or the physical machine component, and acquiring application software covered by tenant permissions corresponding to the service virtualization component, the service containerization component and/or the physical machine component from a software warehouse connected with the application component of the common component through the application component of the common component; and/or logically associating the load balancing component of the common component with the virtual machine component and/or the container node component, and carrying out load balancing on the traffic of the virtual machine component and/or the container node component through the load balancing component; and/or logically associating the elastic expansion component of the common component with the virtual machine component and/or the container node component, wherein the elastic expansion component of the common component is dependent on the load balancing component of the common component, and an elastic expansion strategy of the service of the virtual machine component and/or the container node component is set through the elastic expansion component of the common component.

The service mixing and arranging device provided by the embodiment of the present invention respectively performs logical association on one or more components of the service virtualization component and/or one or more components of the service containerization component through the processor 501, wherein the service virtualization component and the service containerization component are independent from each other when being arranged. In this embodiment, the common component is listed separately, and when service deployment is performed, the service virtualization component and the service containerization component may share the common component, and the processor 501 performs logical association on one or more components of the common component with one or more components in the service virtualization component and/or one or more components in the service containerization component, so as to achieve the purpose of multi-party interaction. The device for service mixing and arranging in the embodiment can solve the problem that service mixing and arranging cannot be realized on the two virtual platforms because the page, mode and network element components of service arranging of the first virtual platform for service virtualization and the second virtual platform for service containerization are not consistent.

Furthermore, the service virtualization component, the service containerization component and the public component can be uniformly in a jsPlumb + avalon architecture, so that specific services can be patterned, the logic association of each component can be realized by clicking and dragging the graph corresponding to each component to connect, and each component is visual and convenient to bind and deploy services.

An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps in the method for service mix orchestration as described above.

It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

In the embodiments provided herein, it should be understood that "B corresponding to a" means that B is associated with a from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also be determined from a and/or other information.

In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network-side device) to perform some steps of the transceiving method according to various embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A method for orchestration of a mix of services, the method comprising:

performing logic association on one or more components in a service virtualization component corresponding to a first virtual platform and/or performing logic association on one or more components in a service containerization component corresponding to a second virtual platform according to a service received by the first virtual platform for service virtualization and/or the second virtual platform for service containerization;

deploying the service received by the first virtual platform and/or the second virtual platform according to the logic association of one or more components in the service virtualization components and/or the logic association of one or more components in the service container components, and the logic association of one or more components of the common components with one or more components in the service virtualization components and/or with one or more components in the service container components.

2. The method of claim 1, wherein the one or more components of the business virtualization component comprise at least: a physical machine component, a virtual machine component and/or a first portal component;

3. The method of claim 2, wherein the traffic virtualization component further comprises: the main and standby dual-machine components and/or the service self-healing component;

4. The method of claim 2, wherein one or more of the service containerization components include at least: a container node component, one or more container components, and/or a second portal component;

5. The method of claim 4, wherein the traffic containerization component further comprises: one or more container port assemblies corresponding to the one or more container assemblies;

logically associating one or more of the business containerization components corresponding to the second virtual platform, further comprising:

6. The method of claim 4, wherein one or more of the common components comprises at least: network components and/or middleware components;

and logically associating the middleware component of the common component with the virtual machine component and/or the container node component, and logically associating the service virtualization component and/or the service containerization component with the middleware covered by the tenant authority corresponding to the virtual machine component and/or the container node component in the service market through the middleware component of the common component.

7. The method of claim 4, wherein the common component further comprises: an application component, a load balancing component and/or an elastic telescopic component;

logically associating the application component of the common component with the virtual machine component, the container node component and/or the physical machine component, and acquiring application software covered by tenant permission corresponding to the service virtualization component, the service containerization component and/or the physical machine component from a software warehouse connected with the application component of the common component through the application component of the common component; and/or

8. An apparatus for orchestration of a mix of services, the apparatus comprising:

9. The apparatus of claim 8, wherein the one or more components of the traffic virtualization component comprise at least: a physical machine component, a virtual machine component and/or a first portal component;

the first logical association module comprising:

10. The apparatus of claim 9, wherein the traffic virtualization component further comprises: the main and standby dual-machine components and/or the service self-healing component;

the first logical association module further comprises:

a fourth logical association unit, configured to logically associate a primary and secondary machine component of the service virtualization component with a virtual machine component of the service virtualization component or a container node component of the service containerization component, and provide primary and secondary machine services for the service virtualization component and/or the service containerization component through the primary and secondary machine component of the service virtualization component; and/or

11. The apparatus of claim 9, wherein one or more of the components of the traffic containerization component comprise at least: a container node component, one or more container components, and/or a second portal component;

the first logical association module further comprises:

a sixth logical association unit, configured to deploy, by a container node component of the service containerization component, one or more container components of the service containerization component onto a same node of container node components;

and the seventh logical association unit is used for logically associating one or more container components of the business containerization component with the mirror image warehouse and creating a container corresponding to the one or more container components through a second mirror image file acquired from the mirror image warehouse.

12. The apparatus of claim 11, wherein the traffic containerization component further comprises: one or more container port assemblies corresponding to the one or more container assemblies;

the first logical association module further comprises:

13. The apparatus of claim 11, wherein one or more of the common components comprise at least: network components and/or middleware components;

the second logical association module comprises:

a tenth logical association unit, configured to logically associate the network component of the common component with the first portal component of the service virtualization component and/or the second portal component of the service containerization component, and communicate, through the network component, the virtual machine component and/or the service containerization component with a network covered by tenant permissions corresponding to the virtual machine component and/or the container node component, respectively;

14. The apparatus of claim 11, wherein the common component further comprises: an application component, a load balancing component and/or an elastic telescopic component;

the second logical association module further comprises:

A thirteenth logic unit, configured to logically associate a load balancing component of the common component with the virtual machine component and/or the container node component, and load balance a service of the virtual machine component and/or the container node component through the load balancing component; and/or

15. An apparatus for service mix orchestration, comprising: memory, processor and computer program stored on the memory and executable on the processor, the processor implementing the steps in the method of service mix orchestration according to any of claims 1-7 when executing the program.

16. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of a method of service mix orchestration according to any one of claims 1-7.