Abstract: Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for placing an application in an external environment such as a cloud or edge environment, when it is rendered unavailable on a local environment such as a local host. The application's instance is moved after a connection test reveals that the application, related applications, and/or underlying physical computing devices hosting the applications and/or their data, do not respond to the test within an acceptable level of performance. By placing the application instances in an external environment, the application(s) can continue to provide an adequate level of service to one or more users until the application can be restored to its better function local host.

Abstract: Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for creating and executing migration workflows to replicate or migrate data from one device or set of devices to another device or set of devices. The embodiments perform checks both before a migration and after the migration is completed to determine if the migrated application and those applications and devices related to it are sufficiently connected and are functioning. Each application or device associated with one or more applications that have been migrated are message in order to determine that all related applications and/or components such as storage devices are communicating in a sufficient manner to provide a desired level of performance to a user of the one or more applications.

Abstract: A method for managing application migration includes: inferring dependencies and connectivity among applications executing on a system; generating a target infrastructure node (IN) configuration template based on the inferred dependencies and connectivity; making a determination that a configuration of a target IN does not satisfy the template, in which an application is executing on an IN, in which the application is not executing on the target IN; in response to the determination: obtaining a weight for each inferred parameter in the template, in which the inferred parameters comprises the inferred dependencies and connectivity, in which the weight for each inferred parameter is configured by a user; executing, based on the weights, a model to obtain a deviation score for a second target IN; generating, based on the deviation score, a migration recommendation specifying the second target IN; and initiating a display of the migration recommendation to the user.

Abstract: Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for performing a connection test prior to bringing an application on-line. The method determines a best time to perform a connection test on an application that is currently off-line and at that time performs the connection test. The connection test is performed between the first application and those applications and components to which it is related. The connection test establishes whether prior to bringing the application on-line, for example after a migration, the connections between it and all the applications and components that are related to it have been re-established with performance within a predetermined threshold.

Abstract: Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for creating and executing migration workflows to replicate or migrate data from one device or set of devices to another device or set of devices. In one or more embodiments, migrations involve obtaining relationship information with regards to the applications that will be migrated from one device to another device or set of devices. This relationship information is used to determine which applications and/or other system resources are affected by the migration, including those applications/system resources that are not being migrated. The migrations are performed in such a way to minimize inconvenience to the end users, by having the migration take place at a time when both the application being migrated, and related applications have reduced usage or idle time.

Abstract: A method for managing application migration includes: inferring dependencies and connectivity among applications executing on a distributed system, in which the applications are operatively connected through a network; generating a target infrastructure node (IN) configuration template based on the inferred dependencies and connectivity; making a determination that a configuration of a target IN satisfies the target IN configuration template, in which an application is executing on an IN, in which the application is not executing on the target IN, in which the distributed system comprises the IN and the target IN; initiating migration, based on the determination, the application to the target IN.

Abstract: Techniques for state prediction and failure prevention are disclosed. For example, a method comprises receiving data corresponding to operation of a plurality of elements, wherein the plurality of elements comprise at least one of a plurality of devices and a plurality of device components. The data corresponding to the operation of the plurality of elements comprises one or more operational states for respective ones of the plurality of elements. Using one or more machine learning algorithms, a future operational state of one or more elements of the plurality of elements is predicted. The prediction is based, at least in part, on the data corresponding to the operation of the plurality of elements. Using the one or more machine learning algorithms, one or more actions to prevent the one or more elements from transitioning to the future operational state are identified.

Abstract: Techniques for detecting a modification to a configuration of a system are disclosed. For example, a method comprises the step of collecting a first data set for a system at a first time instance, wherein the first data set comprises inventory data for a configuration of the system present at the first time instance. The method compares the first data set to a second data set, wherein the second data set comprises inventory data for a configuration of the system present at a second time instance. The method obtains a third data set based on the comparison of the first data set and the second data set, wherein the third data set comprises data indicative of any differences between the inventory data for the configuration of the system present at the first time instance and the inventory data for the configuration of the system present at the second time instance.

Abstract: A method for performing an application upgrade includes: performing an emulation to generate an application upgrade strategy for applying a plurality of application upgrades on a client device; determining a user behavior of a user of the client device; generating an application upgrade summary list using the application upgrade strategy and the user behavior; providing the application upgrade summary list to the user of the client device; and after the providing, initiating upgrading of the client device using a reordered application upgrade strategy generated in response to feedback from the user, in which the reordered application upgrade strategy is generated based on the application upgrade strategy and the user behavior.

Abstract: A method for managing an application upgrade includes: making a first determination that an urgent fix is received from an application monitoring agent; making, based on the first determination, a second determination that a high priority network slice of a network exists; mapping, based on the second determination, the urgent fix to the high priority network slice; making a third determination that a prerequisite fix is required; mapping the prerequisite fix to the high priority network slice; sending the prerequisite fix and the urgent fix to the reordering engine; reordering at least one fix available in a receiving queue of the reordering engine to prioritize the prerequisite fix and the urgent fix in the receiving queue; sending the prerequisite fix and the urgent fix to a client device upgrade manager; and initiating upgrading of a client device based on the prerequisite fix and the urgent fix.

