CN109815034B - Engineering software resource cloud service method - Google Patents
Engineering software resource cloud service method Download PDFInfo
- Publication number
- CN109815034B CN109815034B CN201910070989.6A CN201910070989A CN109815034B CN 109815034 B CN109815034 B CN 109815034B CN 201910070989 A CN201910070989 A CN 201910070989A CN 109815034 B CN109815034 B CN 109815034B
- Authority
- CN
- China
- Prior art keywords
- engineering software
- service
- scheduling
- engineering
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 131
- 230000008569 process Effects 0.000 claims description 45
- 230000007246 mechanism Effects 0.000 claims description 27
- 230000003993 interaction Effects 0.000 claims description 26
- 230000002452 interceptive effect Effects 0.000 claims description 25
- 238000012544 monitoring process Methods 0.000 claims description 18
- 238000004806 packaging method and process Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 12
- 238000011084 recovery Methods 0.000 claims description 8
- 238000010276 construction Methods 0.000 claims description 6
- 238000012217 deletion Methods 0.000 claims description 5
- 230000037430 deletion Effects 0.000 claims description 5
- 238000012800 visualization Methods 0.000 claims description 5
- 238000013475 authorization Methods 0.000 claims description 4
- 230000001419 dependent effect Effects 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 3
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000004075 alteration Effects 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides an engineering software resource cloud service method. The method comprises the following steps: establishing an engineering software operating environment mirror image; adding the engineering software into a sharable template, and creating an engineering software instance to isolate the engineering software; establishing engineering software service and scheduling subsystems in a classified manner; and establishing an engineering software service directory by classification to form a flow from engineering software resource request to revocation. The method and the device establish the engineering software running environment mirror image, add the engineering software into the sharable template, establish the engineering software instance, establish the engineering software service and the scheduling subsystem in a classified mode, establish the engineering software service catalog in a classified mode, form the flow from the engineering software resource request to the cancellation, and solve the cloud service problems caused by various architectures, different deployment modes, different use modes and the like of the engineering software.
Description
Technical Field
The application relates to the technical field of cloud, in particular to a cloud service method for engineering software resources.
Background
For the Web application of business scenes such as business, management and the like, a B/S software development framework is generally adopted, the unified deployment environment of service containers such as Tomcat and the like is relied on, and the method is based on the use mode of a browser, so that the individual configuration (page, database and multiple instances) and elastic expansion (dynamic expansion of a server and the service containers) of the multi-tenant cloud service are easily realized.
In contrast, the engineering software has various architectures, different deployment methods and different use modes. For example, the development framework of engineering software includes a standalone version, a client/server version, and a distributed version, and the distributed version can be further subdivided into a framework based on MPI (Message paging Interface)/OpenMP (a cross-platform, more commonly-used parallel programming model based on a shared memory (address space)), HLA (High Level Architecture)/RTI (Run-Time Interface), and the like; the deployment environment of the engineering software is various, and the deployment environment of the client/server version and the distributed version of the engineering software is complex and the deployment process is complicated; the engineering software has different use modes, namely a bounded surface interaction use mode (which can be divided into a local use mode and a cloud use mode), an interface calling use mode, a distributed interaction use mode, an embedded flow use mode and the like. Due to the characteristics of various architectures, different deployment methods, different use modes and the like of the engineering software, the cloud service of the engineering software is difficult to provide.
Disclosure of Invention
In order to solve one of the problems, the application provides an engineering software resource cloud service method.
Establishing an engineering software operating environment mirror image;
adding engineering software into a sharable template, and creating an engineering software instance to isolate the engineering software;
establishing engineering software service and scheduling subsystems in a classified manner;
and establishing an engineering software service directory by classification to form a flow from engineering software resource request to revocation.
The establishing of the engineering software running environment mirror image comprises the following steps:
determining the engineering software dependent resources, wherein the engineering software dependent resources comprise one or more of the following: operating system, middleware, configuration items, adapters;
and packaging the resources depended by the engineering software.
Wherein encapsulating the resources on which the engineering software depends comprises one or more of the following:
packaging the resources depended by the engineering software to a virtual machine template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes;
packaging the resources depended by the engineering software to a lightweight container template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes;
and packaging the resources depended by the engineering software into a physical configuration file so as to quickly guide out an engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes.
Wherein the sharable template is one or more of: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file;
adding the engineering software into the sharable template comprises the following steps:
and installing the engineering software into one or more of the following items for sharing: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file.
Wherein, the creating engineering software instance comprises:
and configuring and providing an engineering software instantiation interface, starting an engineering software instance while quickly forming a virtualized engineering software operating environment, monitoring the operating state of the engineering software instance, and closing the engineering software after the use is finished.
Wherein, after the creating of the engineering software instance, the method further comprises:
providing an engineering software instance handle to enable a client/server framework engineering software background server instance to be communicated with a foreground client, wherein the instance handle is a Web Service address or a Remote Procedure Call (RPC) handle;
and providing engineering software distribution instantiation based on a distributed framework so as to realize the intercommunication of distributed modules of the engineering software based on middleware.
The classified building of the engineering software service and scheduling subsystem comprises the following steps:
determining a use mode of the engineering software, wherein the use mode comprises one or more of the following modes: the method comprises the following steps of (1) an interface interaction local use mode, an interface interaction cloud use mode, an interface calling use mode, a distribution interaction use mode and an embedded flow use mode;
and establishing an engineering software service and scheduling subsystem by adopting a service and scheduling method according to the using mode.
Wherein the service and scheduling includes one or more of: license service and scheduling, application remote interactive service and scheduling, job batch processing service and scheduling, remote process calling service and scheduling, distributed interactive service and scheduling, and flow calling service and scheduling;
the method for adopting service and scheduling establishes an engineering software service and scheduling subsystem, which comprises one or more of the following steps:
the method comprises the steps of adopting a license service and scheduling method, establishing an engineering software service, a scheduling subsystem, adopting an application remote interactive service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a job batch processing service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a remote process calling service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a distributed interactive service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a process calling service and scheduling method, and establishing the engineering software service and the scheduling subsystem.
The method for establishing the engineering software service and scheduling subsystem by adopting the license service and scheduling comprises the following steps:
providing engineering software license authentication and authorization service to a foreground;
after the engineering software is used in a foreground local interface interaction mode, license resource pool management and license scheduling are established in a background;
the method for establishing the engineering software service and scheduling subsystem by adopting the application remote interactive service and scheduling comprises the following steps:
pushing an interface of the engineering software to a foreground by adopting a virtual network console and/or Windows RDP (remote desktop protocol) so that the engineering software is used by the foreground in an interactive mode;
establishing a second scheduling mechanism in the background so as to open isolated engineering software at different graphic workstations;
the method for establishing the engineering software service and scheduling subsystem by adopting the job batch processing service and scheduling comprises the following steps:
determining a file corresponding to the operation;
dispatching the file to a plurality of computing nodes of a high-performance cluster at a background, and starting computing analysis;
after a third scheduling mechanism is established in the background, the foreground carries out job submission, process monitoring and result acquisition through a page so as to open isolated engineering software on the computing nodes of the high-performance cluster with the required number;
the method for establishing the engineering software service and scheduling subsystem by adopting the remote process call service and scheduling comprises the following steps:
providing services for a remote process call service interface of engineering software through discovery operation, locking operation and call operation;
after a fourth scheduling mechanism is established in the background, the engineering software is used in the foreground through a page or a client program, so that isolated engineering software instances are selected at a computing node of a high-performance cluster for deploying the engineering software;
the method for establishing the engineering software service and scheduling subsystem by adopting the distributed interactive service and scheduling method comprises the following steps:
packaging engineering software into a federal member meeting high-level architecture HLA specifications;
after a fifth scheduling mechanism is established in the background, the federate adds an HLA operation support frame RTI for distribution interaction so as to assign engineering software for the federate and distribute computing nodes for the assigned isolated engineering software;
the method for establishing the engineering software service and scheduling subsystem by adopting the flow call service and scheduling method comprises the following steps:
making the calling of the engineering software into a template embedding flow;
after the sixth scheduling mechanism is established in the background, in the running process of the template embedding process, the engineering software is used in an automatic or manual template calling mode, and the fifth scheduling mechanism is established in the background so as to assign the engineering software for the template and assign the computing nodes for the assigned isolated engineering software.
Wherein, the classifying establishes an engineering software service directory to form a process from engineering software resource request to revocation, which comprises:
establishing an engineering software service directory according to a using mode;
when the engineering software under the service directory is triggered, entering a complete process of the full life cycle of the engineering software service, wherein the complete process of the full life cycle of the engineering software service comprises the following steps: resource request, operation environment construction, software instantiation, task file submission, software starting, software use, software closing, task file deletion, instantiation revocation, operation environment revocation and resource recovery;
and providing a background monitoring means and a distributed cooperation means for the engineering software and the distributed engineering software which are positioned in the background, wherein the background monitoring means comprises a message mechanism and desktop visualization.
According to the technical scheme, an engineering software running environment mirror image is established, engineering software is added into a sharable template, an engineering software instance is established, engineering software services and a scheduling subsystem are established in a classified mode, an engineering software service directory is established in a classified mode, so that a process from engineering software resource request to cancellation is formed, and the cloud service problems caused by various architectures, different deployment methods, different use modes and the like of the engineering software can be solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a flowchart illustrating a method for cloud services of engineering software resources according to an embodiment of the present invention;
fig. 2 shows an architecture diagram obtained by an engineering software resource cloud service method according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions and advantages of the embodiments of the present application more apparent, the following further detailed description of the exemplary embodiments of the present application with reference to the accompanying drawings makes it clear that the described embodiments are only a part of the embodiments of the present application, and are not exhaustive of all embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
The engineering software resource cloud service method is a universal solution, engineering software of a single machine version, a client/server version and a distributed version can be uniformly deployed in a prepared running environment mirror image, engineering software instances are created as required, a multi-tenant cloud service which is isolated from each other and personalized can be effectively accessed and used, and elastic expansion and flexible and scheduling of occupied resources can be realized according to application requirements.
Example 1
The embodiment provides an engineering software resource cloud service method, and refer to fig. 1.
And S101, establishing an engineering software running environment mirror image.
The specific implementation process of the step can be as follows:
step 1.1, determining resources on which the engineering software depends.
The resources on which the engineering software depends comprise one or more of the following: operating system, middleware, configuration items, adapters.
And step 1.2, packaging resources depended by the engineering software.
Wherein, packaging the resources on which the engineering software depends comprises one or more of the following ways:
and packaging resources depended by the engineering software into a virtual machine template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes.
And packaging resources depended by the engineering software into the lightweight container template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes.
And packaging the resources depended by the engineering software into a physical configuration file so as to quickly guide out the engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes.
For example: aiming at various frameworks of single-machine version, client/server version, distributed version and the like of the engineering software, a computing system virtualization technology is adopted to uniformly establish an operating environment for the engineering software.
The operating system, the middleware, the configuration items, the adapters and the like which are depended by the engineering software are encapsulated into the virtual machine template, so that the virtualized engineering software running environment is supported to be quickly formed on a set of specified computing nodes, and the revocation and the recovery of the computing nodes of the running environment are supported.
The operating system, the middleware, the configuration items, the adapters and the like which are depended by the engineering software are packaged into the lightweight container template, the virtualized engineering software running environment is supported to be quickly formed on a set of specified computing nodes, and the withdrawal of the running environment and the recovery of the computing nodes are supported.
The operating system, the middleware, the configuration items, the adapters and the like which are depended by the engineering software are encapsulated into the configuration file, the required engineering software running environment is guided out quickly on a set of specified computing nodes, and the revocation and the recovery of the running environment are supported.
By executing the step, the computing system virtualization technology can be used for preparing the running environment mirror image for the engineering software. Specifically, aiming at various frameworks of a stand-alone version, a client/server version, a distributed version and the like of engineering software, a computing system virtualization technology is adopted to uniformly establish an operating environment for the engineering software, an operating system, middleware, configuration items, adapters and the like which are depended by the engineering software are packaged into a virtual machine template, a lightweight container template or a configuration file, a virtualized engineering software operating environment is supported to be quickly formed on a specified group of computing nodes or a required engineering software operating environment is quickly guided out, and revocation and recovery of the operating environment are supported.
S102, adding the engineering software into the sharable template, and creating an engineering software instance to isolate the engineering software.
Wherein, the sharable template is one or more of the following: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file.
Adding engineering software to a shareable template, comprising:
and installing the engineering software into one or more of the following items for sharing: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file.
Specific implementation processes for creating engineering software instances include, but are not limited to:
and configuring and providing an engineering software instantiation interface, starting an engineering software instance while quickly forming a virtualized engineering software operating environment, monitoring the operating state of the engineering software instance, and closing the engineering software after the use is finished.
For example: the engineering software is installed in a virtual machine template for sharing, an engineering software instantiation interface is configured and provided, the engineering software instance is started while an isolated engineering software running environment is quickly established, the monitoring of the running state of the engineering software instance is supported, and the closing of the engineering software is supported.
The engineering software is installed in a lightweight container template for sharing, an engineering software instantiation interface is configured and provided, the engineering software instance is started while an isolated engineering software running environment is quickly established, the monitoring of the running state of the engineering software instance is supported, and the closing of the engineering software is supported.
The engineering software is installed in a shared storage for sharing, an engineering software instantiation interface is configured and provided, the engineering software instance is started while an isolated engineering software running environment is quickly constructed, the monitoring of the running state of the engineering software instance is supported, and the closing of the engineering software is supported.
In addition, after the engineering software instance is created, an engineering software instance handle can be provided, so that the client/server framework engineering software background server instance is communicated with the foreground client, and the instance handle is a Web Service (Web Service) address or a Remote Procedure Call (RPC) handle. And providing engineering software distribution instantiation based on a distributed framework so as to realize the intercommunication of distributed modules of the engineering software based on middleware.
For example: providing engineering software instance handles (Web Service addresses or various RPC handles) to realize communication between a background server instance and a foreground client of the client/server framework engineering software; and providing distributed instantiation of the engineering software based on a distributed framework, and realizing mutual communication of all distributed modules of the engineering software based on middleware such as MPI/OpenMP, HLA RTI and the like.
By executing the steps, the engineering software can be installed into a sharable template and an address, and engineering software instances can be created as required. Specifically, the engineering software is installed in a virtual machine template, a lightweight container template, and shared, or installed in shared storage. And configuring and providing an engineering software instantiation interface, supporting the quick construction of an isolated engineering software running environment and simultaneously starting an engineering software instance, supporting the monitoring of the running state of the engineering software instance and supporting the closing of the engineering software. Providing an engineering software instance handle to realize communication between a background server instance and a foreground client of the client/server framework engineering software; and providing distributed instantiation of the distributed framework engineering software, and communicating the distributed instantiation with the distributed framework engineering software.
S103, establishing engineering software service and scheduling subsystems in a classified mode.
The specific implementation process of the step can be as follows:
and 2.1, determining the use mode of the engineering software.
Wherein, the use mode comprises one or more of the following modes: the method comprises the following steps of interface interaction local using mode, interface interaction cloud using mode, interface calling using mode, distribution interaction using mode and embedding flow using mode.
And 2.2, establishing an engineering software service and scheduling subsystem by adopting a service and scheduling method according to the using mode.
Wherein the service and scheduling includes one or more of: license service and scheduling, application remote interactive service and scheduling, job batch processing service and scheduling, remote procedure call service and scheduling, distributed interactive service and scheduling, and flow call service and scheduling.
The implementation process of establishing engineering software service and scheduling subsystem by using the service and scheduling method comprises one or more of the following steps: the method comprises the steps of adopting a license service and scheduling method, establishing an engineering software service, a scheduling subsystem, adopting an application remote interactive service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a job batch processing service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a remote process calling service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a distributed interactive service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a process calling service and scheduling method, and establishing the engineering software service and the scheduling subsystem.
In particular, the method comprises the following steps of,
adopting the method of license service and scheduling, establishing an implementation manner of the engineering software service and scheduling subsystem, including:
providing engineering software license authentication and authorization service to a foreground;
and after the engineering software is used in a foreground local interface interaction mode, establishing a license resource pool for managing and scheduling the license in a background.
Adopting a method of applying remote interactive service and scheduling to establish an implementation mode of engineering software service and scheduling subsystem, the implementation mode includes:
pushing an interface of the engineering software to a foreground by adopting a VNC (Virtual Network controller) and/or a Windows RDP (Remote Desktop Protocol) so that the engineering software is used by the foreground in an interactive mode;
a second scheduling mechanism (e.g., a license scheduling mechanism) is established in the background to open isolated engineering software at a different graphics workstation.
The method for establishing the engineering software service and scheduling subsystem by adopting the job batch processing service and scheduling comprises the following implementation modes:
determining a file corresponding to the operation;
dispatching the files to a plurality of computing nodes of a background high-performance cluster, and starting computing analysis;
and a third scheduling mechanism is established in the background, and the foreground carries out job submission, process monitoring and result acquisition through pages so as to open isolated engineering software on the computing nodes of the high-performance cluster with the required number.
The method for establishing the engineering software service and scheduling subsystem by using remote procedure call service (RPC) and scheduling is implemented as follows:
providing services for a remote process call service interface of engineering software through discovery operation, locking operation and call operation;
after the fourth scheduling mechanism is established in the background, the engineering software is used in the foreground through a page or a client program to select isolated engineering software instances at the compute nodes of the high-performance cluster where the engineering software is deployed.
The implementation mode of establishing engineering software service and scheduling subsystem by adopting the method of distributed interactive service and scheduling is as follows:
packaging engineering software into a federal member meeting HLA specifications;
and after a fifth scheduling mechanism is established in the background, the federates join the HLA RTI for distribution interaction so as to appoint engineering software for the federates and distribute computing nodes for the appointed isolated engineering software.
The method for calling service and scheduling by adopting the flow is adopted, and the implementation mode for establishing engineering software service and scheduling subsystems is as follows:
making the calling of the engineering software into a template embedding flow;
after the sixth scheduling mechanism is established in the background, in the running process of the template embedding process, the engineering software is used in an automatic or manual template calling mode so as to assign the engineering software for the template and assign the computing nodes for the assigned isolated engineering software.
For example: aiming at various use modes such as an engineering software interface interactive use mode (which can be subdivided into a local use mode and a cloud use mode), an interface call use mode, a distributed interactive use mode, an embedded flow use mode and the like, different means such as license service and scheduling, application remote interactive service and scheduling, job batch processing service and scheduling, RPC service and scheduling, distributed interactive service and scheduling, flow call service and scheduling and the like are adopted, and engineering software service and scheduling subsystems are respectively established.
Wherein,
the license service and scheduling are license authentication and authorization service provided for engineering software on a local desktop of an engineer, the engineer uses the engineering software locally in an interface interaction mode, and a background establishes a license resource pool to manage and schedule the license.
The application of remote interactive service and scheduling is to push the interface of the engineering software managed by the background to the foreground desktop by adopting VNC and Windows RDP protocols for interactive use of engineers, and the background establishes a scheduling mechanism to open and effectively isolate the engineering software on different graphic workstations.
The operation batch processing service and scheduling is to schedule corresponding files to a plurality of computing nodes of a high-performance cluster at a background to start computing analysis, an engineer submits operation, monitors the process and obtains results through pages at the foreground, and the background establishes a scheduling mechanism to distribute engineering software to the computing nodes of the high-performance cluster and effectively isolate the engineering software.
The RPC service and scheduling are that RPC interfaces of engineering software provide services through operations such as discovery, locking, calling and the like, engineers use the RPC interfaces through pages or client programs in the foreground, and a scheduling mechanism is established in the background to distribute the engineering software to computing nodes of a high-performance cluster and effectively isolate the engineering software.
The distributed interaction service and scheduling are realized by packaging engineering software into federal members meeting HLA specifications, operating the federal members by (a plurality of) engineers on an operation management interface, adding HLARTI to realize distributed interaction, and establishing a scheduling mechanism in a background to assign corresponding engineering software for the federal members and distribute computing nodes for isolated use.
The flow calling service and scheduling are to make the calling of the engineering software into a template embedding flow, the (multiple) engineers automatically or manually call the template to use the engineering software in the running process of the flow, and the background establishes a scheduling mechanism to specify the corresponding engineering software for the template and distribute the computing nodes for the template to be used in an isolation way.
By executing the steps, the engineering software service and scheduling subsystems can be established in a classified mode according to different using modes. Specifically, different means such as license service and scheduling, application remote interaction service and scheduling, job batch processing service and scheduling, RPC service and scheduling, distribution interaction service and scheduling, flow calling service and scheduling and the like are adopted for multiple use modes such as an engineering software interface interaction use mode (which can be subdivided into a local use mode and a cloud use mode), an interface calling use mode, a distribution interaction use mode, an embedded flow use mode and the like, and engineering software service and scheduling subsystems are respectively established.
And S104, establishing an engineering software service directory in a classified manner to form a process from engineering software resource request to revocation.
This step can be implemented as follows:
and 3.1, establishing an engineering software service directory according to the using mode.
And 3.2, entering a complete process of the full life cycle of the engineering software service after the engineering software in the service directory is triggered.
The complete process of the full life cycle of the engineering software service comprises the following steps: resource request, operation environment construction, software instantiation, task file submission, software startup, software use, software shutdown, task file deletion, instantiation revocation, operation environment revocation and resource reclamation.
And 3.3, providing a background monitoring means and a distributed cooperation means for the engineering software and the distributed engineering software which are positioned in the background, wherein the background monitoring means comprises a message mechanism and desktop visualization.
For example: establishing an engineering software service directory according to different classifications of using modes, clicking specific engineering software under the service directory, and entering a complete process of a full life cycle of engineering software service, wherein the complete process comprises resource request, operation environment construction, software instantiation, task file submission, software starting, software using, software closing, task file deletion, instantiation revocation, operation environment revocation and resource recovery. Aiming at background use engineering software and distributed use engineering software, background monitoring means and distributed cooperation means including a message mechanism, desktop visualization and the like are provided.
By executing the steps, the engineering software service directory can be established in a classified mode, and a complete process from resource request to revocation is formed. Specifically, an engineering software service directory is established according to different classifications of using modes, specific engineering software under the service directory is clicked, and a complete process of the full life cycle of the engineering software service is entered, wherein the complete process comprises resource request, operation environment construction, software instantiation, task file submission, software startup, software use, software shutdown, task file deletion, instantiation revocation, operation environment revocation and resource recovery. Aiming at background use engineering software and distributed use engineering software, background monitoring means and distributed cooperation means including a message mechanism, desktop visualization and the like are provided.
The architecture obtained by the engineering software resource cloud service method provided by the embodiment can be as shown in fig. 2, the cloud service method of the software resource is expanded, a generalized solution is formed for the cloud service problems caused by various architectures, different deployment methods, different use modes and the like of engineering software outside the Web application, engineering software of a single machine version, a client/server version and a distributed version can be uniformly deployed in a prepared running environment mirror image, engineering software instances are created as required, a multi-tenant cloud service which is isolated from each other and personalized can be formed, the access and the use can be effectively achieved, and meanwhile, the elastic expansion and contraction of occupied resources can be realized according to application requirements.
The method provided by the embodiment establishes the engineering software running environment mirror image, adds the engineering software into the sharable template, establishes the engineering software instance, establishes the engineering software service and the scheduling subsystem in a classified manner, establishes the engineering software service directory in a classified manner, forms the flow from the engineering software resource request to the revocation, and can solve the cloud service problem caused by various architectures, different deployment methods, different use modes and the like of the engineering software.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (7)
1. A method for engineering software resource cloud service, the method comprising:
establishing an engineering software operating environment mirror image;
adding engineering software into a sharable template, and creating an engineering software instance to isolate the engineering software;
establishing engineering software service and scheduling subsystems in a classified manner;
establishing an engineering software service directory in a classified mode to form a process from engineering software resource request to revocation;
wherein,
the classified building engineering software service and scheduling subsystem comprises:
determining a use mode of the engineering software, wherein the use mode comprises the following steps: the method comprises the following steps of (1) an interface interaction local use mode, an interface interaction cloud use mode, an interface calling use mode, a distribution interaction use mode and an embedded flow use mode;
according to the using mode, adopting a service and scheduling method to establish an engineering software service and scheduling subsystem;
wherein,
the servicing and scheduling, comprising: license service and scheduling, application remote interactive service and scheduling, job batch processing service and scheduling, remote process calling service and scheduling, distributed interactive service and scheduling, and flow calling service and scheduling;
the method for adopting service and scheduling to establish the engineering software service and scheduling subsystem comprises the following steps:
adopting a license service and scheduling method, establishing an engineering software service, a scheduling subsystem, adopting an application remote interaction service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a job batch processing service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a remote process calling service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a distributed interaction service and scheduling method, establishing the engineering software service, the scheduling subsystem, adopting a process calling service and scheduling method, and establishing the engineering software service and the scheduling subsystem;
wherein,
the method for establishing the engineering software service and scheduling subsystem by adopting the license service and scheduling comprises the following steps:
providing engineering software license authentication and authorization service to a foreground;
after the engineering software is used in a foreground local interface interaction mode, license resource pool management and license scheduling are established in a background;
the method for establishing the engineering software service and scheduling subsystem by adopting the application remote interactive service and scheduling comprises the following steps:
pushing an interface of the engineering software to a foreground by adopting a virtual network console and/or Windows RDP (remote desktop protocol) so that the engineering software is used by the foreground in an interactive mode;
establishing a second scheduling mechanism in the background so as to open isolated engineering software at different graphic workstations;
the method for establishing the engineering software service and scheduling subsystem by adopting the job batch processing service and scheduling comprises the following steps:
determining a file corresponding to the operation;
dispatching the file to a plurality of computing nodes of a high-performance cluster at a background, and starting computing analysis;
after a third scheduling mechanism is established in the background, the foreground carries out job submission, process monitoring and result acquisition through a page so as to open isolated engineering software on the computing nodes of the high-performance cluster with the required number;
the method for establishing the engineering software service and scheduling subsystem by adopting the remote process call service and scheduling comprises the following steps:
providing services for a remote process call service interface of engineering software through discovery operation, locking operation and call operation;
after a fourth scheduling mechanism is established in the background, the engineering software is used in the foreground through a page or a client program, so that isolated engineering software instances are selected at a computing node of a high-performance cluster for deploying the engineering software;
the method for establishing the engineering software service and scheduling subsystem by adopting the distributed interactive service and scheduling method comprises the following steps:
packaging engineering software into a federal member meeting high-level architecture HLA specifications;
after a fifth scheduling mechanism is established in the background, the federate adds an HLA operation support frame RTI for distribution interaction so as to assign engineering software for the federate and distribute computing nodes for the assigned isolated engineering software;
the method for establishing the engineering software service and scheduling subsystem by adopting the flow call service and scheduling method comprises the following steps:
making the calling of the engineering software into a template embedding flow;
after the sixth scheduling mechanism is established in the background, in the running process of the template embedding process, the engineering software is used in an automatic or manual template calling mode so as to assign the engineering software for the template and assign the computing nodes for the assigned isolated engineering software.
2. The method of claim 1, wherein the creating an engineering software runtime image comprises:
determining the engineering software dependent resources, wherein the engineering software dependent resources comprise one or more of the following: operating system, middleware, configuration items, adapters;
and packaging the resources depended by the engineering software.
3. The method of claim 2, wherein encapsulating the resources on which the engineering software depends comprises one or more of:
packaging the resources depended by the engineering software to a virtual machine template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes;
packaging the resources depended by the engineering software to a lightweight container template so as to quickly form a virtualized engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes;
and packaging the resources depended by the engineering software into a physical configuration file so as to quickly guide out an engineering software operating environment at any computing node, withdraw the operating environment and recover the computing nodes.
4. The method of claim 3, wherein the sharable template is one or more of: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file;
adding the engineering software into the sharable template comprises the following steps:
and installing the engineering software into one or more of the following items for sharing: the system comprises a virtual machine template, a lightweight container template and a physical machine configuration file.
5. The method of claim 4, wherein creating the engineering software instance comprises:
and configuring and providing an engineering software instantiation interface, starting an engineering software instance while quickly forming a virtualized engineering software operating environment, monitoring the operating state of the engineering software instance, and closing the engineering software after the use is finished.
6. The method of claim 5, wherein after creating the engineering software instance, further comprising:
providing an engineering software instance handle to enable a client/server framework engineering software background server instance to be communicated with a foreground client, wherein the instance handle is a Web Service address or a Remote Procedure Call (RPC) handle;
and providing engineering software distribution instantiation based on a distributed framework so as to realize the intercommunication of distributed modules of the engineering software based on middleware.
7. The method of claim 1, wherein the classifying creates an engineering software service directory to form a process from engineering software resource request to revocation, comprising:
establishing an engineering software service directory according to a using mode;
when the engineering software under the service directory is triggered, entering a complete process of the full life cycle of the engineering software service, wherein the complete process of the full life cycle of the engineering software service comprises the following steps: resource request, operation environment construction, software instantiation, task file submission, software starting, software use, software closing, task file deletion, instantiation revocation, operation environment revocation and resource recovery;
and providing a background monitoring means and a distributed cooperation means for the engineering software and the distributed engineering software which are positioned in the background, wherein the background monitoring means comprises a message mechanism and desktop visualization.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910070989.6A CN109815034B (en) | 2019-01-25 | 2019-01-25 | Engineering software resource cloud service method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910070989.6A CN109815034B (en) | 2019-01-25 | 2019-01-25 | Engineering software resource cloud service method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109815034A CN109815034A (en) | 2019-05-28 |
| CN109815034B true CN109815034B (en) | 2021-02-12 |
Family
ID=66604962
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910070989.6A Active CN109815034B (en) | 2019-01-25 | 2019-01-25 | Engineering software resource cloud service method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109815034B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825499B (en) * | 2020-01-13 | 2020-06-19 | 中软信息系统工程有限公司 | Method and device for realizing security isolation based on unified container cloud platform |
| CN112395736B (en) * | 2020-10-09 | 2023-07-07 | 北京仿真中心 | Parallel simulation job scheduling method of distributed interactive simulation system |
| CN113672351A (en) * | 2021-08-20 | 2021-11-19 | 中国建设银行股份有限公司 | Method and device for constructing cloud service |
| CN115550331A (en) * | 2022-09-19 | 2022-12-30 | 重庆新致金服信息技术有限公司 | Software service processing method, electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255934A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service publishing method, cloud service publishing interface message packet and cloud service broker |
| CN106200572A (en) * | 2016-06-29 | 2016-12-07 | 北京奇步自动化控制设备有限公司 | The flexible intelligence using cloud service platform makes method |
| CN109063309A (en) * | 2018-07-26 | 2018-12-21 | 武汉理工大学 | A kind of Parameterized Design System and method based on cloud platform |
| CN109116820A (en) * | 2018-08-30 | 2019-01-01 | 安徽维德工业自动化有限公司 | A kind of intelligent manufacturing system based on magnanimity cloud operational mode |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9565275B2 (en) * | 2012-02-09 | 2017-02-07 | Rockwell Automation Technologies, Inc. | Transformation of industrial data into useful cloud information |
| CN103902347B (en) * | 2012-12-24 | 2017-09-29 | 中国电信股份有限公司 | The dispositions method and system of dummy machine system |
| CN104850449A (en) * | 2015-05-05 | 2015-08-19 | 华为技术有限公司 | Method and apparatus for implementing system architecture |
| CN106897947A (en) * | 2017-01-04 | 2017-06-27 | 上海易谷网络科技有限公司 | A kind of multi-tenant service quick deployment method based on cloud platform |
| CN108667909A (en) * | 2018-04-16 | 2018-10-16 | 南京维拓科技股份有限公司 | Mix wound visitor's plateform system under cloud mode |
| CN108989466A (en) * | 2018-08-30 | 2018-12-11 | 共享智能铸造产业创新中心有限公司 | Industrial cloud platform management system |
-
2019
- 2019-01-25 CN CN201910070989.6A patent/CN109815034B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102255934A (en) * | 2010-05-20 | 2011-11-23 | 中兴通讯股份有限公司 | Cloud service publishing method, cloud service publishing interface message packet and cloud service broker |
| CN106200572A (en) * | 2016-06-29 | 2016-12-07 | 北京奇步自动化控制设备有限公司 | The flexible intelligence using cloud service platform makes method |
| CN109063309A (en) * | 2018-07-26 | 2018-12-21 | 武汉理工大学 | A kind of Parameterized Design System and method based on cloud platform |
| CN109116820A (en) * | 2018-08-30 | 2019-01-01 | 安徽维德工业自动化有限公司 | A kind of intelligent manufacturing system based on magnanimity cloud operational mode |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109815034A (en) | 2019-05-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3944082B1 (en) | Extending the kubernetes api in-process | |
| CN109815034B (en) | Engineering software resource cloud service method | |
| CN110795219B (en) | Resource scheduling method and system suitable for various computing frameworks | |
| CN108205463B (en) | Application lifecycle management system | |
| CN108829409B (en) | Distributed system rapid deployment method and system | |
| CN104813614B (en) | Asynchronous framework for IAAS management | |
| AU2018365860B2 (en) | Code module selection for device design | |
| US20200379794A1 (en) | Method for containerizing application on cloud platform | |
| US20160147558A1 (en) | Virtual machine disk image installation | |
| CN110658794B (en) | Manufacturing execution system | |
| US20130138818A1 (en) | Method for accessing an automation system and system operating according to the method | |
| CN110245003A (en) | A kind of machine learning uniprocessor algorithm arranging system and method | |
| EP3963447A1 (en) | Supervisory device with deployed independent application containers for automation control programs | |
| CN107479984A (en) | Message based distributed space data processing system | |
| CN115794659B (en) | Distributed parallel testing method, device, equipment and medium for CFD software | |
| CN113672240A (en) | Container-based multi-machine-room batch automatic deployment application method and system | |
| CN112395736A (en) | Parallel simulation job scheduling method of distributed interactive simulation system | |
| CN115344356A (en) | Distributed training system based on containerization realization and construction method thereof | |
| CN113568755A (en) | Distributed compilation system and distributed compilation method | |
| CN115033290A (en) | A method, device and terminal device for splitting microservices based on instruction set | |
| JP6792125B1 (en) | The edge system, the control method of the edge system, the computer program used to control the edge system, and the recording medium thereof. | |
| CN113312429A (en) | Intelligent contract management system, method, medium, and article in a blockchain | |
| CN115202821B (en) | Non-cloud native application programming method and system, electronic device and storage medium thereof | |
| CN114157569A (en) | Cluster system and construction method and construction device thereof | |
| KR102549159B1 (en) | Edge cloud building system and method for verification automation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |