Abstract: An approach is provided for determining a carbon footprint-based consumption of cloud resources. Cloud resource requirements and a carbon footprint cap of a workload of a cloud consumer are received. The requirements and cap are based on a sustainability target, published by the cloud consumer, and subscribed by cloud service providers. A list of cloud resources that satisfy the requirements are sent. Carbon emission values of the cloud resources at different load levels of the workload are sent. Based on a service level agreement requirement, a criticality level, and a peak load duration of the workload, and previous success rates of satisfying cloud resource requirements by cloud service providers, an optimized configuration of cloud resource(s) and cloud service provider(s) is selected. The cloud resource(s) are selected from the list and have a carbon footprint that does not exceed the cap at a given load level.

Abstract: A set of profile parameters to characterize an unknown group of servers is computed. A set of known groups of servers is selected from a historical repository of known group of servers. A subset of known group is selected such that each known group in the subset has a corresponding similarity distance that is within a threshold similarity distance from the unknown group. A decision tree is constructed corresponding to a known group in the subset, by cognitively analyzing a usage of the set of profile parameters of the unknown group in the known group. Using the decision tree a number of problematic servers is predicted in the unknown group. When the predicted number of problematic servers does not exceed a threshold number, a post-prediction action is caused to occur on the unknown group, which causes a reduction in an actual number of problematic servers in the unknown group.

Abstract: Aspects of the present invention disclose a method, computer program product, and system for multi-factor authentication. In response to a request for an action, the method includes one or more processors whether a first authentication credential passes validation. In response to determining that the first authentication credential does pass validation, the method further includes one or more processors determining a second authentication credential, wherein the second authentication credential includes an indication of a wireless connection between a first computing device and a second computing device. The method further includes one or more processors determining whether the second authentication credential passes validation. In response to determining that the second authentication credential passes validation, the method further includes one or more processors allowing execution of the requested response.

Abstract: Aspects of the present invention disclose a method, computer program product, and system for multi-factor authentication. In response to a request for an action, the method includes one or more processors whether a first authentication credential passes validation. In response to determining that the first authentication credential does pass validation, the method further includes one or more processors determining a second authentication credential, wherein the second authentication credential includes an indication of a wireless connection between a first computing device and a second computing device. The method further includes one or more processors determining whether the second authentication credential passes validation. In response to determining that the second authentication credential passes validation, the method further includes one or more processors allowing execution of the requested response.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and Impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and Impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and Impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and Impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: A set of profile parameters to characterize an unknown group of servers is computed. A set of known groups of servers is selected from a historical repository of known group of servers. A subset of known group is selected such that each known group in the subset has a corresponding similarity distance that is within a threshold similarity distance from the unknown group. A decision tree is constructed corresponding to a known group in the subset, by cognitively analyzing a usage of the set of profile parameters of the unknown group in the known group. Using the decision tree a number of problematic servers is predicted in the unknown group. When the predicted number of problematic servers does not exceed a threshold number, a post-prediction action is caused to occur on the unknown group, which causes a reduction in an actual number of problematic servers in the unknown group.

Abstract: File selection techniques that can handle overlapping module contexts provide flexible and reversible backup, restore, migration, deployment and synchronization operations. Both remote (administrative) control and local (user) control of the file selection are provided. Application and configuration specific templates are provided to a user from the remote administrator for further customization by selecting or de-selecting configurations, applications and/or individual files or configuration entries. The templates may be controlled geographically by the IP address or identity associated with the user. A user's interaction with the customization is saved and the order of changes is maintained, so that when the templates are updated, the user's customizations can be re-applied. The administrator may override user settings based on rules, which may also be geographically determined. The file selection may also be altered based on media type and location, e.g., local backup vs. server backup.

Abstract: A method and associated systems for predicting a degree of risk associated with a planned change to a computer server or other electronic component. A computerized change-management system receives Probability and Impact inputs derived from user-derived input, from which it determines a Baseline risk of change failure. The system processes mined data to determine an historic change-failure rate as a function of a type of change, and computes a predictive incident probability based on a predictive analytics engine's forecast of whether a particular type of server will be problematic. The system then computes a final Change Risk by adjusting the Baseline risk as a function of the historic change-failure rate, the predictive incident-probability, and a Baseline-specific weighting factor. If the resulting Change Risk is judged to be elevated, the system initiates collateral actions and notifications intended to reduce the probability and impact of a change failure.

Abstract: Conflict management for calendar events is provided. A schedule of a user has one or more schedule entries, each corresponding to an event that the user is available to attend. A waitlist of the user has one or more waitlist entries, each corresponding to an event that the user is unavailable to attend. Whether the user is available to attend a new event is determined based, at least in part, on a priority of the new event and the one or more schedule entries. A new entry is added to one of the waitlist and the schedule based, at least in part, on whether the user is available to attend the new event. A change in user availability is identified for at least one time period and, in response, an availability determination is updated for an event that at least partially coincides with the at least one time period.

Abstract: Conflict management for calendar events is provided. A schedule of a user has one or more schedule entries, each corresponding to an event that the user is available to attend. A waitlist of the user has one or more waitlist entries, each corresponding to an event that the user is unavailable to attend. Whether the user is available to attend a new event is determined based, at least in part, on a priority of the new event and the one or more schedule entries. A new entry is added to one of the waitlist and the schedule based, at least in part, on whether the user is available to attend the new event. A change in user availability is identified for at least one time period and, in response, an availability determination is updated for an event that at least partially coincides with the at least one time period.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: A modification method and system. The method includes retrieving by a computer processor of a computing system a list of features and plug-ins associated with an application. The features include features version metadata and the plug-ins include plug-ins version metadata. The computer processor compares features source code associated with the features with previous versions of associated source code. The computer processor generates modified features version metadata associated with the features version metadata. The modified features version metadata includes updated version labels differing from previous version labels of the previous versions of associated source code. The features are assembled into an application.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: Embodiments of the present invention provide an approach to automatically convert existing support materials (support manuals, troubleshooting guides, content, help files, etc.) into machine-executable programs so as to obviate for manual execution of the steps described in the support materials. That is, the embodiments of the invention will (among other things): create support-based programs that automate the execution of previously manual steps; create an inventory of said programs; parse existing support documentation; map sections of each support document into existing program automation; construct a sequence of program automations that resemble the flow of each support document; and/or associate a constructed sequence of automation with a support document that could be executed automatically.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.

Abstract: An approach is provided for validating translated files for inclusion in an application being developed. Content in a natural language is translated into another language and received as a first translation in a first translated file. Based on an error condition indicated by simulations of loading and presenting the first translation in a user interface of the application, a syntax error that causes the error condition is determined. The syntax error can include a lack of a match between a key and exactly one value, a missing key, or a mismatch of placeholders in the first translated file. Responsive to a receipt of a second translation of the content that includes the correction of the syntax error, and based on simulations of loading and presenting the second translation in the interface not indicating the error condition, the second translation is presented at runtime without causing the application to stop running.