International Business Machines Corporation

Xiang Zhen Gan

Hai Hui Wang

Peng Li

Xun Pan

Guang Ya Liu

Guangya Liu

Xin Peng Liu

Shan Gao

Yuanyuan He

Ying Mo

An embodiment maps identifying information of a remote registry into a database within a local inventory at a local registry hub. An embodiment selects at least one remote registry from an index maintained in the local inventory in accordance with a policy received at a scheduler from an external client of the local registry hub. An embodiment selects a locally stored image in accordance with a policy received from an external client of the local registry hub. An embodiment uploads replicas of the selected image via one or more registry agents, each registry agent transmitting to its corresponding remote registry, transmitting constituent layers of the replica across multiple remote registries simultaneously such that a subset of the layers constituting the image are uploaded to each remote registry. An embodiment stores metadata for the uploaded image in a cache within a local metadata store.

Multiple distributed private registry management

Provisioning an orchestration platform is provided. A pre-application programming interface (API) server hook is used to preprocess a request to generate a custom resource in the orchestration platform. The pre-API server hook generates a custom resource definition corresponding to the custom resource and generates the custom resource based on the custom resource definition. A custom resource definition generation event is monitored for, using a custom resource definition (CRD) meta-controller, to manage a custom resource definition controller corresponding to the custom resource definition. The CRD meta-controller retrieves the custom resource definition controller from a CRD controller configuration repository to deploy the custom resource definition controller on a worker node in the orchestration platform. Data is distributed, using a data partition proxy, to the custom resource definition controller running the custom resource on the worker node to ensure that no overlapping of data processing tasks exists in the orchestration platform.

Event-driven provisioning of an elastic orchestration platform

Methods, computer program products, and/or systems are provided that perform the following operations: identifying a first workload being processed by a first plurality of sites in a cluster; identifying, from the first plurality of sites: (i) a first site as a primary site for the first workload, and (ii) one or more secondary sites for the first workload; identifying a communication link issue between the first site and at least one of the one or more secondary sites; splitting the cluster into sub-clusters based, at least in part, on the communication link issue, wherein the first site is included in a first sub-cluster of the sub-clusters and the at least one of the one or more secondary sites is included in a sub-cluster of the sub-clusters that is different from the first sub-cluster; and instructing the first sub-cluster to locally process the first workload.

Auto-split and auto-merge clusters

A system may include a memory and a processor in communication with the memory. The processor may be configured to perform operations. The operations may include registering a custom resource definition for a tenant with a host and scaling a controller for the customer resource definition. The operations may include generating a replication using the customer resource definition, injecting information into the replication, and syncing a status of the custom resource definition between the host and the tenant.

Extend controller for multi-tenancy

A computer-implemented method, an apparatus, and a computer program product for edge node autonomy. For a first edge node of a plurality of edge nodes in a federation in a distributed computing framework, one or more processors receive a request to be sent to a central node in the distributed computing framework. The one or more processors determine whether the federation is connected to the central node. In response to determining that the federation is not connected to the central node, the one or more processors determine whether a controller capable of processing the request is available in the federation. In response to determining that the controller capable of processing the request is available in the federation, the one or more processors notify the controller to process the request.

Edge node autonomy

A processor may receive a composable deployer comma-separated values (CSV) file. The processor may parse the composable deployer CSV file. The processor may determine if there is a composable deployer foundation template. The processor may install a resource. The resource to install may be associated with the composable deployer foundation template.

Growing community of inventors

Xian, China

Xiang Zhen Gan