Abstract: A method for managing data migration includes: obtaining a confidence level of a predicted failure state of an internal component (IC) of a source device, in which the IC is one of a plurality of ICs in the source device; making a first determination that the confidence level exceeds a predetermined confidence level threshold; making, based on the first determination, a second determination that a high priority network slice of a network exists; mapping, based on the second determination, data stored in the IC to the high priority network slice; and migrating the data to a target device via the high priority network slice.

Abstract: A method for generating an upgrade recommendation for a communication network includes: analyzing a dataset to generate a request category, in which the dataset comprises at least a request, a response to the request, and a corresponding response time, in which the request and the response are communicated over the communication network; generating a network slice corresponding to the request category; executing an emulation using the network slice and the request to generate an emulated response time for the request; comparing the emulated response time against the corresponding response time; determining, based on the comparison, a response time variation for the request; and generating the upgrade recommendation based on the response time variation.

Abstract: A method for managing data migration includes: obtaining a confidence level of a predicted failure state of a storage component (SC) of a source device; making a first determination that the confidence level exceeds a minimum threshold; making, based on the first determination, a second determination that a high priority network slice of a network exists; mapping data stored in the SC to the high priority network slice; migrating the data to a target device; after migrating the data to the target device: obtaining a confidence level of a predicted failure state of a processing component (PC); making a third determination that the confidence level of the predicted failure state of the PC exceeds a maximum threshold; mapping, based on the third determination, non-migrated data stored in the source device to the high priority network slice; and migrating the non-migrated data to the target device.

Abstract: A method for managing data migration includes: obtaining a confidence level of a predicted failure state of a storage component (SC) of a source device; making a first determination that the confidence level exceeds a minimum threshold; making, based on the first determination, a second determination that a high priority network slice of a network exists; mapping data stored in the SC to the high priority network slice; migrating the data to a target device; after migrating the data to the target device: obtaining a confidence level of a predicted failure state of a processing component (PC); making a third determination that the confidence level of the predicted failure state of the PC exceeds a maximum threshold; mapping, based on the third determination, non-migrated data stored in the source device to the high priority network slice; and migrating the non-migrated data to the target device.

Abstract: A method for managing a client environment includes obtaining, by a predictor, a future state prediction request associated with an application upgrade on an emulation of a client device, wherein the application upgrade failed; in response to the future state prediction request: obtaining live data associated with the application upgrade; performing natural language processing on the live data to obtain processed live data; applying a future state prediction model to the processed live data to generate a future state prediction; and initiating the remediation of the application upgrade based on the future state prediction.

Abstract: A method for managing an application upgrade includes: obtaining metadata of a client device from a production host (PH) client device twin; executing, using the metadata, an emulation to generate an application upgrade strategy for applying a plurality of application upgrades; setting, using the metadata, a first entry in a PH required properties file; transferring the application upgrade strategy and the first entry from the PH client device twin to a client environment (CE) client device twin; storing, the application upgrade strategy and the first entry in a CE required properties file; initiating the plurality of application upgrades based on the application upgrade strategy and the first entry; setting a second entry in a CE reported properties file; transferring the second entry from the CE client device twin to the PH client device twin; and verifying a status of the plurality of application upgrades using the second entry.

Abstract: Techniques are disclosed for equipment support management comprising proactive identification and remediation for one or more impacted components of the equipment using a machine learning-based approach. By way of one example, a method identifies, for given equipment comprising a plurality of components, one or more components of the plurality of components that may be impacted by another component of the plurality of components for which an issue has been reported, wherein one or more machine learning-based algorithms are used to perform at least a portion of the identification. The method then generates, for the given equipment, a plan to proactively remedy the one or more identified components in conjunction with remedying the issue-reported component. In some further examples, a relevance tree is used to identify the one or more impacted components.

Abstract: A method for managing an application upgrade includes: obtaining metadata of a client device from a production host (PH) client device twin; executing, using the metadata, an emulation to generate an application upgrade strategy for applying a plurality of application upgrades; setting, using the metadata, a first entry in a PH required properties file; transferring the application upgrade strategy and the first entry from the PH client device twin to a client environment (CE) client device twin; storing, the application upgrade strategy and the first entry in a CE required properties file; initiating the plurality of application upgrades based on the application upgrade strategy and the first entry; setting a second entry in a CE reported properties file; transferring the second entry from the CE client device twin to the PH client device twin; and verifying a status of the plurality of application upgrades using the second entry.

Abstract: A method for modifying a communication network includes: making a first determination, using monitored data, that scaling is required; in response to the first determination, executing an emulation using a modified network slice and the monitored data to generate an emulated response time, in which the monitored data comprises at least a request, a response to the request, and a corresponding response time for the request, in which the monitored data is analyzed to generate the modified network slice; making, based on the emulated response time, a second determination to implement the modified network slice; and initiating modification of the communication network using the modified network slice.

Abstract: A method for managing a client environment includes obtaining, by a remediation orchestrator, a remediation request associated with a failed application upgrade on an emulation of a client device; in response to the remediation request: obtaining a remediation policy associated with the application upgrade; obtaining application upgrade information associated with the application upgrade; identifying remediation steps to service the remediation request using the application upgrade information and the remediation policy; and initiating performance of the application upgrade and the remediation steps on the client device.