Abstract: Systems and methods are provided for performing, at a server, a stack trace of an application at a predetermined interval to generate a plurality of stack traces, where each stack trace of the plurality of stack traces is from a different point in time based on the predetermined interval. The stack trace is performed when the application is operating normally and when the application has had a failure. The plurality of stack traces stored are indexed by timestamp. The server may determine a state of the application based on at least one of the plurality of stack traces. The server may condense data for at least one of the plurality of stack traces that are indexed using predetermined failure scenarios for the application. The server may generate a report based on the condensed data and the state of the application, and may transmit the report for display.

Abstract: A method that includes identifying a declarative deployment file defining a deployment configuration for multiple logical single-tenant system stacks supported by a compute container system, where the deployment configuration includes a set of deployment criteria and a failure threshold. The method may further include determining, based on the set of deployment criteria, a set of deployment groups for implementing one or more system updates, where the set of deployment groups includes a first deployment group and the first deployment group includes a first set of logical single-tenant system stacks from the multiple logical single-tenant system stacks supported by the compute container system. The method may further include implementing the one or more system updates for the set of deployment groups based on the failure threshold.

Abstract: A compute container system may support logical partitions for various single tenant systems. These logical partitions may be referred to as logical single-tenant system stacks. An operator or release manager for a logical partition may identify a declarative deployment file defining a deployment configuration for one or more of a plurality of logical single-tenant system stacks. The operator may determine a deployment schedule for implementing one or more system updates for the plurality of logical single-tenant system stacks based on the declarative deployment file and implement the system updates based on the determined deployment schedule.

Abstract: A method that includes identifying a declarative deployment file defining a deployment configuration for multiple logical single-tenant system stacks supported by a compute container system, where the deployment configuration includes a set of deployment criteria and a failure threshold. The method may further include determining, based on the set of deployment criteria, a set of deployment groups for implementing one or more system updates, where the set of deployment groups includes a first deployment group and the first deployment group includes a first set of logical single-tenant system stacks from the multiple logical single-tenant system stacks supported by the compute container system. The method may further include implementing the one or more system updates for the set of deployment groups based on the failure threshold.

Abstract: A compute container system may support logical partitions for various single tenant systems. These logical partitions may be referred to as logical single-tenant system stacks. An operator or release manager for a logical partition may identify a declarative deployment file defining a deployment configuration for one or more of a plurality of logical single-tenant system stacks. The operator may determine a deployment schedule for implementing one or more system updates for the plurality of logical single-tenant system stacks based on the declarative deployment file and implement the system updates based on the determined deployment schedule.