CN101866286B - PaaS collaboration system based on semantic relatedness and method thereof - Google Patents

Abstract

The invention discloses a PaaS (Platform-as-a-Service) collaboration system based on semantic relatedness and a method thereof. The system comprises an engine layer, a service layer, a control layer and a resource layer. The control layer and the resource layer are the core of the invention. The control layer analyzes and maintains the semantic relatedness and carries out the collaborative management on the distributed asynchronous operation of a plurality of developers based on the semantic relatedness, calls the PaaS collaboration system based on semantic relatedness to carry out the resource subscription and notification, and controls the access permission of the developers. The resource layer realizes a virtual resource maintenance based on the space view of developers and the mapping from the virtual resource to a physical resource. The invention also provides a PaaS collaboration method based on semantic relatedness for analyzing, processing and notifying the semantic relatedness between different modules and codes maintained by a plurality of developers. The invention increases the efficiency and quality of the collaboration development work.

Description

A PaaS collaboration system and method based on semantic association

technical field

The present invention relates to the field of cloud computing, and more specifically, relates to a PaaS collaboration system and method based on semantic association.

Background technique

PaaS (Platform as a service) is an emerging business model that provides server platforms or development environments as services. It can provide enterprises with a middleware platform for customized research and development, covering databases and application servers. Users or enterprises can use PaaS to create, test and deploy applications and services without purchasing hardware and software, which saves money and manpower, and at the same time increases the number of resources utilized on the Web platform. Development teams distributed in different regions can jointly complete certain application and software development projects through the PaaS platform. Currently popular PaaS platforms include Google's AppEngine and Amazon's EC2, S3, SimpleDB, etc.

However, the current PaaS platform has insufficient support for collaborative work, mainly in the coding, testing and deployment phases of project development, and lacks semantic or logical correlation analysis between modules maintained by different developers and their corresponding codes and processing, which brings difficulties to collaborative development characterized by close dependencies. For example, when a user's requirement changes greatly, the update of the code will cause the corresponding dependent code module to generate an update requirement. Although some PaaS systems, such as App Engine, can cooperate with CVS and other technologies to carry out version control of development projects (that is, record the update history of global code), they do not support the validity check and maintenance of semantic associations between code modules, so they cannot fundamentally To solve the efficiency problem of collaborative development work.

Contents of the invention

Based on this, it is necessary to provide a PaaS collaboration system based on semantic association that can improve the efficiency of collaborative development.

A PaaS collaboration system based on semantic association, including an engine layer, a service layer, a control layer and a resource layer, the engine layer receives and parses Soap requests, and the server layer triggers corresponding Web services according to the received Soap requests, the The control layer parses and maintains the semantic association and coordinates the distributed asynchronous operations of multiple developers based on the semantic association, calls the PaaS collaboration method based on the semantic association for resource subscription and notification, and controls the access rights of the developers. The layer performs the maintenance of virtual resources based on the developer space view and the mapping of virtual resources to physical resources.

Preferably, the engine layer includes a Soap engine module for receiving and parsing Soap requests.

Preferably, the service layer includes a service pool, and the service pool includes Web services for processing developer code update and deployment.

Preferably, the control layer includes an operation controller, an association controller and a permission controller, the operation controller is used to process the developer's operation instructions, the association controller is used to resolve and maintain semantic associations, detect resource updates, and The semantic-based PaaS collaboration method is invoked for resource subscription and notification, and operations between developers are coordinated, and the authority controller is used to control the developer's access authority.

Further preferably, the operation controller includes a resource management module that maps resource operation instructions of developers, a resource debugging module that completes resource testing and functional joint debugging, and a resource deployment module that assists project release.

Further preferably, the association controller includes a semantic association management module and a semantic association monitoring module, the semantic association management module is used to analyze and maintain semantic associations between resources, construct and upgrade semantic association instances, and the semantic association monitoring module The module is used to detect resource updates, and the semantic association management module and the semantic association monitoring module call the PaaS collaboration method based on semantic association to perform resource subscription and notification.

