Hewlett-packard Development Company, L.P.

Mastercard International Incorporated

Cisco Technology, Inc.

Fabio Giannetti

Shaun Patrick Henry

Ryan Eschinger

Kok-Wei Koh

John Zaiss

Alon Shlomo Bernstein

Ehud Chatow

Ingeborg Tastl

Amit Surendra Singh

Gidi Amir

Paul Wissenbach

Benjamin I Dempster

Brian Patrick Bresnahan

Alysha Naples

Bhanushree Krishnamurthy

Jose Manuel Perez

Steven Borrelli

The disclosure herein describes using a monitoring tool and a management tool from a cloud native system to monitor and manage an application executing on a legacy system. Network addresses of services running in the application on the legacy systems are discovered. Based on the discovered addresses, a probe is configured for execution on the legacy system by a monitoring tool deployed on the legacy system to obtain metrics data associated with the services running on the legacy system, the metrics data representing execution loads of the application. A management tool deployed on the cloud native system receives the obtained metrics data. The management tool compares the metrics data to one or more performance thresholds associated with the application. Based on the comparison, the management tool adjusts a quantity of instances of the application running on the cloud native system, enabling the cloud native system to share the execution loads.

Monitoring and managing services in legacy systems using cloud native monitoring and managing tools

The disclosure herein describes managing multiple clusters within a container environment using a control cluster. The control cluster includes a single deployment model that manages deployment of cluster components to a plurality of clusters at the cluster level. Changes or updates made to one cluster are automatically propagated to other clusters in the same environment, reducing system update time across clusters. The control cluster aggregates and/or stores monitoring data for the plurality of clusters creating a centralized data store for metrics data, log data and other systems data. The monitoring data and/or alerts are displayed on a unified dashboard via a user interface. The unified dashboard creates a single representation of clusters and monitor data in a single location providing system health data and unified alerts notifying a user as to issues detected across multiple clusters.

Control cluster for multi-cluster container environments

The disclosure herein describes automating runbook operations associated with an application within an application host on an application platform. A runbook definition associated with the application is accessed by a processor, wherein the runbook definition includes trigger events and runbook operations associated with the trigger events. A runbook operator is executed on the application platform based on the accessed runbook definition and a runbook sidecar container is added to the application host by the runbook operator, wherein the runbook operator is enabled to perform the runbook operations within the application host via the runbook sidecar container. Based on detecting a trigger event, a runbook operation associated with the detected trigger event is performed by the runbook operator, via the runbook sidecar container, whereby the application is maintained based on performance of the runbook operations from within the application host.

Performing runbook operations for an application based on a runbook definition

A computerized method and system for containerized application deployment is disclosed that includes: receiving an identification of a containerized application; generating parameters for the containerized application; based at least on historical performance data for a previous deployment of the containerized application, optimizing the generated parameters for the containerized application to produce optimized parameters for the containerized application; validating the optimized parameters for the containerized application; committing the optimized parameters for the containerized application to a repository; and deploying a selected number of instances of the containerized application with the optimized parameters for the containerized application. This advantageously brings operational data into deployment optimization in order to permit optimization based on actual historical performance data. Some examples provide for rollback to previously-deployed configurations, due to the commit of parameters for the containerized application in a repository that permits enhanced version tracking.

Containerized application deployment

The disclosure herein describes deploying an application cluster based on a cluster definition and service templates. A cluster definition is obtained from a repository and a cluster is created on a cluster platform based on the cluster definition. A cluster type of the cluster is identified based on the cluster definition and a service set is determined from a service map based on the identified cluster type, the service map including at least one cluster type mapped to at least one service. A service deployment template of each service of the service set is obtained and each service of the service set is deployed on the created cluster based on the obtained service deployment templates, whereby the cluster is configured for use according to the cluster type. Using service deployment templates mapped to cluster types enables efficient, flexible automated deployment of clusters with a wide variety of configurations.

Automated core services bootstrap for on-premises clusters

