Performing a provisioning operation associated with a software application on a subset of the nodes on which the software application is to operate

• US 7,698,391 B2
• Filed: 05/16/2005
• Issued: 04/13/2010
• Est. Priority Date: 05/16/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jerath, Nitin, Manglik, Gaurav, Paliwal, Bharat
• Primary Examiner(s): Harrell; Robert B
• Application Number:
  US11/131,025
• Publication Number:
  US 20060259594A1
• Time in Patent Office: 1,793 Days
• Field of Search: 705/5, 705/6, 705/1, 705/28, 705/26, 705/27, 705/56, 705/35, 705/37, 705/44, 705/10, 705/14, 705/30, 705/7, 709203-205, 709217-219, 709/204, 709220-222, 709206-207, 710 8- 11, 717/121, 717/126, 717/177, 717/101, 725/40, 725/39, 725/37, 725/32, 725/22
• US Class Current: 709/220
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

An application deployment architecture provides the capability to independently invoke different phases of an operation associated with an application, thereby progressively deploying the application across a network of peer nodes and providing fault tolerance. Therefore, applications are easier to deploy on the network of nodes, the deployment process is less error prone, and remediation of deployment errors is simpler than with prior approaches. Tasks constituent to phases of a deployment process are schedulable rather than completely automated and outside the control of the administrator, and are schedulable on a subset of the nodes rather than only on the entire network of nodes.

Claims

1. A computer-implemented method for progressively provisioning a set of nodes in a computing system in which processing is distributed across the set of nodes, the method comprising:

configuring the computing system by;

identifying, to each of the nodes in the set, which nodes are in the set, and

specifying, to each of the nodes in the set, that the nodes in the set operate as peers in the computing system;

wherein configuring the computing system is performed by one or more processors;

wherein the steps of identifying and specifying include;

performing, on a first subset of the nodes, a provisioning operation associated with a software application,

wherein the provisioning operation is one of;

installing the software application,

upgrading the software application, or

patching the software application;

wherein the software application is designed such that instances of the software application interoperate with other instances of the software application on a peer-to-peer basis,

wherein the first subset is less than the entire set of nodes; and

without rolling back the provisioning operation on the first subset of nodes,

performing, on a second subset of the set of nodes, the provisioning operation associated with the software application, wherein the second subset is less than the entire set of nodes and is a different subset of nodes than the first subset of nodes;

wherein, while the provisioning operation associated with the software application is being performed on the first subset of nodes and before the provisioning operation associated with the software application is performed on the second subset of nodes, the second subset of nodes remains online while the first subset of nodes is taken offline for the provisioning operation; and

wherein, after the provisioning operation associated with the software application is performed on the second subset of nodes, instances of the software application that are running on nodes in both the first subset and the second subset are able to interoperate with each other on a peer-to-peer basis.

2. The method of claim 1, wherein performing the provisioning operation on a first subset of nodes includes:

copying application files to a first node of the first subset of nodes;

performing one or more actions on the application files on the first node;

indicating in an inventory associated with the system, that the application files are installed on the first node;

after updating the inventory,

copying the application files to a second node of the first subset of nodes, wherein the second node is a different node than the first node;

performing one or more actions on the application files on the second node; and

indicating in the inventory that the application files are installed on the second node.

3. The method of claim 2, further comprising:

adding a new node to the system;

copying the application files to the new node;

performing one or more actions on the application files on the new node; and

indicating in the inventory that the application files are installed on the new node; and

updating a node list to indicate to the first, second and new nodes that instances of the software application that are installed on the first, second, and new nodes are to interact with each other as peers in the computing system.

4. The method of claim 1, wherein performing the provisioning operation on the first subset of nodes includes:

copying one or more application files to a first node of the first subset of nodes;

separately from copying, performing one or more actions on at least one of the one or more application files on the first node;

updating an inventory that corresponds to the set of nodes to indicate that the one or more application files are installed on the first node;

in response to a failure associated with copying the one or more application files to a second node of the first subset of nodes or with performing one or more actions on the one or more application files on the second node,

identifying at what point in performance of the provisioning operation the failure occurred; and

restarting performance of the provisioning operation on the second node at the point at which the provisioning operation failure occurred, without recopying the application files that were copied before the failure.

5. The method of claim 4, further comprising:

reporting (a) that the one or more application files are installed on the first node, and (b) that a failure occurred in copying, or in performing one or more actions on, the one or more application files on the second node.

6. The method of claim 1,

wherein performing the provisioning operation on the first subset of nodes includes:

disabling the first subset of nodes;

updating the application on the first subset of nodes while instances of the software application that are running on the second subset of nodes continue to provide services;

wherein performing the provisioning operation on the second subset of nodes includes, after updating the application on the first subset of nodes;

disabling the second subset of nodes;

updating the application on the second subset of nodes; and

enabling the first and second subsets of nodes.

7. The method of claim 6, wherein the second subset of nodes consists of only one node.

8. The method of claim 1, wherein said performing the provisioning operation on the first subset of nodes, and said performing the provisioning operation on the second subset of nodes are performed from a single node in response to user input received by a system management tool running on said single node.