Further preferably, the semantic association management module constructs and upgrades the semantic association instance according to the dependency relationship defined by the developer. The dependency relationship is a one-way relationship, which is divided into code modification dependency, interface update dependency and module deployment dependency. The constructed The semantic association instance of contains all association tuples, and each association tuple is defined as <x, y, R _x→y >, where x, y represent resources, and R _x→y represents the semantic association R from x to y, so The above semantic association is a one-way relationship, including code modification semantic association, interface update semantic association and module deployment semantic association.

Preferably, the semantic association monitoring module is further configured to call a resource subscription method based on semantic association to subscribe resources when the semantic association management module constructs or upgrades the semantic association instance, specifically: traversing all semantic association instances Association tuples, take out one of the association tuples Q: <x, y, R _x→y >, judge whether R is equal to the code modification semantic association, if so, add x to the code modification association subscription set of y, otherwise further judge R Whether it is equal to the interface update semantic association, if so, add x to the interface update association subscription set of y, otherwise further judge whether R is equal to the module deployment semantic association, if so, add x to the module deployment association subscription set of y, until all Associative tuples are processed. Among them, the code modification associated subscription set represents all resources that have been subscribed to resource p with code modification associated subscription; the interface update associated subscription set represents all resources that have performed interface update associated subscription on resource p; the module deployment associated subscription set represents all resources that have been associated with p. The resources associated with the module deployment subscription.

Preferably, the semantic association monitoring module is further configured to call a resource notification method based on semantic association for resource notification when a resource update is detected, specifically: generate a resource update operation set according to the received resource update operation, and take out the resource Update a resource in the operation set and its semantic association, judge whether the semantic association is a code modification semantic association and the code modification association subscription set of the resource is not empty, if so, execute the code modification association notification, otherwise further judge the semantic Whether the association is an interface update semantic association and the interface update association subscription set of the resource is not empty, if so, execute the interface update association notification, otherwise further judge whether the semantic association is a module deployment semantic association and the module deployment of the resource The associated subscription set is not empty. If so, execute the module to deploy associated notifications. Otherwise, further judge whether there are unprocessed resources in the resource update operation set. If so, continue to fetch a resource in the resource update operation set and its semantic association for judgment, otherwise Finish.

Preferably, the authority controller includes an account management module for identifying and verifying the developer's login identity and a security access control module for controlling the developer's access authority.

Preferably, the resource layer includes a resource manager, and the resource manager includes a user space management module, a virtual resource management module, and a physical resource management module, and the user space management module is used to maintain the developer's user space view, so The virtual resource management module is used to maintain a virtual resource view, and the physical resource management module is used to realize the mapping from virtual resources to physical resources and the node storage strategy of physical resources.

Further preferably, the physical resource management module includes a centralized control submodule and a node control submodule; the centralized control submodule uses the Mapreduce parallel method to map and search and locate virtual resources to physical resources, and the virtual resources to physical resources The mapping adopts a unique design of storage-to-association migration, and stores semantically related resources on nodes whose physical distance is less than the threshold; the node control sub-module stores physical resources on multiple nodes of the distributed file system inside the cluster.

In addition, it is also necessary to provide a PaaS collaboration method based on semantic association that can improve the efficiency of collaborative development.

A PaaS collaboration method based on semantic association, the method is applied in the control layer of the PaaS collaboration system based on semantic association, including: when the control layer constructs or upgrades the semantic association instance, calling the resource subscription based on semantic association method for resource subscription; when the control layer detects a resource update, it calls the resource notification method based on semantic association for resource notification.

Preferably, before invoking the resource subscription method and resource notification method based on semantic association, it also includes: constructing and upgrading the semantic association instance according to the dependency relationship defined by the developer. The dependency relationship is a one-way relationship, which is divided into code modification dependency, interface Update dependencies and module deployment dependencies, the constructed semantic association instance contains all association tuples, each association tuple is defined as <x, y, R _x→y >, where x, y represent resources, and R _x→y represents A semantic relationship R from x to y, the semantic relationship is a one-way relationship, including code modification dependency semantic relationship, interface update semantic relationship and module deployment semantic relationship.

Further preferably, the resource subscription method based on semantic association includes the following steps:

A1. Traverse all association tuples in the semantic association instance, and take out one of the association tuples Q: <x, y, R _x→y >;

A2. Determine whether R is equal to the code modification semantic association, if so, add x to the code modification association subscription set of y, and then perform step A5, otherwise, proceed to step A3, where the code modification association subscription set means that all codes for p have been coded Modify the resources of the associated subscription;

