Remote debugging in a cloud computing environment

Patent metadata

Field	Value
Publication number	US-9244817-B2
Application number	US-201414472282-A
Country	US
Kind code	B2
Filing date	Aug 28, 2014
Priority date	Jan 31, 2013
Publication date	Jan 26, 2016
Grant date	Jan 26, 2016

Abstract

A method for performing remote debugging in a cloud system comprises the steps of: receiving a remote debugging request during a remote debugging session; determining, according to an isolation level of the remote debugging request, a server node from a plurality of server nodes in the cloud system for performing the remote debugging, wherein the isolation level of the remote debugging request comprises at least one of: an exclusive level and a sharing level; and in response to determining the server node, forwarding the remote debugging request to the server node.

First claim

What is claimed is:

1. A method for performing a remote debugging in a cloud system, the method comprising:
receiving a remote debugging request during a remote debugging session, wherein the remote debugging request specifies a remote debugging process;
automatically determining an isolation level associated with the remote debugging request, wherein the isolation level of the remote debugging request comprises at least one of: an exclusive level and a sharing level, wherein a server node receiving the remote debugging request is only allowed to respond to other remote debugging requests and establish multiple simultaneous debugging connections during the remote debugging process when the isolation level is the sharing level, and wherein in response to the isolation level being the exclusive level, the server node is exclusively occupied by the remote debugging process during the remote debugging session and does not respond to other requests in a production mode;
selecting, as the server node, a particular node from a plurality of server nodes in the cloud system that is suitable for performing the remote debugging based on the isolation level of the remote debugging request; and
in response to determining the server node, forwarding the remote debugging request to the server node.

2. The method according to claim 1 , further comprising:
in response to the remote debugging session ending, updating a registry of the cloud system to identify a current debugging mode of the server node, wherein the registry identifies the current debugging mode of each of the plurality of server nodes in the cloud system.

3. The method according to claim 2 , wherein updating the registry to identify the current mode of the server node further comprises:
releasing the server node from operating in an exclusive debugging mode.

4. The method according to claim 2 , wherein updating the registry to identify the current mode of the server node further comprises:
determining whether there is an association between an identifier of the remote debugging session and an identifier of the server node; and
in response to determining that there is no association between the identifier of the debugging session and the identifier of the server node, releasing the server node from operating in a sharing debugging mode.

5. The method according to claim 1 , wherein the determining the server node further comprises:
selecting the particular node as the server node responsive to the particular node operating in the production mode for the remote debugging session and the isolation level of the remote debugging request being the exclusive level; and
updating a registry to set a current operating mode of the server node to an exclusive debugging mode, wherein during the exclusive debugging mode an identifier of the remote debugging session is associated in a one-to-one manner with an identifier of the server node.

6. The method according to claim 1 , wherein the determining the server node further comprises:
in response to the isolation level of the remote debugging request being the sharing level, selecting the particular node as the server node for the remote debugging session based on the particular node already operating in a sharing debugging mode; and
updating a registry to add an association between an identifier of the debugging session and an identifier of the server node.

7. The method according to claim 6 , further comprising:
in response to determining that there is currently no server node of the plurality of server nodes that is operating in the sharing debugging mode, selecting the particular node as the server node for the remote debugging session based on the particular node operating in the production mode; and
updating the registry to set the server node to the sharing debugging mode.

8. The method according to claim 1 , wherein in response to the server node receiving the remote debugging request, the server node performs a method comprising:
switching the server node from the production mode to a debugging mode, wherein the debugging mode has an isolation level that is adaptive to the remote debugging request;
providing information on the server node to an initiator of the remote debugging request wherein the information comprises a broadcast message that indicates a current operating mode of the server node;
establishing a debugging connection to the initiator of the remote debugging request to perform the remote debugging process;
determining whether the remote debugging process involves at least one other server node; and
in response to determining that the remote debugging process involves at least one other server node, transmitting a request to perform the remote debugging process to a front-end component of the cloud system.

9. The method according to claim 8 , wherein in response to the isolation level being the exclusive level, the server node only allows a debugging connection to the server node to be established with the initiator of the remote debugging request.

10. The method according to claim 8 , wherein in response to the isolation level being the sharing level, the server node allows a plurality of debugging request initiators to establish a plurality of simultaneous debugging connections with the server node.

11. The method according to claim 8 , wherein the information further comprises a current internet protocol (IP) address and a debugging listening port number of the server node.

12. The method according to claim 1 , further comprising:
selecting the particular node as the server node based on a load of the cloud system.

13. The method according to claim 12 , further comprising:
selecting the particular node as the server node based on an operating mode of each of the plurality of server nodes in the cloud system.

14. The method according to claim 1 , wherein the isolation level indicates a particular debugging mode that a server node receiving the remote debugging request is required to operate in to perform the remote debugging process.

15. The method according to claim 1 , wherein in response to the isolation level being the sharing level, the server node is exclusively occupied by the remote debugging request during the remote debugging process.

Assignees

• IBM

Inventors

• Cai Junjie
• Fei Jia
• Liu Xin Peng
• Wang Heng
• Wu Yan R
• Zhong Si Qi

Classifications

• H04L67/025

  for remote control or remote monitoring of applications · CPC title

• G06F11/362

  Debugging of software · CPC title

• G06F11/3698 Primary

  Environments for analysis, debugging or testing of software · CPC title

• G06F11/3664 Primary

  Physics · mapped topic