9. The method of claim 1, wherein the provisioning operation involves multiple phases, and

the method includes scheduling execution of a particular phase of the multiple phases separately and independently of executing other phases of the multiple phases.

10. The method of claim 1, wherein the software application is a database server, and the instances of the software application are database servers that have shared access to data in a same database.

11. A machine-readable storage device storing one or more sequences of instructions which, when executed by one or more processors, causes the one or more processors to perform:

configuring a computing system in which processing is distributed across a set of nodes, wherein the configuring comprises;

identifying, to each of the nodes in the set, which nodes are in the set, and

specifying, to each of the nodes in the set, that the nodes in the set operate as peers in the computing system;

wherein the identifying and specifying include;

performing, on a first subset of the nodes, a provisioning operation associated with a software application,

wherein the provisioning operation is one of;

installing the software application,

upgrading the software application, or

patching the software application;

wherein the software application is designed such that instances of the software application interoperate with other instances of the software application on a peer-to-peer basis,

wherein the first subset is less than the entire set of nodes; and

without rolling back the provisioning operation on the first subset of nodes, performing, on a second subset of the set of nodes, the provisioning operation associated with the software application, wherein the second subset is less than the entire set of nodes and is a different subset of nodes than the first subset of nodes;

wherein, while the provisioning operation associated with the software application is being performed on the first subset of nodes and before the provisioning operation associated with the software application is performed on the second subset of nodes, the second subset of nodes remains online while the first subset of nodes is taken offline for the provisioning operation; and

wherein, after the provisioning operation associated with the software application is performed on the first subset of nodes and before the provisioning operation associated with the software application is performed on the second subset of nodes, instances of the software application that are running on nodes in the first subset of nodes but not the second subset of nodes are able to interoperate with each other on a peer-to-peer basis; and

wherein, after the provisioning operation associated with the software application is performed on the second subset of nodes, instances of the software application that are running on nodes in both the first subset and the second subset are able to interoperate with each other on a peer-to-peer basis.

12. A machine-readable storage device as recited in claim 11, wherein performing the provisioning operation on a first subset of nodes includes:

copying application files to a first node of the first subset of nodes;

performing one or more actions on the application files on the first node;

indicating in an inventory associated with the system, that the application files are installed on the first node;

after updating the inventory,

copying the application files to a second node of the first subset of nodes, wherein the second node is a different node than the first node;

performing one or more actions on the application files on the second node; and

indicating in the inventory that the application files are installed on the second node.

13. A machine-readable storage device as recited in claim 12, wherein the one or more sequences of instructions further causes the one or more processors to perform:

adding a new node to the system;

copying the application files to the new node;

performing one or more actions on the application files on the new node; and

indicating in the inventory that the application files are installed on the new node; and

updating a node list to indicate to the first, second and new nodes that instances of the software application that are installed on the first, second, and new nodes are to interact with each other as peers in the computing system.

14. A machine-readable storage device as recited in claim 11, wherein performing the provisioning operation on the first subset of nodes includes:

copying one or more application files to a first node of the first subset of nodes;

separately from copying, performing one or more actions on at least one of the one or more application files on the first node;

updating an inventory that corresponds to the set of nodes to indicate that the one or more application files are installed on the first node;

in response to a failure associated with copying the one or more application files to a second node of the first subset of nodes or with performing one or more actions on the one or more application files on the second node,

identifying at what point in performance of the provisioning operation the failure occurred; and

restarting performance of the provisioning operation on the second node at the point at which the provisioning operation failure occurred, without recopying the application files that were copied before the failure.

15. A machine-readable storage device as recited in claim 14, wherein the one or more sequences of instructions further causes the one or more processors to perform:

reporting (a) that the one or more application files are installed on the first node, and (b) that a failure occurred in copying, or in performing one or more actions on, the one or more application files on the second node.

16. A machine-readable storage device as recited in claim 11, wherein performing the provisioning operation on the first subset of nodes includes:

disabling the first subset of nodes;

updating the application on the first subset of nodes while instances of the software application that are running on the second subset of nodes continue to provide services;

wherein performing the provisioning operation on the second subset of nodes includes,

after updating the application on the first subset of nodes;

disabling the second subset of nodes;

updating the application on the second subset of nodes; and

wherein the one or more sequences of instructions further causes the one or more processors to perform enabling the first and second subsets of nodes.

17. A machine-readable storage device as recited in claim 16, wherein the second subset of nodes consists of only one node.

18. A machine-readable storage device as recited in claim 11, wherein said performing the provisioning operation on the first subset of nodes, and said performing the provisioning operation on the second subset of nodes are performed from a single node in response to user input received by a system management tool running on said single node.

19. A machine-readable storage device as recited in claim 11, wherein the provisioning operation involves multiple phases, and wherein the one or more sequences of instructions further causes the one or more processors to perform scheduling execution of a particular phase of the multiple phases separately and independently of executing other phases of the multiple phases.

20. A machine-readable storage device as recited in claim 11, wherein the software application is a database server, and the instances of the software application are database servers that have shared access to data in a same database.