Abstract: A blockchain configuration may be used to store smart contracts. One example method of operation may include one or more of identifying a metric configuration associated with a smart contract stored in a blockchain, logging an event which is part of the metric configuration, determining whether the event supports requirements of the smart contract, determining whether a smart contract policy in the smart contract matches a system policy, and updating the smart contract on the blockchain when the requirements of the smart contract are supported by the event and the smart contract policy matches the system policy.

Abstract: The creation of a private sub-blockchain from a main blockchain is disclosed including receiving a request including a trust requirement and an agility requirement, receiving monitoring data from at least one of a plurality of validator nodes of the main blockchain, the monitoring data generated by monitoring the execution of transactions and the exchange of consensus messages by one or more of the plurality of validator nodes, determining a minimum number of validator nodes required to meet the trust requirement, identifying a subset of the plurality of validator nodes of the main blockchain that meets the agility requirement based on the received monitoring data, the subset containing at least the determined minimum number of validator nodes required to meet the trust requirement, and creating a private sub-blockchain of the main blockchain, the private sub-blockchain including the identified subset of the plurality of validator nodes of the main blockchain.

Abstract: A blockchain configuration may be used to store a distributed ledger for product review verification procedure. One example method of operation may include receiving a product review for a product purchase transaction by a purchasing entity, validating the product review was submitted by the purchasing entity by referencing the product purchase transaction in a blockchain, storing the product review and product purchase transaction, creating a link to the product review, and transmitting the link to a product site where the product can be purchased.

Abstract: Operating conditions of a blockchain configuration may be dynamic and change automatically under certain circumstances. One example method of operation may include receiving a blockchain transaction sent from a first blockchain to a second blockchain, identifying an inter-ledger contract between the first blockchain and the second blockchain, receiving an inter-ledger message at the second blockchain from the first blockchain, and determining whether to log the blockchain transaction in the first blockchain or the second blockchain based on the inter-ledger message.

Abstract: Utilizing blockchain in a gaming environment comprises one or more of receiving one or more contracts related to a game stored in a blockchain, initiating a game session of the game based on the one or more contracts, and receiving information and actions related to a game player in the blockchain based on the initiated game session.

Abstract: A blockchain configuration may log asset data as well as transaction data. One example method of operation may include logging a transaction on a blockchain, linking assets to the transaction, recording a current asset state on the blockchain of the assets responsive to linking the assets to the transaction, determining parties to the blockchain transaction have requirement criteria associated with the current asset state, and monitoring the current asset state to identify whether a lapse in the requirement criteria has occurred.

Abstract: The system, method, and computer program product described herein provides a built-in feedback mechanism for a blockchain to sanction validator nodes that consistently “vote” in a manner that does not match the ultimate consensus. The method includes receiving a vote on whether to add a transaction to the blockchain, comparing the vote to a consensus decision on whether to add the transaction to the blockchain, determining based on the comparison that the vote does not match the consensus decision, in response to determining that the vote does not match the consensus decision, incrementing a value associated with the validator node in a feedback registry, determining that the value associated with the validator node is above a predetermined threshold value, and in response to determining that the value associated with the validator node is above the predetermined threshold, proposing a sanction of the validator node to the plurality of validator nodes.

Abstract: The present disclosure relates to the enforcement of a smart contract execution hierarchy on a blockchain. A method includes receiving a submission of a first smart contract to be appended to a blockchain, comparing a priority value of the first smart contract to a priority value of a second smart contract previously appended to the blockchain, determining based on the comparison that the first smart contract has a lower priority than the second smart contract, comparing the terms of the first smart contract to the terms of the second smart contract, determining at least one of an overlap and a conflict between the terms of the first smart contract and the terms of the second smart contract, resolving any terms of the first smart contract that are determined to overlap or conflict with the terms of the second smart contract, and appending the resolved first smart contract to the blockchain.

Abstract: A system, method, and computer program product provides contextual contracts across various enterprise blockchain applications. In an aspect of the present disclosure, a method is disclosed including receiving a contextual contract for addition to a blockchain. The contextual contract includes at least one state dependent term. The method further includes appending a block to the blockchain based on the received contextual contract and in response to appending the block, activating a ledger sensor for the contextual contract. The ledger sensor is configured to monitor at least one of the blockchain and at least one other blockchain for transactions that correspond to the at least one term. The method further includes receiving from the ledger sensor data about transactions that corresponding to the at least one term and finalizing the contextual contract by appending a block to the blockchain based on the received data and the contextual contract.

Abstract: An arbitrary customer instance is transferred from a customer environment to a target managed-infrastructure-as-a-service cloud environment as a transferred image. An image adjustment plan, capturing at least one adjustment required to render the transferred image compliant with standards of the target managed-infrastructure-as-a-service cloud environment, is formulated. The image adjustment plan is executed to adjust the transferred image to obtain an adjusted image compliant with standards of the target managed-infrastructure-as-a-service cloud environment. The adjusted image is on-boarded into the managed-infrastructure-as-a-service cloud environment as a standard image thereof.

