JP2004110624A - Computer resource management device and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To facilitate resource sharing setting of a user by concealing the complicatedness of a procedure of sharing setting between decentralized resource sharing mechanisms from the user. <P>SOLUTION: A name space synthesizing means (13, 23) manages a data structure of a traversal domain management table to a traversal domain striding over a plurality of name management services. The traversal domain management table holds a list of a traversal domain ID identified by own name managemet service, a naming context ID serving as a route of the traversal domain, and an external domain combination list summarizing the information on the other name management services participating in the traversal domain. The external domain combination list holds a list of another name management service ID participating in the traversal domain, the traversal domain ID, a naming context ID serving as a route of the traversal domain and identification information. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a technology for transparently integrating and managing computer resources in a distributed environment, and more particularly to enabling a plurality of name management services to cooperate. The present invention can be applied to a distributed name service, a distributed file system, and a peer-to-peer communication service.
[0002]
[Prior art]
Users independently manage computer resources such as electronic documents related to their activities. When multiple users perform collaborative work, it is effective to share computer resources managed by each user among users involved in the collaborative work. Further, in some cases, not only computer resources managed by each user but also public computer resources not under the control of the user, such as computer resources in a conference room, may be temporarily shared. As described above, a group of computer resources in a shared state can be collectively handled as one computer resource. Hereinafter, a group of the above computer resources will be referred to as a joint workplace for convenience. Since the joint workplace is a computer resource, it is managed again by name.
[0003]
With a single namespace, the co-working space must be located somewhere in the single namespace. This means that, from the viewpoint of each user, it is necessary to always appropriately associate a personal computer resource that he / she has managed without permission with a name corresponding to a collaborative workplace.
[0004]
As a first problem of managing with a single namespace, throughout the collaborative life cycle, the associated computing resources are globally dependent on a single namespace and the cost of managing that dependency is high. Can occur.
[0005]
For example, in a conventional server-centric architecture, in a collaborative work, a user needs to upload a file to a file server specified by a predetermined URL, or place the file on a Web server to be accessed using the URL. Each time a resource is updated, the user must repeat these procedures.
[0006]
A second problem of management with a single namespace is the life cycle management of the collaborative workshop itself. When transitioning from personal to collaborative work, resources under personal management need to be re-mapped to the collaborative workplace. It's always a matter of where to set up the co-working area and how to map it. Also, when the collaborative work ends and returns to the personal work, similarly, necessary resources from the collaborative workplace must be re-mapped under personal management.
[0007]
For example, in the conventional server-centered architecture, when starting a collaborative work, it is necessary to determine which file server is to be set up and managed, and once it is decided, it is not easy to change during the collaborative work. When the operation of the file server is finished, each person must bring back the necessary files.
[0008]
As a non-server-centric method, there is a distributed file system. In the distributed file system, each computer can share a part of the file system with each other.
[0009]
Network File System (NFS), a distributed file system developed by Sun Microsystems, USA, and Coda (a file system developed at Carnegie Mellon University) are based on a single global namespace. The former means a dependency on a DNS (Domain Name System) namespace called a host name, and Coda means a mapping for a single tree.
[0010]
As a pioneering technology as a distributed management technology for computer resources using a local name space, there is a file system of a distributed OS ToM (Thread on Modules). In the ToM file system, unique views can be configured by assigning different views to users and groups.
[0011]
The group view corresponds to the collaborative workshop referred to here. However, in order to manage the life cycle of the joint work, a user and group management mechanism must be added, including a mechanism that can easily create a group view (joint work place).
[0012]
Another non-server centric scheme is peer-to-peer file sharing. In peer-to-peer file sharing, the purpose of file sharing services connected to each other is to share a group of available files, and cannot handle the resource of a joint workplace with a life cycle as a joint workplace . For this reason, in a joint work situation, only a very temporary connection can be established between users.
[0013]
Another issue is the dynamic aspects of collaboration. In an ongoing collaboration, rather than an archive of work that has already been done, various resources are constantly updated. The volatility of each resource is high, and the resource group fluctuates greatly. If this property is not properly accommodated, the collaborative workplace will not be used much, and the collaborative work will not progress due to stagnation, or conversely, it will be overused, overflowing unnecessary resources and causing confusion.
[0014]
These issues are barriers to working together. The present applicant has proposed a computer resource management method for solving such a problem (Japanese Patent Application No. 2002-120661, not disclosed at the time of filing this application). This proposal aims to make the computer resources involved in collaborative work globally independent of a single namespace by providing a mechanism for sharing named resources under personal management with each other according to collaborative work. Is possible. Furthermore, by providing a mechanism for monitoring a change in the state of a computer resource and changing the association between a name and a resource based on the change, the joint workplace itself can autonomously manage resources in the joint workplace.
[0015]
In the proposal according to Japanese Patent Application No. 2002-120661, resource sharing settings are distributed and held across individuals and organizations involved in collaborative work, and a centralized control mechanism is eliminated. In order to perform the above resource sharing setting, information necessary for the setting must be exchanged between resource management hosts in a complicated procedure. However, in this proposal, since there is no mechanism for controlling the progress of the left procedure, there is a problem that the user has to operate all the left procedures, and the sharing setting becomes very complicated.
[0016]
[Problems to be solved by the invention]
The present invention has been made in view of the above circumstances, and conceals the complexity of the sharing setting procedure from the non-centralized resource sharing mechanism from the user so that the user can easily perform the resource sharing setting. It is intended to be.
[0017]
[Means for Solving the Problems]
According to the present invention, in order to achieve the above object, a configuration as described in the claims is adopted. Here, before describing the invention in detail, the description of the claims will be supplementarily described.
[0018]
In a specific configuration of the present invention, the management range of the computer resource management device is regarded as a domain, and the management range of computer resources shared and managed across these domains is regarded as a transverse domain. Then, by centrally managing the sharing setting information under the crossing domain, the computer resource management device can execute the sharing setting on behalf of the user, and can greatly reduce the trouble of the user setting. . Further, the present invention will be described.
[0019]
The computer resource management apparatus according to one aspect of the present invention is based on a name management environment in which a plurality of name management services are provided on a network and the computer manages computer resources distributed on the network using the name management services. The computer resource management device includes: for each of at least two name management services to be linked; name management for managing the correspondence between computer resources and names and controlling the operation of the correspondence for each operation subject; Means; and at least a part of the correspondence between the computer resource and the name managed by the name management means and the name management means of the other name management service to be linked is included in the correspondence of the name management means. A name space synthesizing unit that collectively manages management information to be positioned as a collaborative work object so that it can be distinguished from other similar management information and manages the information; An external service linking means for cooperating with each other to set a joint work target of the namespace synthesizing means; and calculating in cooperation with the name managing means Associating a resource with the name further includes a computer resource operation means for performing an operation for each operation subject to the computer resources cooperate with each other in between the names management service of the associated object.
[0020]
The collaborative work target is called, for example, a transverse domain. By centrally managing the sharing setting information under the traversing domain, the computer resource management device can execute the sharing setting on behalf of the user, thereby greatly reducing the trouble of the user setting.
[0021]
The management information associated with the traversing domain is identifiable by the traversing domain ID, and includes other name management services participating in the traversing domain, its managed names, and its managed traversing domain IDs. Further, it may include authentication information used for authentication by another name management service, a list of users registered in the cross domain among users of the other name management services, and the like.
[0022]
The present invention can be realized not only as a device or a system but also as a method. In addition, it goes without saying that a part of such an invention can be configured as software. Also, it goes without saying that a software product used for causing a computer to execute such software is also included in the technical scope of the present invention.
[0023]
The above aspects of the present invention and other aspects of the present invention are set forth in the appended claims, and are described in detail below with reference to embodiments.
[0024]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a computer resource management system according to an embodiment of the present invention will be described with reference to the drawings.
[0025]
[Device configuration]
FIG. 1 is a configuration diagram of the apparatus according to the present embodiment. In FIG. 1, a name management service (10, 20) includes an authentication means (11, 21), a name management means (12, 22), a name space synthesis means (13, 23), and an external service linking means, respectively. (14, 24). Each of the resource management services (30, 40, 50, 60) includes resource operation means (31, 41, 51, 61) and user interface means (32, 42, 52, 62).
[0026]
Each name management service has its own management scope, which is called a domain. In the figure, a domain A and a domain B are shown.
[0027]
Each of the name management service and the resource management service has an identifier called a service ID, and is identified by this. The service ID is a universally unique identifier that can be generated by each service. Various types of such identifiers are known. In the present embodiment, a UUID (Universal Unique Identifier) is used.
[0028]
In this embodiment, each service in FIG. 1 is configured on a network-transparent distributed processing infrastructure, and can cooperate with each other across a network through reference to a partner service.
[0029]
Prior to the cooperative operation, it is necessary to obtain a reference to the partner service. For this processing, an infrastructure function is used. For example, as shown in FIG. 2, a bootstrap service (80) is prepared, and a service location is registered and inquired in the bootstrap service (80) to obtain a reference to a partner service. By doing so, a method of notifying the partner service can be used. (90) is a router.
[0030]
Hereinafter, each part will be described in detail.
[0031]
[Authentication means]
The authentication means (11, 21) performs authentication based on an authentication key with respect to a previously registered operation subject. In this embodiment, a password is used as an authentication key, and authentication is performed by collating the password.
[0032]
The authentication means (11, 21) manages the data structures of FIG. 4 (user authentication information table) and FIG. 5 (authenticated session table).
[0033]
FIG. 4 (user authentication information table) is used to store the correspondence between the previously registered operating subject and the authentication key. The user ID is a universally unique identifier, and in this embodiment, a UUID is used.
[0034]
The authentication means (11, 21) starts a session for the authenticated user and issues a session object which is a special object representing the session. Each session object is identified by a session ID. The session ID is a universally unique identifier, and in the present embodiment, is configured by combining a service ID and a session number generated by a strong random number.
[0035]
The client of each service presents a session object to each service, and each service checks whether the session has been authenticated by the authentication means (11, 21), and determines whether or not operation on the object under management is possible. Is determined. FIG. 5 (authenticated session table) is used for storing the session ID of the authenticated session for the above inspection.
[0036]
[Name management means]
The name management means (12, 22) manages the naming context object, and further manages the name space by managing graph information of the naming context.
[0037]
The name management means (12, 22) manages the data structures shown in FIG. 6 (naming context table) and FIG. 7 (external service inquiry table).
[0038]
FIG. 6 (naming context table) is used to manage the graph of the naming context. Each naming context is identified by an object ID. The object ID is a universally unique identifier. In the present embodiment, the object ID is configured by combining the serial number of the object assigned when the service generates the object and the service ID of the service.
[0039]
The naming context has a name list as an element. The name list associates names with naming contexts and resources that the naming contexts organize.
[0040]
In the name list, the naming context and the resource are represented by a set of a service ID of a service managing each object and an object ID of the object itself.
[0041]
FIG. 7 (external service inquiry table) indicates a service ID appearing in FIG. 6 (naming context table) and a reference relationship to the corresponding service. The name management means (12, 22) acquires a specific reference destination from the service ID while using the function of the infrastructure as necessary, and fills this external service inquiry table (FIG. 7). The reference destination is a resource management service or another name management service. Thereby, the name management means (12, 22) can reach the resource managed by the external service.
[0042]
[Namespace composition means]
The name space synthesizing means (13, 23) performs name synthesis between a plurality of name management services. The name space synthesizing means (13, 23) manages the data structure shown in FIG. 8 (transverse domain management table). When an agreement for performing namespace composition is made between a plurality of name management services, a range related to the agreement is called a transverse domain. In FIG. 8 (transverse domain management table), the transverse domain ID identified by the own name management service, the ID of the naming context that is the root of the transverse domain, and information on other name management services participating in the transverse domain are shown. Represents a list of sets consisting of the aggregated external domain binding lists. Further, the external domain binding list includes the IDs of other name management services participating in the crossing domain, the crossing domain ID identified by the service on the left, and the ID of the naming context that is the root of the crossing domain set by the service on the left. And a list of sets of authentication information. Further, the authentication information on the left is a list of the correspondence between the user ID of the own domain and an external authentication key for the user to be authenticated in another domain, and conversely, the ID of the user who can be authenticated in the own domain among other domains Represents a list. The former is used by the name management service to perform the user's authentication operation on the other domain on behalf of the user when the user of the own domain operates the computer resource of the other domain. Conversely, the latter is used when a user in another domain operates a computer resource in the own domain. The authentication key at that time is set in the authentication means (11, 21) by the external service linking means (14, 24).
[0043]
The name space synthesis processing performs the processing in FIG. 10 and inquires objects on the cross domain. In this process, while descending the graph of the naming context, when the naming context set at the root of the crossing domain is reached, the naming context is extended to another corresponding domain to perform an object query.
[0044]
The query processing of the object on the crossing domain in FIG. 10 is performed as follows.
[0045]
[Step S10]: Substitute the naming context of the query start point into c, substitute the name (composite name) into n, and empty the result set S.
[Step S11]: It is determined whether or not the name cannot be resolved (atomic name). If it is impossible, the process proceeds to step S14. If it is possible, the process proceeds to step S12.
[Step S12]: For the naming context c, an object inquiry process is performed for each of the naming contexts of other domains that are routed on the crossing domain, and the result is added to the result set S. If the naming context c is not set on the traversal domain, nothing is performed.
[Step S13]: The first part of the name is deleted. Returning to step S11, the process is repeated.
[Step S14]: An object name corresponding to the name n is added to the result set S.
[Step S15]: It is determined whether or not the number of elements of the result set S is one. If 1, the process proceeds to step S16. If not 1, the process proceeds to step S17.
[Step S16]: Return the object name of the only element of the result set S. The process ends.
[Step S17]: The conflict of the result set S is resolved. The process ends. The conflict resolution will be described later.
[0046]
FIG. 11 shows an example of this processing. Since the naming context C12 is set as the root of the traversing domain, the corresponding namespaces of C22 and below in other domains are also to be queried in the same manner as the namespace of the own domain.
[0047]
If the object queried by the above processing is a naming context, the name management means (12, 22) handles the naming context irrespective of whether it is its own domain or another domain. As a result, the namespace is synthesized.
[0048]
If there is a duplicate name, the conflict is resolved. Various methods can be used to resolve the conflict. However, as long as it can be ensured that two or more objects do not correspond to the name, no specific method is used in this embodiment.
[0049]
1. Simply fail
2. Get objects directly associated with your namespace
3. Get the object with the latest update time (in this case, you need to add an attribute field to the naming context table)
[0050]
[External service linking means]
The external service linking means (14, 24) is responsible for establishing and breaking down links between the plurality of name management services. The external service linking means (14, 24) updates the data structure of FIG. 8 (transverse domain management table) in response to an operation request from the user. The processing that can be performed by the user is as follows.
[0051]
1. Creating a new crossing domain
2. Extending transverse domains
3. Cross Domain Reduction
4. Delete transverse domain
[0052]
FIG. 12 shows a process commonly used in the process of creating a new crossing domain and the process of expanding the crossing domain. This process is activated by a user using each name management service, and is executed by each name management service. In the case of newly creating a transverse domain, all the name management services execute the processing of FIG. 12 equally. In the case of the crossing domain expansion process, the name management service newly joining the existing crossing domain executes the process of FIG. In this process, information necessary for setting FIG. 8 (transverse domain management table) is transmitted to each other as a message, and the reception of the message is mutually confirmed. What to do.
[0053]
The process of creating a new crossing domain in FIG. 12 is performed as follows.
[0054]
[Step S20]: Generate a crossing domain ID, add an entry to the crossing domain management table, and set the crossing domain ID and the ID of the naming context to be the root.
[Step S21]: For each of the cross-domain participation services, a cross-domain setting message including a set of all cross-domain participation service IDs, a naming context ID serving as a root of the own domain, and authentication information is prepared.
[Step S22]: Transmit a transverse domain setting message to the corresponding participating service.
[Step S23]: Receive a crossing domain setting message from the corresponding participating service, and set the external domain binding list and the authentication means in the crossing domain management table based on the message.
[Step S24]: It is determined whether or not the crossing domain setting messages have been received from all other crossing domain participation services. If all the crossing domain setting messages have been received, the process proceeds to step S25. If not, the process returns to step S23 to repeat the process.
[Step S25]: A crossing domain setting confirmation message is prepared for each of the transmission sources of the crossing domain setting message.
[Step S26]: Send a cross-domain setting confirmation message to the corresponding participating service.
[Step S27]: Receive a transverse domain setting confirmation message from the corresponding participating service.
[Step S28]: It is determined whether or not crossing domain setting confirmation messages have been received from all other crossing domain participation services. If all the crossing domain setting confirmation messages have been received, the process proceeds to step S29.
[Step S29]: Validate the crossing domain. Processing Exit.
[0055]
FIG. 13 shows a process when a name management service that has already joined the existing crossing domain accepts another name management service that newly joins by a user operation in the case of the transverse domain extension process. In this process, as in the process of FIG. 12, information necessary for setting FIG. 8 (transverse domain management table) is transmitted as messages to each other, and reception of the messages is confirmed by each other, thereby achieving synchronization. The setting of the crossing domain is performed autonomously.
[0056]
The process of accepting new participation in the existing cross-domain shown in FIG. 13 is performed as follows.
[0057]
[Step S30]: Add an entry in the crossing domain management table corresponding to the crossing domain ID that accepts entry, and add an entry of the joining service to the external domain binding list.
[Step S31]: For a service to be entered, a set of all crossing domain participation service IDs and a crossing domain setting message including the ID of a naming context to be the root of the own domain and authentication information are prepared.
[Step S32]: Transmit a transverse domain setting message to the corresponding participating service.
[Step S33]: Receive a crossing domain setting message from the corresponding participating service, and set the external domain binding list and authentication means in the crossing domain management table based on the message.
[Step S34]: It is determined whether or not the crossing domain setting messages have been received from all the other crossing domain participation services. If all the crossing domain setting messages have been received, the process proceeds to step S35. If not, the process returns to step S33 and repeats the process.
[Step S35]: Prepare a transverse domain setting confirmation message for each of the transmission sources of the transverse domain setting message.
[Step S36]: Transmit a cross-domain setting confirmation message to the corresponding participating service.
[Step S37]: Receive a transverse domain setting confirmation message from the corresponding participating service.
[Step S38]: It is determined whether or not crossing domain setting confirmation messages have been received from all other crossing domain participation services. If all of them have been received, the process proceeds to step S39. If not, the process returns to step S37 and repeats the process.
[Step S39]: Validate the crossing domain. Processing Exit.
[0058]
Note that the authentication information in FIGS. 12 and 13 must share an authentication key for a plurality of users with a related name management service. In the present embodiment, a “seed” for generating a series of external authentication keys is used. Each name management service generates a plurality of external authentication keys based on the seed.
[0059]
FIG. 14 and FIG. 15 show the processes of the side that withdraws from the existing crossing domain and the side that stays in the existing crossing domain and accepts the withdrawal, respectively, in the crossing domain reduction process. The withdrawing side is activated by user processing. The withdrawal accepting side is always activated and waits while waiting for the cross-domain reduction message. In this process, as in the process of FIG. 12, information necessary for setting FIG. 8 is transmitted to each other as a message, and the reception of the message is confirmed by each other. It is something to be done.
[0060]
The process on the withdrawal side in FIG. 14 is performed as follows.
[0061]
[Step S40]: For each of the crossing domain participation services in the crossing domain to be withdrawn, a crossing domain reduction message including the crossing domain ID is generated.
[Step S41]: Send a transverse domain reduction message to the corresponding participating service.
[Step S42]: A cross-domain setting confirmation message is received from the corresponding participating service.
[Step S43]: It is determined whether or not a crossing domain setting confirmation message has been received from all other crossing domain participation services. If all the crossing domain setting confirmation messages have been received, the process proceeds to step S44. If not, the process returns to step S42 and repeats the process.
[Step S44]: Prepare a transverse domain reduction confirmation message for each of the transmission sources of the transverse domain setting confirmation message.
[Step S45]: Send a transverse domain reduction confirmation message to the corresponding participating service.
[Step S46]: The crossing domain is deleted from the crossing domain management table. Processing Exit.
[0062]
The processing on the withdrawal receiving side in FIG. 15 is performed as follows.
[0063]
[Step S50]: Receive a transverse domain reduction message.
[Step S51]: Transmit a crossing domain setting confirmation message to the transmission source of the crossing domain reduction message.
[Step S52]: Receive a transverse domain reduction confirmation message.
[Step S53]: Delete the relevant crossing domain from the crossing domain management table. Processing Exit.
[0064]
FIG. 16 shows a process of deleting a transverse domain. The crossing domain remains in the name management service for which the withdrawal process has not been started until the end, but this process completely deletes the crossing domain from the entire system.
[0065]
The deletion processing of FIG. 16 is performed as follows.
[0066]
[Step S60]: It is determined whether the number of participating services in the crossing domain is one. If it is two or more, the process ends without doing anything. If it is 1, the process proceeds to step S61.
[Step S61]: Delete the crossing domain. Processing Exit.
[0067]
[Computer resource operation means]
The computer resource operation means (31, 41, 51, 61) manages computer resources on each computer as a resource object and associates them with a name space. Further, based on the authentication information, the resource object can be directly operated by another computer resource operation means.
[0068]
The computer resource operation means (31, 41, 51, 61) manages the data structure of FIG. 9 (computer resource inquiry table). FIG. 9 includes a set of a resource object ID (structure is the same as the naming context) managed by the computer resource operation means (31, 41, 51, 61), a resource type, and an external reference to the resource. For example, a normal file has a path name on the local file system as an external reference, and a running process has a communication channel name for inter-process communication as an external reference. This makes it possible to associate the name management means with individual computer resources.
[0069]
The computer resource operation means (31, 41, 51, 61) allows the authenticated operation subject to directly operate the computer resource. The authentication information is inquired to the authentication means (11, 21).
[0070]
The user interface means (32, 42, 52, 62) provides a man-machine interface for allowing a user to perform processing such as input of a login, inquiry of resources, operation, creation of a cross domain, expansion, reduction, deletion, and the like. provide.
[0071]
Note that the present invention is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the present invention. For example, in the above description, a plurality of cooperating name management services share a composite part with each other, but only one name management service incorporates a part of the other name management service into its own namespace. It may be. The cooperating name management service and resource management service may be executed on a single computer. In addition, it goes without saying that the operation subject may log in to the resource management server (service) from another terminal.
[0072]
【The invention's effect】
As described above, according to the present invention, the computer resource management device substitutes the user for the sharing setting by introducing a namespace synthesizing unit which enables the synthesis range of the namespace to be identified and centrally manages related information. Now you can run. As a result, the user only has to activate the sharing setting once, and the trouble of the user setting can be greatly reduced.
[Brief description of the drawings]
FIG. 1 is a configuration diagram showing a specific configuration of an embodiment of the present invention.
FIG. 2 is a diagram illustrating acquisition of a reference using an external reference introduction service.
FIG. 3 is a diagram illustrating acquisition of a reference by broadcast communication.
FIG. 4 is a diagram illustrating an example of a user authentication information table used by the authentication unit in FIG. 1;
FIG. 5 is a diagram illustrating an example of an authenticated session table used by the authentication unit of FIG. 1;
FIG. 6 is a diagram illustrating an example of a naming context table used by the name management unit of FIG. 1;
FIG. 7 is a diagram illustrating an example of an external service inquiry table used by the name management unit of FIG. 1;
FIG. 8 is a diagram illustrating an example of a crossing domain management table managed by the namespace synthesizing unit of FIG. 1;
FIG. 9 is a diagram illustrating an example of a computer resource inquiry table managed by the computer resource operation unit of FIG. 1;
FIG. 10 is a flowchart illustrating an inquiry process in a traversal domain of the namespace synthesizing unit in FIG. 3;
FIG. 11 is a diagram illustrating an example of an object inquiry process in a crossing domain.
FIG. 12 is a flowchart illustrating a crossing domain generation and extension process by the external service linking unit of FIG. 1;
FIG. 13 is a view for explaining a cross-domain extension accepting process by the external service linking means of FIG. 1;
14 is a flowchart illustrating a cross-domain reduction process (withdrawal side) by the external service linking unit of FIG. 1;
FIG. 15 is a flowchart illustrating a transverse domain reduction process (withdrawal accepting side) by the external service linking unit of FIG. 1;
FIG. 16 is a flowchart illustrating a cross-domain deletion process by the external service linking unit of FIG. 1;
[Explanation of symbols]
10,20 Name management service
11,21 Authentication means
12,22 Name management means
13,23 Namespace synthesis means
14,24 External service linking means
30,40,50,60 Resource management service
31, 41, 51, 51 Computer resource operation means
32, 42, 52, 52 user interface means
80 Bootstrap Service
90 router