A3. Determine whether R is equal to the interface update semantic association, if so, add x to the interface update association subscription set of y, and then perform step A5, otherwise, proceed to step A4, where the interface update association subscription set indicates that all interfaces to p have been implemented Update the resources of the associated subscription;

A4. Determine whether R is equal to the module deployment semantic association, if so, add x to the module deployment association subscription set of y, and then perform step A5, otherwise, proceed to step A5, where the module deployment association subscription set indicates that all modules for p have been executed Deploy resources associated with subscriptions;

A5. Determine whether there is an unprocessed semantic association in the current resource, if yes, proceed to step A1, otherwise end.

Preferably, the resource notification method based on semantic association includes the following steps:

B1. Generate a resource update operation set according to the received resource update operation;

B2. Take out a resource of the resource update operation set and its semantic association;

B3. Determine whether the semantic association is a code modification semantic association and the code modification association subscription set of the resource is not empty, if so, execute the code modification association notification, and go to step B6, otherwise proceed to step B4;

B4. Determine whether the semantic association is an interface update semantic association and the interface update association subscription set of the resource is not empty, if so, execute the interface update association notification, and go to step B6, otherwise proceed to step B5;

B5. Determine whether the semantic association is a module deployment semantic association and the module deployment association subscription set of the resource is not empty, if so, execute the module deployment association notification, otherwise proceed to step B6;

B6. Determine whether there are unprocessed resources in the resource update operation set, if yes, execute B2, otherwise end.

The above-mentioned PaaS collaboration system based on semantic association includes an engine layer, a service layer, a control layer, and a resource layer. The control layer can analyze and maintain a variety of semantic associations that play a core role in the collaborative work of multiple developers, and support the development of multiple developers. Analyze and process multiple semantic associations between different modules and codes, subscribe to resources through the PaaS collaboration method based on semantic associations, and notify the corresponding developers with dependencies when the codes with semantic associations are updated; Layer maintenance of virtual resources based on developer space view and mapping of virtual resources to physical resources using the design of storage-to-association migration. Therefore, it intelligently helps collaborative developers to better coordinate each related development module, and fundamentally improves the efficiency and quality of collaborative development work.

Description of drawings

Fig. 1 is a schematic structural diagram of a PaaS collaboration system based on semantic association in an embodiment;

Fig. 2 is the internal structure of the resource manager and its corresponding management control diagram in an embodiment;

FIG. 3 is a schematic diagram of a strategy for mapping virtual resources to physical resources in an embodiment;

Fig. 4 is a flowchart of a resource subscription method based on semantic association in an embodiment;

Fig. 5 is a flowchart of a resource notification method based on semantic association in an embodiment.

Detailed ways

The PaaS collaboration system based on semantic association provided by the present invention can be divided into two parts, a client and a server, from the perspective of a developer. Developers log in and access the system through the client (that is, the command terminal or the visual user interface (Graphic User Interface, GUI)), and select the engineering project according to the project list listed by the system, and then write and debug the project code it maintains. The client periodically sends the developer's update operations (records) to the server, and the server needs to implement timely notification of resource updates, so that the overall project maintains coordination in association.

As shown in Figure 1, a kind of PaaS cooperative system based on semantic correlation comprises engine layer, server, control layer and resource layer, and described engine layer is used for receiving and parsing Soap (Simple Object Access Protocol, Simple Object Access Protocol) request, The service layer triggers the corresponding Web service according to the received Soap request, the control layer analyzes and maintains the semantic association, and based on the semantic association, performs collaborative management on the distributed asynchronous operations of multiple developers, and invokes the PaaS collaboration method based on the semantic association Subscription and notification of resources are performed, and access rights of developers are controlled at the same time. The resource layer maintains virtual resources based on the developer's space view and maps virtual resources to physical resources.

As shown in Figure 1, engine layer comprises the Soap engine module for receiving and parsing Soap request, and this Soap engine module comprises Soap request monitoring module, Soap request parsing module and multi-user session management module (not shown in the figure), wherein , the Soap request monitoring module receives the Soap request sent by the user, and forwards the Soap response generated by the underlying system. connection of user sessions.

