hostfactory 0.0.3.post2

Symphony k8s deployment tools

Morgan Stanley makes this available to you under the Apache License, Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. See the NOTICE file distributed with this work for additional information regarding copyright ownership. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Symphony on K8s Hostfactory Provider

This provider extends IBM Symphony hostfactory custom provider to provide the necessary functionality for hostfactory to provision Symphony compute nodes on Kubernetes.

Overview

IBM Symphony hostfactory is a service that runs as part of IBM Symphony Orchestrator. The hosfactory service manages compute host bursting to public cloud. Hostfactory provides custom provider extension to allow usecase specific implementation of the host provider. Hostfactory overview.

Prerequisites

The plugin should be installed as part of an IBM Symphony deployment with the necessary credentials/capabilities to deploy pods on a Kubernetes cluster.

Provider installation

The provider scripts k8s-hf should be part of the ${HF_CONFDIR} under Symphony and hostProviderPlugins.json should add the plugin name:

{
    "version": 2,
    "providerplugins": [
        {
            "name": "k8s-hf",
            "enabled": 1,
            "scriptPath": "${HF_CONFDIR}/providers/k8s-hf/scripts/"
        }
    ]
}

as for the script files and hostProviders.json they should be copied under ${HF_CONFDIR} in the following tree structure

├── providers
│   ├── hostProviders.json
│   └── k8s-hf
│       └── scripts
│           ├── getAvailableTemplates.sh
│           ├── getRequestStatus.sh
│           ├── getReturnRequests.sh
│           ├── requestMachines.sh
│           └── requestReturnMachines.sh

built python binaries should be part of $PATH in the runtime environment.

Provider mechanism

The Symphony on K8s provider implements multiple processes to allow the interface to invoke Kubernetes API for Pod/Host management asynchronously. The process that should be running as part of the runtime environment:

• hostfactory watch request-machines Watches hostfactory provider requests and creates the pods.
• hostfactory watch request-return-machines Watches hostfactory provider return requests and deletes the pods.
• hostfactory watch pods Watches the kubernetes event loop for new/modified/deleted pods and captures them on disk.

Installation

Today, the only supported python version is 3.12.

pip install hostfactory

Pod spec

An example pod spec can be found at example pod spec

Running the provider

Supposing you have a valid kubernetes config, the following commands will schedule a pod.

mkdir /tmp/hostfactory
hostfactory-admin request-machines | hostfactory --configdir config_example/ request-machines
hostfactory watch request-machines

Testing

Common Requirements

A python venv containing the necessary dependencies can be created using the following command:

./create_dev_venv.sh
source .venv/bin/activate

Unit tests

Running the tests

The unit tests are written using pytest and can be run using the following command:

pytest src/hostfactory/tests/unit

Integration tests

Requirements

In order to test the provider, a Kubernetes cluster should be available with a valid kube config in any of the standard directories or environment variables.

The workdir which default to /var/tmp/hostfactory also needs to be writable.

Running the tests

The unit tests are written using pytest and can be run using the following command:

pytest src/hostfactory/tests/regression

Feedback

Please contact [e-mail] for any questions.