Flexible upgrade of multi-subsystem products
Described is a system that provides for granular and customized upgrades of sub-systems deployed within a third-part system. The system generates an upgrade manager service for implementation of a first sub-system upgrade package from within a third-party system that hosts the first sub-system. The system generates the first sub-system upgrade package according to a compatibility with a first sub-system version currently deployed in the third-party system to update the first sub-system with a feature(s) available in an upgraded version of the first sub-system. The system sends the upgrade manager service to the third-party system. The system receives a first request for the first sub-system upgrade package from the upgrade manager service running in the third-party system. The system sends the first sub-system upgrade package for implementation at the first sub-system by the upgrade manager service running in the third-party system.
1. A computer-implemented method comprising:
generating an upgrade manager service for upgrading at least a first sub-system, the upgrade manager service being configured to: (i) run within a master sub-system, (ii) retrieve a first sub-system upgrade package generated for the first sub-system from the master sub-system, and (iii) implement the first sub-system upgrade package by the upgrade manager service running in the master sub-system in communication with the first sub-system;
generating the first sub-system upgrade package according to a compatibility with any corrections to the first sub-system currently deployed in the master sub-system to update the first sub-system with at least one feature available in an upgraded version of the first sub-system, the first sub-system upgrade package including a section for the upgrade manager service and a section for upgrade files for the first sub-system;
receiving a first request for the first sub-system upgrade package from the upgrade manager service running in the master sub-system;
sending the first sub-system upgrade package to the master sub-system; and
implementing the first sub-system upgrade at the first sub-system by the upgrade manager service running in the master sub-system.
2. The computer-implemented method of claim 1 , further comprising:
generating a second sub-system upgrade package according to a compatibility with a second sub-system version to update a second sub-system with at least one feature available in an upgraded version of the second sub-system, the feature available in the upgraded version of the first sub-system being different than the feature available in the upgraded version of the second sub-system;
receiving a second request for the second sub-system upgrade package from the upgrade manager service running in the master sub-system; and
sending the second sub-system upgrade package for implementation at the second sub-system by the upgrade manager service running in the master sub-system.
3. The computer-implemented method of claim 2 , further comprising:
generating the upgrade manager service to perform a pre-check of the first sub-system from within the master sub-system prior to the implementation of the first sub-system upgrade package.
4. The computer-implemented method of claim 3 , further comprising at least one of:
identifying one or more policies associated with the first sub-system;
determining a status of at least one proxy backing up the first sub-system; and
determining a status of storage associated with the first sub-system.
5. The computer-implemented method of claim 4 , further comprising:
determining whether backed-up data will be compatible with the feature available in the upgraded version of the first sub-system.
6. The computer-implemented method of claim 5 , further comprising:
generating the upgrade manager service to provide an opt-out option prior to the implementation of the first sub-system upgrade package based on a determination of an incompatibility between the backed-up data and the feature available in the upgraded version of the first sub-system.
7. The computer-implemented method of claim 2 , further comprising:
generating the second sub-system upgrade package in accordance with a data dependency currently existing between the first and the second sub-systems, wherein the implementation of the second sub-system upgrade package, by the upgrade manager service running in the master sub-system, complies with the data dependency between the first and the second sub-systems.
8. A system comprising:
one or more processors; and
a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to:
generate an upgrade manager service for upgrading at least a first sub-system hosted by a master sub-system, the upgrade manager service being configured to: (i) run within the master sub-system, (ii) retrieve a first sub-system upgrade package generated for the first sub-system, and (iii) implement the first sub-system upgrade package by the upgrade manager service running in the master sub-system;
generate the first sub-system upgrade package according to a compatibility with any corrections to the first sub-system currently deployed in the master sub-system to update the first sub-system with at least one feature available in an upgraded version of the first sub-system, the first sub-system upgrade package including a section for the upgrade manager service and a section for upgrade files for the first sub-system;
send the upgrade manager service to the master sub-system;
receive a first request for the first sub-system upgrade package from the upgrade manager service running in the master sub-system;
send the first sub-system upgrade package to the master sub-system; and
implement the first sub-system upgrade package at the first sub-system by the upgrade manager service running in the master sub-system.
9. The system of claim 8 , wherein the plurality of instructions, when executed, further cause the one or more processors to:
generate a second sub-system upgrade package according to a compatibility with a second sub-system version to update a second sub-system with at least one feature available in an upgraded version of the second sub-system, the feature available in the upgraded version of the first sub-system being different than the feature available in the upgraded version of the second sub-system;
receive a second request for the second sub-system upgrade package from the upgrade manager service running in the master sub-system; and
send the second sub-system upgrade package for implementation at the second sub-system by the upgrade manager service running in the master sub-system.
10. The system of claim 9 , wherein the plurality of instructions, when executed, further cause the one or more processors to:
generate the upgrade manager service to perform a pre-check of the first sub-system from within the master sub-system prior to the implementation of the first sub-system upgrade package.
11. The system of claim 10 , wherein the pre-check of the first sub-system comprises at least one of:
an identification of one or more policies associated with the first sub-system;
a determination of a status of at least one proxy backing up the first sub-system; and
a determination of a status of storage associated with the first sub-system.
12. The system of claim 11 , wherein the determination of a status of at least one proxy backing up the first sub-system comprises:
a determination of whether backed-up data will be compatible with the feature available in the upgraded version of the first sub-system.
13. The system of claim 12 , wherein the plurality of instructions, when executed, further cause the one or more processors to:
generate the upgrade manager service to provide an opt-out option prior to the implementation of the first sub-system upgrade package based on a determination of an incompatibility between the backed-up data and the feature available in the upgraded version of the first sub-system.
14. The system of claim 9 , wherein the plurality of instructions, when executed, further cause the one or more processors to:
generate the second sub-system upgrade package in accordance with a data dependency currently existing between the first and the second sub-systems, wherein the implementation of the second sub-system upgrade package, by the upgrade manager service running in the master sub-system, complies with the data dependency between the first and the second sub-systems.
15. A computer program product comprising a non-transitory computer-readable medium having a computer-readable program code embodied therein to be executed by one or more processors, the program code including instructions to:
generate an upgrade manager service for upgrading at least a first sub-system, the upgrade manager service being configured to: (i) run within a master sub-system, (ii) retrieve a first sub-system upgrade package generated for the first sub-system from the master sub-system, and (iii) implement the first sub-system upgrade package by the upgrade manager service running in the master sub-system in communication with the first sub-system;
generate the first sub-system upgrade package according to a compatibility with any corrections to the first sub-system currently deployed in the master sub-system to update the first sub-system with at least one feature available in an upgraded version of the first sub-system, the first sub-system upgrade package including a section for the upgrade manager service and a section for upgrade files for the first sub-system;
receive a first request for the first sub-system upgrade package from the upgrade manager service running in the master sub-system;
send the first sub-system upgrade package to the master sub-system; and
implement the first sub-system upgrade at the first sub-system by the upgrade manager service running in the master sub-system.
16. The computer program product of claim 15 , wherein the program code includes further instructions to:
generate a second sub-system upgrade package according to a compatibility with a second sub-system version to update a second sub-system with at least one feature available in an upgraded version of the second sub-system, the feature available in the upgraded version of the first sub-system being different than the feature available in the upgraded version of the second sub-system;
receive a second request for the second sub-system upgrade package from the upgrade manager service running in the master sub-system; and
send the second sub-system upgrade package for implementation at the second sub-system by the upgrade manager service running in the master sub-system.
17. The computer program product claim 16 , wherein the program code includes further instructions to:
generate the upgrade manager service to perform a pre-check of the first sub-system from within the master sub-system prior to the implementation of the first sub-system upgrade package.
18. The computer program product claim 17 , wherein the pre-check of the first sub-system comprises at least one of:
an identification of one or more policies associated with the first sub-system;
a determination of a status of at least one proxy backing up the first sub-system; and
a determination of a status of storage associated with the first sub-system.
19. The computer program product claim 18 , wherein the program code includes further instructions to:
determine whether backed-up data will be compatible with the feature available in the upgraded version of the first sub-system.
20. The computer program product claim 19 , wherein the program code includes further instructions to:
generate the upgrade manager service to provide an opt-out option prior to the implementation of the first sub-system upgrade package based on a determination of an incompatibility between the backed-up data and the feature available in the upgraded version of the first sub-system; and
generate the second sub-system upgrade package in accordance with a data dependency currently existing between the first and the second sub-systems, wherein the implementation of the second sub-system upgrade package, by the upgrade manager service running in the master sub-system, complies with the data dependency between the first and the second sub-systems.