The service layer maintains a service pool, which contains a large number of Web services for handling developer code updates and deployment operations. Each Web service is defined and described through WSDL (Web Service Description Language, an XML language used to describe Web services and how to communicate with Web services), and follow the WSRF (Web Service Resource Framework, Web Service Resource Framework) standard.

The control layer includes operation controllers, association controllers and permission controllers, among which:

The operation controller is used to process the developer's operation instructions, including resource management module, resource debugging module and resource deployment module, among which, the resource management module is used to map the developer's resource operation instructions, including resource addition, deletion and modification, etc.; resource The debugging module is used to complete the testing and functional joint debugging of various resources, such as functional testing, multi-module joint debugging, etc.; the resource deployment module is used to assist project release, etc.

The association controller is used to resolve and maintain semantic associations, detect resource updates, and call PaaS collaboration methods based on semantic associations for resource subscription and notification, and coordinate operations between developers. It includes a semantic association management module and a semantic association monitoring module, among which: the semantic association management module is used to analyze and maintain the semantic association between resources, construct and upgrade the semantic association instance; the semantic association monitoring module is used to detect resource updates, semantic association management The module and the semantic association monitoring module are also used to call the PaaS collaboration method based on the semantic association to subscribe and notify resources.

(其中x，y表示两个资源，“→”表示语义关联，R为语义关联的一种类型)，则

(x代码修改关联y)是指：资源x依赖于开发人员对资源y所作的任何修改；

(x接口更新关联y)是指：资源x依赖于开发人员对资源y的函数以及模块间的接口所作的更新；

(x模块部署关联y)是指：资源x依赖于资源y所在模块的完整模块发布，一个完整模块的发布，表明一个更加完整的阶段性更新，每个发布都配有一个版本号以协助历史记录。语义关联实例表示为一个由资源节点和关联有向边组成的图，其构造方法是通过遍历每一个资源结点，根据其到其他资源的依赖关系R生成相应的关联元组并存储在语义数据库中。Specifically, the semantic association management module generates and stores a semantic association instance according to the dependency between resources specified by the developer. Dependency is a one-way relationship, which is divided into code modification dependency, interface update dependency, and module deployment dependency. Semantic association is also a one-way relationship, which is also divided into code modification semantic association, interface update semantic association, and module deployment semantic association. The constructed semantic association instance contains all association tuples, and each association tuple is defined as <x, y, R _x→y >, where x, y represent resources, and R _x→y represents the semantic association R from x to y ,set up

(where x, y represent two resources, "→" represents semantic association, and R is a type of semantic association), then

(x code modification association y) means: resource x depends on any modification made by the developer to resource y;

(x interface update association y) means: resource x depends on the update made by the developer on the function of resource y and the interface between modules;

(x module deployment association y) means: resource x depends on the complete module release of the module where resource y is located. The release of a complete module indicates a more complete phased update. Each release is equipped with a version number to assist history Record. A semantic association instance is represented as a graph composed of resource nodes and associated directed edges. Its construction method is to traverse each resource node, generate corresponding association tuples according to its dependency relationship R to other resources, and store them in the semantic database middle.

The semantic association monitoring module is responsible for the monitoring of resource updates, and it maintains two types of queues: notification queue and update operation queue. The notification queues are stored on different physical nodes where the resources are located. One resource corresponds to three notification queues, which are code modification notification queues, interface update notification queues, and module deployment notification queues; update operation queues are stored in different physical nodes where resources are located. On the physical node of , multiple resources correspond to an update operation queue.

In one embodiment, when the semantic association management module of the association controller in the control layer constructs or upgrades the semantic association instance, the semantic association monitoring module invokes the resource subscription method based on the semantic association to subscribe resources, specifically: traversing the semantic association For all the associated tuples in the instance, take out one of the associated tuples Q: <x, y, R _x→y >, that is, take out a record in the semantic database, and judge whether R is equal to the semantic association of code modification. If so, in the resource y Add object x to the code modification notification queue, otherwise further judge whether R is equal to the interface update semantic association, if so, add object x to the interface update notification queue of resource y, otherwise further judge whether R is equal to the module deployment semantic association, if so, in Add object x to the module deployment notification queue for resource y until all associated tuples are processed.