Abstract: An arbitrary customer instance is transferred from a customer environment to a target managed-infrastructure-as-a-service cloud environment as a transferred image. An image adjustment plan, capturing at least one adjustment required to render the transferred image compliant with standards of the target managed-infrastructure-as-a-service cloud environment, is formulated. The image adjustment plan is executed to adjust the transferred image to obtain an adjusted image compliant with standards of the target managed-infrastructure-as-a-service cloud environment. The adjusted image is on-boarded into the managed-infrastructure-as-a-service cloud environment as a standard image thereof.

Abstract: During a process of migrating a source system into a standardized virtual environment, virtual machine instances of the source system executing in a hypervisor are snapshotted as virtual machine images in an operational repository of the hypervisor. The virtual machine images in the operational repository are short-term snapshots. From time to time during the migration process, long-term snapshots of the source system are created by checking given ones of the virtual machine images from the hypervisor operational repository into an image library as image objects.

Abstract: A method and system for tracking a virtual machine is provided. The method includes determining updates applied to virtual machine instances and tracking updates associated with a master image used to generate the virtual machine instances. High level semantic updates to the master image are identified by performing a breadth-first search on a version graph to identify a cut on the version graph such that each edge in the cut comprises all elements of the high level semantic updates and splitting a node that immediately follows the cut into a node V1 and a node V2. The node V1 captures changes of the high level semantic updates and the node V2 captures changes not in the high level semantic updates. The node V1 is promoted to a root. A version tree configured to track drift of each virtual machine instance with respect to the master image is maintained.

Abstract: During a process of migrating a source system into a standardized virtual environment, virtual machine instances of the source system executing in a hypervisor are snapshotted as virtual machine images in an operational repository of the hypervisor. The virtual machine images in the operational repository are short-term snapshots. From time to time during the migration process, long-term snapshots of the source system are created by checking given ones of the virtual machine images from the hypervisor operational repository into an image library as image objects.

Abstract: Methods, systems, and computer program products for software identification, dependency analysis, and manipulation of file system layers of container images are provided herein. A computer-implemented method includes extracting multiple layer files from an input image; identifying software components in each of the extracted layer files; manipulating the input image based on said identifying and user-defined parameters, wherein said manipulating comprises (i) selecting a sub-set of the layer files for retention, (ii) removing a sub-set of the layer files, and (iii) modifying one or more of the layer files selected for retention and/or inserting one or more new layer files in place of one or more of the removed layer files; and outputting a modified version of the input image that includes the sub-set of the multiple layer files selected for retention and any new layer files inserted in place of removed layer files.

Abstract: A service method and associated system is provided. The method includes generating event types for events and services associated with the events. Virtual or physical machines associated with the services are provisioned and a message associated with a first event is published. The message is routed to a queue of a second service and the second service is notified of the message. The services are enabled and a selection for a sub-set of the services is received. The selection is enabled.

Abstract: Methods and arrangements for managing a consistency group for computing sites. A plurality of computing sites contained within a consistency group are communicated with by using an aggregator, each of the plurality of computing sites comprising one or more of a virtual machine and a server. The aggregator acts as a central communication hub between the plurality of computing sites and combines data changes from the plurality of computing sites. Updates captured at each of the sites are received and the updates are batched. The updates are communicated, after the batching, to the plurality of computing sites, thereby ensuring data consistency across the plurality of sites. Other variants and embodiments are broadly contemplated herein.

Abstract: Methods and arrangements for providing assistance with troubleshooting for system updates. There is sent, to a first database, a feature log associated with an update event at a first location. The feature log is pooled in the first database with feature logs associated with update events at other locations. A signature is created of at least one update from the first database, and the signature is added to a signature database. The signature database is employed to identify one or more deviations, when the at least one update fails in at least one location. The one or more deviations are ranked with respect to at least one other deviation. Other variants and embodiments are broadly contemplated herein.

Abstract: Methods and arrangements for managing a consistency group for computing sites. A plurality of computing sites are communicated with, each of the sites comprising one or more of (i) and (ii): (i) at least one virtual machine; and (ii) at least one server. Updates captured at each of the sites are received, and the captured updates are batched. The batched updates are communicated to the plurality of sites, thereby ensuring data consistency across the plurality of sites. Other variants and embodiments are broadly contemplated herein.

Abstract: Techniques, systems, and articles of manufacture for automatically propagating updates in a data center. A method includes dividing multiple virtual machines in a data center into one or more equivalence classes, wherein each equivalence class is based on a signature corresponding to an offline, online and/or manual update, automatically creating an offline and/or online virtual machine manifest for a first virtual machine of the multiple virtual machines based on one or more file system changes during the offline, online and/or manual update for the first virtual machine, wherein said manifest is applicable to each additional virtual machine in the same equivalence class as the first virtual machine, and applying the offline and/or online virtual machine manifest for the first virtual machine to the remaining multiple virtual machines in the same equivalence class to automatically update the remaining multiple virtual machines in the same equivalence class.