Oracle International Corporation

Jacob Lindholm

Yamini Kalyandurga Balasubramanyam

Rajiv Mordani

Nazrul Islam

Abhijit Kumar

Christopher S Kasso

Steven Liu

Josh Dorr

Andrew James Pryde

Joshua Aaron Horwitz

Aseem Bajaj

David Sang-Chul Nahm

Joshua Lee Dorr

Josh Aaron Horwitz

Techniques are described herein for authenticating a pod. A method can include a manager instance receiving a first request for a first token to access a computing resource. The manager instance can determine an identity of the service account and generate a second request for the first token based at least in part on the authentication. The manager instance can transmit the second request to a token issuance service of the computing system. The token issuance service can generate a third request for the first token, the third request comprising the identity of the service account and a token issuance service signature. The token issuance service can transmit the third request to an identity service of the computing system. The identity service can generate the first token based at least in part on determining whether to generate the first token.

Workload identity resource principle

In accordance with an embodiment, described herein is a system and method for supporting patching in a multi-tenant application server environment. The system can associate one or more partitions with a tenant, for use by that tenant, wherein a partition is a runtime and administrative subdivision or slice of a domain. A patching process can take advantage of high-availability features provided by an application server clustering environment, to apply patches in a controlled, rolling restart, which maintains a domain's ability to operate without interruption, or with zero downtime. The process can be used to automate complex or long running tasks, including preserving an unpatched or prior version of an application server, application, or other software component for possible rollback, or providing automatic reversion in the event of an unrecoverable error.

System and method for supporting patching in a multitenant application server environment

Systems, devices, and methods discussed herein are directed to modifying aspects of a compute instance. A user may request a change to the compute instance. The system may derive a state object indicating a future state of the compute instance were the change to be applied. A hash of a subset of the state object's attributes may be computed and provided to the requesting computing component. The system may subsequently proceed with applying the change. A current state object indicating a current state of the compute instance may be derived based on applying the change. An additional hash of the subset of the current state object's attributes may be computed and provided to the requesting computing component. The two hashes may be configured to enable the requesting computing component to verify the change to the compute instance has been implemented.

Techniques for modifying a compute instance

Techniques for migrating worker nodes within clusters to a new manager instance. One technique includes receiving a request to migrate or update a configuration of a cluster within a container system, where the migration or update includes switching from a first communication pathway to a second communication pathway between worker nodes and a manager instance; creating a component and associated IP address for the second communication pathway; communicating a pod specification that includes the IP address for the second communication pathway to the manager instance, where the pod specification will cause a container tool to update each of the worker nodes with the IP address for the second communication pathway; receiving a notification that all worker nodes have been updated with the IP address; and removing a component and associated IP address for the first communication pathway from the cluster.

Techniques for migrating worker nodes to a new manager instance

In accordance with an embodiment, described herein is a system and method for providing support for custom hooks during patching in an application server, enterprise, cloud computing, or other computing environment. A patch orchestration engine generates a patching workflow including a series of steps that apply patches to update one or more targeted nodes in a controlled manner with minimal downtime. Custom hooks provide a flexible mechanism that enables modifying phases of the patching workflow that can be associated with extension points. When an extension, for example an additional Java software code, script or other command, is specified to be run at a particular extension point associated with a particular phase of a patching workflow, the patch orchestration engine causes the extension to be inserted into the patching workflow, for execution during patching of the targeted nodes, to modify that phase of the patching workflow.

System and method for supporting custom hooks during patching in an application server environment

In accordance with an embodiment, described herein are a system and method for partition-scoped patching in an application server environment. A computer environment includes an application server, for example a multitenant application server, that supports the use of one or more partitions, wherein each partition provides an administrative and runtime subdivision of a domain. During a partition-scoped rollout of a patch or update, to a resource group or application within a plurality of servers or clusters of servers, the resource group or application can be updated within a targeted partition, using a patch orchestrator and partition lifecycle runtime interface, without affecting the operation of other partitions at those servers or clusters of servers. One or more session handling flags can be used, to enable sessions and/or requests that are associated with the targeted partition, to be handled by a traffic director, during the patching process.

Growing community of inventors

Londonderry, NH, United States of America

Jacob Lindholm