In another embodiment, the semantic association monitoring module is further used to call a resource notification method based on semantic association to perform resource notification when a resource update is detected, specifically: generate a resource update operation set according to the received resource update operation, that is, take out Generate a resource update operation set for all objects in the update operation queue, then take out a resource p and its semantic association M in the resource update operation set, and judge whether M is equal to the code modification semantic association and the code modification notification queue of p is not empty, if , then take out all the objects in the code modification notification queue of p to perform code modification association notification, otherwise, further judge whether M is equal to the interface update semantic association and the interface update notification queue of p is not empty, if so, take out the interface update notification queue of p All objects are notified of interface update association, otherwise further judge whether M is equal to module deployment semantic association and p’s module deployment notification queue is not empty, if so, take out all objects in p’s module deployment notification queue for module deployment association notification, otherwise further Judging whether the resource update operation set exists as a resource to be processed, if so, continue to fetch a resource p and its semantic association M in the resource update operation set for judgment, otherwise end.

The authority controller is used to control the access authority of the developer, including the account management module and the security access control module. The account management module uses the public key mechanism (Public Key Infrastructure, PKI) to check the user public key stored on the server and the The user key sent to identify and verify the developer's login identity. In addition, the client encrypts all Soap requests sent, and the security access control module on the server side decrypts them before processing, thus ensuring the safe and confidential transmission of messages. The security access control module also stipulates that all developers of the same project have the "read permission" of each resource, but the "write permission" of each resource only belongs to a unique developer.

The resource layer includes a resource manager, which provides a unified virtual resource view (that is, a single mirror resource) to the high-level modules, thereby facilitating the operation of distributed resources. At the same time, it manages the underlying physical resources through the distributed file system to ensure that resources Reliability in storage and use. The resource layer also reduces communication overhead through the "storage-to-association migration" strategy to improve collaboration efficiency, and periodically implements data checkpoint recording and recovery.

As shown in Figure 2, the resource manager includes a user space management module, a virtual resource management module and a physical resource management module, wherein: the user space management module is used to maintain the user space view of the developer, mainly including metadata information of the user space, For example, the identification ID of the user space, the total disk space size, the size of the available space, etc.; the virtual resource management module is used to maintain the virtual resource view, and perform unified planning and processing on the user virtual resource view, mainly including the metadata information of the virtual resource, such as The identification ID of virtual resources, the authority owner of virtual resources, the semantic association of virtual resources, etc.; the physical resource management module is used to realize the mapping from virtual resources to physical resources and the node storage strategy of physical resources.

As shown in Figure 3, the physical resource management module mainly includes a centralized control sub-module and a node control sub-module, wherein: the centralized control sub-module uses Mapreduce (a programming model) parallel method to map virtual resources to physical resources and search and locate. The resource mapping adopts the design of "storage-to-association migration", and stores semantically related resources on nodes whose physical distance is smaller than the threshold, thereby improving the management efficiency of physical resources in a distributed environment. Specifically, resources associated based on code modification should be stored on the same node as much as possible, so as to avoid frequent network transmission overhead; resources associated based on interface update semantics and module deployment semantics should be stored on the same node or the same node. different nodes in the rack; modules without any semantic association are recommended to be stored on nodes in different racks. The node control sub-module stores physical resources on multiple nodes of the distributed file system inside the cluster to achieve a highly reliable resource storage mode, that is, when any resource is damaged or lost, it can be restored through the copy stored on other nodes .

The present invention also provides a PaaS collaboration method based on semantic association, which is applied to the control layer of the above-mentioned PaaS collaboration system based on semantic association, including: when the control layer constructs or upgrades the semantic association instance, calling the semantic association-based The resource subscription method is used for resource subscription; when the control layer detects resource updates, it calls the resource notification method based on semantic association for resource notification.

In the control layer of the PaaS collaboration system based on semantic association, the semantic association instance is constructed and upgraded according to the dependency relationship defined by the developer. The dependency relationship is a one-way relationship, which is divided into code modification dependency, interface update dependency and module deployment dependency , the constructed semantic association instance contains all association tuples, including code modification dependency semantic association, interface update semantic association and module deployment semantic association. Each association tuple is defined as <x, y, R _x→y >, where , x and y represent resources, and R _x→y represents the semantic association R from x to y.