Temporal transaction locality in a stateless environment may be provided. First, a current message having an identifier may be received. Next, it may be determined, based on the identifier, that the current message is associated with a transaction. Then, in response to determining that the current message is associated with the transaction, the current message may be sent to a target service instance corresponding to the transaction.

Temporal transaction locality in a stateless environment

Techniques for tracking microservices and facilitating rollbacks in response to exceptions are described herein. In an embodiment, a server computer system receives, from one or more sets of microservices program instructions, digital data identifying a plurality of tasks and a sequence of the tasks, the digital data specifying a particular computational workflow for execution by a computer. During execution of the workflow by the server computer system, the system identifies a particular failure in a first task of the plurality of tasks. The system causes displaying on a client computing device, a graphical user interface comprising a plurality of nodes, the nodes corresponding to the tasks. Within the graphical user interface, the system further causes displaying, with a particular node of the plurality of nodes corresponding to the first task, a graphical indication that the first task failed. Within the graphical user interface, the system further causes displaying, with the plurality of nodes, a first rollback path comprising nodes and edges, the first rollback path comprising one or more graphical edges that graphically bypass each task of the workflow that would not be executed if a rollback is executed by the computer according to the first rollback path.

Tracking microservices using a state machine and generating digital display of rollback paths

In one embodiment, a sequence of microservice steps may be performed according to a programmed microservice workflow, while determining which executed tasks within the performed sequence of microservice steps have an individually corresponding rollback defined within the particular task. As such, a rollback path is stored corresponding to reversing the sequence of those executed tasks having an individually corresponding rollback, and, for each executed task having an individually corresponding rollback, a current status of the microservice workflow is also stored as a respective rollback status within the rollback path. In response to detecting, during the performing, an error event at a particular multiservice step of the sequence of microservice steps, the rollback path may be executed by performing the individually corresponding rollback of each task having an individually corresponding rollback along the rollback path according to the respective rollback status, until either success or failure of the rollback path.

Rollback for cloud native workflows

A system for identifying a print service provider including an input module to receive a requested print product intent and an identification module. The identification module collects production job data regarding a plurality of successfully produced print jobs and compares the collected production job data to the requested print product intent to identify matching print jobs and its associated print service provider. A reporting module reports the matching print jobs.

Print service identifier

A system and method is disclosed for imposing a print job. In one example, the system discloses a computer programmed with executable instructions which operate a set of modules, including an imposition sequence modulewhich calculates a time to process the print jobrelative to a processing operation, and an imposition module, orwhich variably imposes the print jobbased on the time to process. In one example, the method discloses how to balance a print jobworkflow relative to a processing operation, and impose the print jobbased on the workflow balancing.

System and method for efficiently imposing a print job in a print production workflow

To generate a proof of a printable item, a data structure is provided that maps a set of spot colors into a respective set of color values based on measurement data provided by a measurement device of colors printed by a printing system from the spot colors.

Providing a mapping data structure for use in generating a proof

Methods and arrangements are provided for generating, rendering and/or printing documents from a variable-data printing document template which defines multiple document versions, each document version may be selectable in response to input selection data. There is provided a way of producing of variable-data publishing (VDP) documents for Digital Publishing (DP) that rely upon complex document designs containing copy-holes which may be expressed according to a set of options, one of which being non-existence of the copy-hole.

Variable data printing

A method, system and a computer program product for generating, rendering and printing documentsfrom a variable-data printing document templatewhich defines a document defining a layout of nested document portionscomprising content which is variable in response to input data. There is provided a way of expressing and treating nested flows, thus enabling the creation of complex document designs for Variable Data Publishing material used in Digital Publishing.

Recursive flows in variable-data printing document templates

Devices and methods for using an electronic device for a print job ticket. Such an electronic device may include a network interface, a display, and an input device. The network interface may receive an assignment of the electronic device to a print job from a print service provider controller, receive workflow instructions associated with the print job from the print service provider controller, and send job status information associated with the print job to the print service provider controller. The display may display a representation of the workflow instructions and a user-selectable representation of the job status information. The input device may register a user selection of the representation of the job status information.

Growing community of inventors

Los Gatos, CA, United States of America

Fabio Giannetti