Abstract: Reducing classloading of hierarchically configured applications via provisioning is disclosed. In one example, a hierarchically configured application is launched within a first container of a container application platform according to a set of resource descriptions that define a structure of the hierarchically configured application, valid operations may be performed by elements of the hierarchically configured application, and handlers for each operation. After the process of loading the classes representing the resource descriptions and operation handlers is performed, services to be used by the hierarchically configured application are installed. The state of each service is then determined, and one or more serialized data structures representing the state of the services is generated.

Abstract: In order to facilitate automatic roll-forward updates, embodiments include detecting a failure in a software package. In response to the failure, data indicative of a current version of a software package is extracted from a release directory. In response to the application data, a base repository with a version history of the application is cloned. In response to the cloning, a prior set of changes from the base repository in the temporary directory, where the prior set of changes form an old application version of the application, is imported. In response to the import of the prior set of changes, the current version is overwritten with the prior set of changes to generate a new version. The new version is pushed directly to the base repository and a deployment API causes the new version to replace the current version.

Abstract: Identifying a trace based on wait chain coverage analysis comprises identifying a scenario covered by a plurality of traces, as well as a plurality of scenario phases. Each phase has corresponding phase beginning and ending, and is covered by corresponding trace(s) of the plurality of traces. For each prior instance of each phase, a corresponding wait chain comprising a series of wait operations is identified. After identifying signatures configured to match a subset of wait operations in wait chain(s), at least a signature coverage is calculated over the identified corresponding wait chains. The signature coverage characterizes portions(s) of these wait chains that are matched by the signature(s). Based on calculating the signature coverage, one or more of the plurality of traces are identified as having unknown wait states, based on the identified trace(s) corresponding to a larger amount of uncovered wait chain portions than others of the plurality of traces.

Abstract: A system writes to a replicated direct access storage device (DASD) a record of each step within a job as each step begins and as each step completes. The records are maintained on the replicated DASD for a predetermined period of time. The predetermined period of time is, for example, the greatest amount of lag in replication of all storage systems operating within the system. The records are stored, for example, in an open jobs and datasets (OJD) file, where the file itself is a dataset. The dataset is written to by an online task (e.g., OJDSTC) which gathers input from two sources. Upon job completion, the records are stored, for example, in an OJD journal and removed from the OJD file.

Abstract: The application pertains to the automated deployment of software packages to an enterprise's testing, staging and production environments. It does this by detecting events with respect to the enterprise's code base and, upon detection of a change in a package, identifies the application(s) that include that package. For each such application, a workflow is provided defining a pipeline of environments in which a bundle of packages that make up that application are to be installed for testing, staging or production. A software package in which an event has occurred is installed in those environments on a stepwise basis per that workflow and the application is (re)built there for testing, etc. A status of the bundle of packages that make up an application in each of the respective environments is shown in a graphical user interface.

Abstract: A high parallelism computing system and instruction scheduling method thereof are disclosed. The computing system comprises: an instruction reading and distribution module for reading a plurality of types of instructions in a specific order, and distributing the acquired instructions to corresponding function modules according to the types; an internal buffer for buffering data and instructions for performing computation; a plurality of function modules each of which sequentially executes instructions of the present type distributed by the instruction reading and distribution module and reads the data from the internal buffer; and wherein the specific order is obtained by topologically sorting the instructions according to a directed acyclic graph consisting of the types and dependency relationships.

Abstract: Systems and methods are provided for transcompiling non-distributed source code for a nondistributed software program into a distributed software package for implementation on a distributed computing system. A transcompiler can identify loops within non-distributed source code written in a data-driven language. The transcompiler can generate MapReduce jobs using mapper keys based on grouping indicators associated with each of the loops. The MapReduce jobs can be linked together based on input-output connections of the loops in the non-distributed source code. Then, the transcompiler can generate a distributed software package including the generated MapReduce jobs to implement the same functionality as the non-distributed source code on the distributed computing system, thereby improving the speed of execution over very large datasets. The distributed software package can be optimized using machine learning searching algorithms.

Abstract: A method for semi-automated development data management for control devices includes saving a development data model in a central data store comprising a plurality of mutually related configuration data units, wherein the configuration data units each store control commands and/or configuration parameters. The method further includes providing a ruleset and identifying an initial configuration data unit, wherein it is possible, using the ruleset, to identify further configuration data units automatically on a basis of a relationship thereof with the initial configuration data unit. In addition, the method includes applying the provided ruleset to the development data model in order to identify a subset of configuration data units within the development data model and saving the identified subset.

Abstract: An information processing apparatus which transmits data to setup predetermined software in a terminal includes a processor. The processor is configured to perform the following processing operation, a receiving process which receives registration of user information, a first generating process which generates an installer to install the data including user identification information to identify a user according to the user information received in the receiving process, a setting process which sets the installer generated in the first generating process to be downloadable, and a first transmitting control process which transmits to a terminal in which the installer is started the data corresponding to the user information when the installer is downloaded and started, and the terminal in which the installer is started is connected to the information processing apparatus through a network.

Abstract: A sourcing interface enables a particular device communicatively connected on a network to share one or more resources of the particular device with other devices communicatively connected to the network and coordinate task bidding with the other through broadcasting requests on the network. The sourcing interface manages dispatch of a particular task to one or more selected devices, the one or more selected devices selected based on one or more bids received by the particular device that best match a service level of particular request by the particular device, the dispatched task migrated to the one or more selected devices instead of handled by a web service provider. The sourcing interface monitors, at the particular device, for a result of execution of the particular task from the one or more selected devices, the one or more selected devices collecting telemetry data for usage reporting to the web service provider.