In one embodiment, as shown in FIG. 4 , the process of the resource subscription method based on semantic association is specifically:

Step S101, traverse all association tuples in the semantic association instance, and take out one association tuple Q: <x, y, R _x→y >.

Step S102, judging whether R is equal to code modification semantic association, if yes, execute step S103, otherwise, enter step S104.

Step S103, adding x to the code modification associated subscription set of y, that is, adding object x to the code modification notification queue of resource y.

Step S104, judge whether R is equal to the interface update semantic association, if so, go to step S105, otherwise go to step S106.

Step S105, adding x to the interface update association subscription set of y, that is, adding object x to the interface update notification queue of resource y.

Step S106, judge whether R is equal to the module deployment semantic association, if so, go to step S107, otherwise go to step S108.

Step S107, adding x to the module deployment associated subscription set of y, that is, adding object x to the module deployment notification queue of resource y.

Step S108, determine whether there is an unprocessed semantic association in the current resource, if yes, return to step S101, otherwise end.

In another embodiment, as shown in Figure 5, the specific process of the resource notification method based on semantic association is as follows:

Step S201, generate a resource update operation set according to the received resource update operation, that is, take out all objects in the update operation queue to generate a resource update operation set.

Step S202, fetching a resource p and its semantic association M in the resource update operation set.

Step S203, judging whether M is a code modification semantic association and p's code modification association subscription set is not empty, that is, judging whether M is equal to a code modification semantic association and p's code modification notification queue is not empty, if so, go to step S204, Otherwise, go to step S205.

Step S204, execute code modification associated notification, that is, take out all objects in p's code modification notification queue and perform code modification associated notification.

Step S205, determine whether M is an interface update semantic association and p's interface update association subscription set is not empty, that is, determine whether M is equal to an interface update semantic association and p's interface update notification queue is not empty, if so, go to step S206, Otherwise, go to step S207.

Step S206, execute interface update association notification, that is, take out all objects in p's interface update notification queue and perform interface update association notification.

Step S207, determine whether M is a module deployment semantic association and p's module deployment association subscription set is not empty, that is, determine whether M is equal to a module deployment semantic association and p's module deployment notification queue is not empty, if so, execute step S208, Otherwise, go to step S209.

Step S208, execute module deployment association notification, that is, take out all objects in p's module deployment association notification queue and perform module deployment association notification.

Step S209, judging whether there are unprocessed resources in the resource update operation set, if yes, return to step S202, otherwise end.

The above-mentioned PaaS collaboration system based on semantic association includes an engine layer, a service layer, a control layer, and a resource layer. The control layer can analyze and maintain a variety of semantic associations that play a core role in the collaborative work of multiple developers, and support the development of multiple developers. Analyze and process multiple semantic associations between different modules and codes, subscribe to resources through the PaaS collaboration method based on semantic associations, and notify the corresponding developers with dependencies when the codes with semantic associations are updated; Layer maintenance of virtual resources based on developer space view and mapping of virtual resources to physical resources using the design of storage-to-association migration. Therefore, it intelligently helps collaborative developers to better coordinate each related development module, and fundamentally improves the efficiency and quality of collaborative development work.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. within range.

Claims (10)

1. the PaaS cooperative system of a semantic-based association, it is characterized in that, comprise engine layers, service layer, key-course and resource layer, described engine layers is used for receiving and resolves Soap and ask, described service layer triggers the service layer of corresponding Web service according to the Soap request that receives, described key-course is resolved and is safeguarded that the related distributed asynchronous operation to a plurality of developers of semantic association and semantic-based carries out coordinated management, the PaaS Synergistic method that calls the semantic-based association carries out resource subscription and notice, control simultaneously developer's access rights, described resource layer carry out based on the virtual resource of developer's space view safeguard and virtual resource to the mapping of physical resource;

Described resource layer comprises explorer, described explorer comprises user's space administration module, virtual resource administration module and physical resource management module, described user's space administration module is used for Maintenance Development personnel's user's space view, described virtual resource administration module is used for safeguarding the virtual resource view, and described physical resource management module is used for the realization virtual resource and deposits strategy to the mapping of physical resource and the node of physical resource;

