llama-stack-provider-kft
Llama Stack Remote Post Training Provider for Distributed InstructLab Training using the Kubeflow Trainer
Utilities
As a part of this package, the ilab-kft command line interface is available to get a cluster properly set up for distributed training.
NOTE: the oc cli is a pre-requisite to using this tool.
How to
Upload your SDG data to the cluster
Currently ilab-kft allows you to upload a local directory of data to your cluster mounted in a PVC.
example: python3.11 ilab-kft.py data-upload --data-path ~/.local/share/instructlab/datasets/ --pvc-name data --namespace default
Upload your model
Using the same data-upload command, you can also upload models:
example: python3.11 ilab-kft.py data-upload --data-path ~/.cache/instructlab/models/granite-7b-lab/ --pvc-name model --namespace default
Run training
Using llama-stack and the client SDK, one can spin up a llama stack server and run post-training using this provider
llama stack run run.yaml --image-type venv
python3.10 train.py
train.py utilizes the llama-stack-client python SDK to initialize training arguments, and pass the required arguments to supervised_fine_tune in order to kick off the provider implementation maintained externally in this repository.
Run llama-stack-provider-kft in cluster
1. Deploy Kustomize manifests
Apply the kustomize manifests under base directory.
kubectl apply -k manifests/base/
2. (Optional) Access the service locally
If you want to run a client such as the train.py script locally, you can port-forward the service to your localhost.
kubectl port-forward svc/lls-provider-kft 8321:80
Metadata
Release files for llama-stack-provider-kft 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| llama_stack_provider_kft-0.1.0.tar.gz | 11.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| llama_stack_provider_kft-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.4 kB
Release files / llama_stack_provider_kft-0.1.0.tar.gz
| Download URL | llama_stack_provider_kft-0.1.0.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b443b1b3cb37d99b125ac73a4dd8bc46e802603370c6f734ac175852375b830b
|
|
BLAKE2b-256 checksum How to use checksums |
56e9c1dca00dee4638ebcb43d57146dec3e3d08f65ba2323ae399f476b845582
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.5
|
Release files / llama_stack_provider_kft-0.1.0-py3-none-any.whl
| Download URL | llama_stack_provider_kft-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b567b1b676fe370ea55fcb91cd32e64c8bc54a610160ed3dbcaf09e9e3cf941
|
|
BLAKE2b-256 checksum How to use checksums |
c718c41b7e1568c45bcda2ee183ffe4f1f5de88012710687f5a6dc1d920f1b40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.6.5
|
Security for llama-stack-provider-kft 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.