Claims (8)

A plurality of name management services are provided on a network, a computer resource management device that manages computer resources distributed on the network using the name management service,
For each of the at least two linked name management services,
Name management means for managing the correspondence between computer resources and names and controlling the operation of the correspondence for each operating entity;
At least a part of the correspondence between the computer resource and the name managed by the name management means and the name management means of the other name management service to be linked, respectively, is set in the correspondence of the name management means. Namespace synthesizing means for managing the management information to be positioned as a target, collectively, and identifying each other with other similar management information,
External service linking means for cooperating with each other between the linked name management services to set a portion to be cooperated by the namespace synthesizing means;
A computer resource operating unit that associates a computer resource with a name in cooperation with the name management unit, and further operates in cooperation with each other between the linked object name management services to operate the computer resource for each operation subject; A computer resource management device comprising: The management information includes an identifier of a joint work target, a name, an identifier of a linked name management service, an identifier of a joint work target in a linked name management service, and a name in a linked name management service. Computer resource management device as described. A plurality of name management services are provided on a network, a computer resource management device that manages computer resources distributed on the network using the name management service,
For each of the at least two linked name management services,
An authentication means for authenticating a previously registered operation subject;
Name management means for managing the correspondence between computer resources and names and controlling the operation of the correspondence for each operation subject authenticated by the authentication means;
For positioning at least a part of the correspondence between the computer resource and the name managed by the name management means of the name management service of the other link target as a joint work target in the correspondence of the name management means. Namespace synthesizing means for managing the management information collectively and distinguishably from other similar management information and managing the management information;
Operating under the authentication by the authentication means of the other linked name management service, the linked name management services cooperate with each other to set a joint work target part in the namespace synthesizing means. External service linkage means;
The computer resource is associated with a name in cooperation with the name management means, and further, the name management services to be linked operate in cooperation with each other to operate the computer resource for each operation subject authenticated by the authentication means on the computer resource. And a computer resource operating means for performing the following. 4. The management information includes an identifier of a joint work target, a name, an identifier of a linked name management service, an identifier of a joint work target in a linked name management service, and a name in a linked name management service. Computer resource management device as described. The computer resource management device according to claim 4, wherein the management information includes authentication information for receiving authentication in a linked name management service. The computer resource management device according to claim 4, wherein the management information includes a list of associated name management service users registered as users for the collaborative work target. A plurality of name management services are provided on a network, a computer resource management method for managing computer resources distributed on the network using the name management service,
For each of the at least two linked name management services,
A name management step of managing the correspondence between the computer resource and the name and controlling the operation of the correspondence for each operation subject;
At least a part of the correspondence between the computer resource and the name managed by the name management step and the name management step of the name management service of the other linked object is included in the correspondence managed by the name management step. A namespace synthesizing step of collectively managing management information to be positioned as a collaborative work object so as to be distinguishable from each other and managed with other similar management information;
An external service linking step in which the linked name management services cooperate with each other to set a portion of the collaborative work to be managed in the namespace step;
A computer resource operation step of coordinating with the name management step to associate a computer resource with a name, and further cooperating with each other between the coordination target name management services to operate the computer resource for each operation subject. A computer resource management method, comprising: A plurality of name management services are provided on a network, a computer program for computer resource management that manages computer resources distributed on the network using the name management service,
For at least one of the at least two linked name management services,
A name management step of managing the correspondence between the computer resource and the name and controlling the operation of the correspondence for each operation subject;
At least a part of the correspondence between the computer resource and the name managed by the name management step and the name management step of the name management service of the other linked object is included in the correspondence managed by the name management step. A namespace synthesizing step of collectively managing management information to be positioned as a collaborative work object so as to be distinguishable from each other and managed with other similar management information;
An external service linking step in which the linked name management services cooperate with each other to set a portion of the collaborative work to be managed in the namespace step;
A computer resource operation step of coordinating with the name management step to associate a computer resource with a name, and further cooperating with each other between the coordination target name management services to operate the computer resource for each operation subject. Computer resource management computer program used for causing a computer to execute the following.

Images