Described physical resource management module comprises centralized control submodule and node control submodule; Described centralized control submodule adopts the Mapreduce parallel method to carry out virtual resource to the mapping of physical resource and search location, described virtual resource adopts storage to the design of association migration to the mapping of physical resource, and the resource that has semantic association is left on the node of physical distance less than threshold value; Described node control submodule is stored in physical resource on a plurality of nodes of the inner distributed file system of cluster.

2. the PaaS cooperative system of semantic-based association according to claim 1 is characterized in that, described engine layers comprises for the Soap engine modules that receives and resolve the Soap request.

3. the PaaS cooperative system of semantic-based association according to claim 1 is characterized in that, described service layer comprises service pool, comprises the Web service for the treatment of developer's code update and deployment in the described service pool.

4. the PaaS cooperative system of semantic-based association according to claim 1, it is characterized in that, described key-course comprises operation control, related controller and drm controller, described operation control is for the treatment of developer's operational order, described related controller is used for resolving and safeguarding semantic association, detect resource updates, and the PaaS Synergistic method that calls the semantic-based association carries out resource subscription and notice, operation between the coordinated development personnel, described drm controller is used for control developer's access rights.

5. the PaaS cooperative system of semantic-based association according to claim 4, it is characterized in that, described operation control comprises the resource deployment module of the resource management module of the resource operation instruction of shining upon the developer, the resource debugging module of finishing resource testing and function uniting and adjustment and supporting item issue.

6. the PaaS cooperative system of semantic-based association according to claim 4, it is characterized in that, described related controller comprises semantic association administration module and semantic association monitoring module, described semantic association administration module is used for the semantic association between parsing and the maintenance resources, structure and upgrading semantic association example, described semantic association monitoring module is for detection of resource updates, and described semantic association administration module calls the related PaaS Synergistic method of semantic-based with the semantic association monitoring module and carries out resource subscription and notice.

7. the PaaS cooperative system of semantic-based association according to claim 6, it is characterized in that, described semantic association administration module defines dependence structure and the upgrading semantic association example of resource according to the developer, described dependence is unidirectional relationship, be divided into code revision dependence, interface renewal dependence and module and dispose dependence, the semantic association example of constructing comprises all association tuple, and each association tuple is defined as＜x, y, R _{X → y}, wherein, x, y represent resource, R _{X → y}Expression x is to the semantic association R of y, and described semantic association is unidirectional relationship, comprises code revision semantic association, the association of interface update semantics and module deployment semantic association.

8. the PaaS cooperative system of semantic-based association according to claim 7, it is characterized in that, described semantic association monitoring module is further used for when described semantic association administration module is constructed or upgraded complete semantic association example, call the resource subscription method of semantic-based association and carry out resource subscription, specifically: all association tuple in the traversal semantic association example, take out one of them association tuple Q:＜x, y, R _{X → y}; judge whether R equals the code revision semantic association; if x is added to related subscription of code revision of y and concentrate, otherwise it is related to judge further whether R equals the interface update semantics; if; the interface that then x is added to y upgrades related the subscription to be concentrated, otherwise judges further whether R equals module and dispose semantic association, if; then x is added to related subscription of module deployment of y and concentrate, until all association tuple are processed complete.

9. according to claim 7 or the PaaS cooperative system of 8 described semantic-based associations, it is characterized in that, when described semantic association monitoring module is further used for detecting resource updates, call the resource notification method of semantic-based association and carry out resource notification, specifically: generate the resource updates operation set according to the resource updates operation that receives, take out resource and the semantic association thereof of described resource updates operation set, judge that whether described semantic association is that the related collection of subscribing to of code revision of code revision semantic association and described resource is for empty, if, run time version is revised related notice, otherwise judge further whether described semantic association is that interface update semantics interface related and described resource upgrades the related collection of subscribing to not for empty, if, then executive's interface upgrades related notice, otherwise judge that further whether described semantic association is that the module that module is disposed semantic association and described resource is disposed the related collection of subscribing to for empty, if, then execution module is disposed related notice, otherwise judge further whether the resource updates operation set exists untreated resource, if, then continue to take out resource and the semantic association thereof of resource updates operation set and judge, otherwise finish.

10. the PaaS cooperative system of semantic-based association according to claim 4, it is characterized in that, described drm controller comprises identifies the account management module of checking and the safe access control module of control developer's access rights to developer's login identity.

Images