Abstract: An information processing apparatus which transmits data to setup predetermined software in a terminal includes a processor. The processor is configured to perform the following processing operation, a receiving process which receives registration of user information, a first generating process which generates an installer to install the data including user identification information to identify a user according to the user information received in the receiving process, a setting process which sets the installer generated in the first generating process to be downloadable, and a first transmitting control process which transmits to a terminal in which the installer is started the data corresponding to the user information when the installer is downloaded and started, and the terminal in which the installer is started is connected to the information processing apparatus through a network.

Abstract: Methodologies and systems are described herein whereby application functionality may be optimized and extended based on a contextual analysis of the features that are accessed within the application. In one or more embodiments, the contextual analysis includes (a) detecting that an end user of an application is using a particular feature of the application and (b) determining that a set of one or more third-party applications are configured for operations accessing data sets of the same type accessed by the particular feature. Responsive at least to the detecting and determining operations, the set of one or more third-party applications are presented to the user when the user is accessing the particular feature of the first application.

Abstract: A request to install an application on a device may be received, and data associated with the device and a set of users associated with the device may be received. Acceptance factors specified in a terms and conditions document associated with the application to be installed on the device may be identified. A terms and conditions implication of installing the application on the device may be determined based on the acceptance factors. Based on the terms and conditions implication, a rule may be dynamically generated to control at least a running of the application on the device. The rule may be activated or caused to be activated on the device. The activation of the rule may control the running of the application on the device.

Abstract: Methods, systems, and computer-readable storage media for deploying upgrade packages during zero downtime upgrade of production systems include actions of receiving an upgrade package, the upgrade package defining one or more changes to be deployed to a system that has already undergone partial deployment during a zero downtime upgrade, and including one or more objects having respective object types, receiving a deployment configuration, the deployment configuration providing a plurality of lists of object types for respective constraints and, for each list of object types, specifying a deployment option for object types in the respective list of object types, determining a set of object types included in the upgrade package, the set of object types comprising one or more object types, and selectively permitting deployment of the upgrade package to execute the one or more changes based on the set of object types and the plurality of lists of object types.

Abstract: A user that installed an application, user information regarding a user who is registered as frequently using the application, and the application are managed in association, and at the time of menu display, display of icons is controlled according to whether or not a logged-in user is included in the user information associated with the application. In addition, control is performed such that, when uninstalling an application, the application is actually uninstalled or only user information is deleted based on user information associated with the application.

Abstract: Behavioral intelligence can be used with cloud native computing to enhance software deployment for various infrastructures by analyzing and deploying software functions according to the various infrastructures. Because different providers can have their own systems and controls for managing their infrastructures, it is costly to deploy software functions that are coupled together. However, if the software functions are disaggregated and translated according to the systems and controls relative to the various infrastructures, then the software functions can be failed and scaled independently of one another, thereby generating efficiencies.

Abstract: A method and apparatus for determining the impact of a software upgrade on a service performance are disclosed. The method obtains call detail records associated with a plurality of mobile user endpoint devices, aggregates each mobile user endpoint device into at least one group, maps each mobile user endpoint device to at least one first aggregate, wherein each aggregate of the at least one first aggregate comprises at least one of: a group established based on the type of each of the mobile user endpoint devices, a group established based on the make of each of the mobile user endpoint devices, or a group established based on the model of each of the mobile user endpoint devices, and identifies a nearest co-occurring software upgrade when a change in a service performance in the communications network is detected based on the at least one first aggregate.

Abstract: Techniques are disclosed relating to distributing software packages among servers in a data storage facility. In various embodiments, a package distribution computer system receives an indication that a software package is to be distributed to a plurality of server systems. In some embodiments, the computer system determines a division of the plurality of server systems into two or more groups for distributing the software package. In some embodiments, for a given group, the computer system selects a server system to retrieve the software package and facilitate peer-to-peer distribution of the software package to remaining server systems within the given group. In some embodiments, the computer system receives metadata specifying one or more files included in the software package. In some embodiments, the computer system provides the metadata to at least one of the remaining server systems in the given group for retrieving the software package from the selected server system.

Abstract: Technologies for lifecycle management include multiple computing devices in communication with a lifecycle management server. On boot, a computing device loads a lightweight firmware boot environment. The lightweight firmware boot environment connects to the lifecycle management server and downloads one or more firmware images for controllers of the computing device. The controllers may include baseboard management controllers, network interface controllers, solid-state drive controllers, or other controllers. The lifecycle management server may select firmware images and/or versions of firmware images based on the controllers or the computing device. The computing device installs each firmware image to a controller memory device coupled to a controller, and in use, each controller accesses the firmware image in the controller memory device. The controller memory device may be a DRAM device or a high-performance byte-addressable non-volatile memory. Other embodiments are described and claimed.

Abstract: In some examples, a server may determine a plurality of variables associated with a software package. For example, the plurality of variables may include a size of the software package, a reboot variable associated with the software package indicating whether a reboot is to be performed after installing the software package, and an installation type indicating whether the software package is a first install or an upgrade. The server may execute a machine learning model to determine, based on the plurality of variables, a risk score predicting an installation success rate of the software package. The server may select a deployment strategy from a plurality of deployment strategies based at least in part on the risk score and the plurality of variables. The server may provide the software package to a plurality of computing devices in accordance with the deployment strategy.