This release is a pre-release and may not be stable for production use.
Kayobe
Kayobe enables deployment of containerised OpenStack to bare metal.
Containers offer a compelling solution for isolating OpenStack services, but running the control plane on an orchestrator such as Kubernetes or Docker Swarm adds significant complexity and operational overheads.
The hosts in an OpenStack control plane must somehow be provisioned, but deploying a secondary OpenStack cloud to do this seems like overkill.
Kayobe stands on the shoulders of giants:
OpenStack bifrost discovers and provisions the cloud
OpenStack kolla builds container images for OpenStack services
OpenStack kolla-ansible delivers painless deployment and upgrade of containerised OpenStack services
To this solid base, kayobe adds:
Configuration of cloud host OS & flexible networking
Management of physical network devices
A friendly openstack-like CLI
All this and more, automated from top to bottom using Ansible.
Features
Heavily automated using Ansible
kayobe Command Line Interface (CLI) for cloud operators
Deployment of a seed VM used to manage the OpenStack control plane
Configuration of physical network infrastructure
Discovery, introspection and provisioning of control plane hardware using OpenStack bifrost
Deployment of an OpenStack control plane using OpenStack kolla-ansible
Discovery, introspection and provisioning of bare metal compute hosts using OpenStack ironic and ironic inspector
Virtualised compute using OpenStack nova
Containerised workloads on bare metal using OpenStack magnum
Control plane monitoring using Prometheus and Grafana.
Log aggregation using OpenSearch and OpenSearch Dashboards.
Documentation
Release Notes
Bugs
Community
OFTC’s IRC channel: #openstack-kolla
License
Kayobe is distributed under the Apache 2.0 License.
1 maintainer
Metadata
1 maintainer
Release files for kayobe 21.0.0.0rc1
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 | Actions |
|---|---|---|---|---|
| kayobe-21.0.0.0rc1.tar.gz | 677.9 kB | Without provenance | Details for kayobe-21.0.0.0rc1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kayobe-21.0.0.0rc1-py3-none-any.whl | Python 3 | none | any | Details for kayobe-21.0.0.0rc1-py3-none-any.whl |
Total release size: 1.4 MB
Release files / kayobe-21.0.0.0rc1.tar.gz
| Download URL | kayobe-21.0.0.0rc1.tar.gz |
|---|---|
| Size | 677.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dc6182a79f1b2fe5ddb581e9a9398bbe9340989bba13980c8a0f8690814b4c2
|
|
BLAKE2b-256 checksum How to use checksums |
98919f734924870bc67f577d148d4ce007aae417090b3f9281f52e16465855b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / kayobe-21.0.0.0rc1-py3-none-any.whl
| Download URL | kayobe-21.0.0.0rc1-py3-none-any.whl |
|---|---|
| Size | 771.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d2b23e129b6d678317e9a601438c9d060cbf683e0c9dc5c417b5e4e421cf0941
|
|
BLAKE2b-256 checksum How to use checksums |
5aa5c4da56ed3e917d6369cf8c09123d4ec2d720c01ec34d3efa246eee16af2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for kayobe 21.0.0.0rc1
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.
