8c93743041
L2 Gateway (L2GW) is an API framework that offers bridging 2+ networks together to make them look as a single broadcast domain. A typical use case is bridging the virtual with the physical networks. Change-Id: I95ff59ce024747f7af40c6bef0661bb3743b0af1 |
||
---|---|---|
aodh | ||
barbican | ||
ceilometer | ||
cinder | ||
congress | ||
doc | ||
glance | ||
heat | ||
horizon | ||
ironic | ||
keystone | ||
magnum | ||
mistral | ||
neutron | ||
nova | ||
panko | ||
rally | ||
releasenotes/notes | ||
senlin | ||
tempest | ||
tests | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
Makefile | ||
README.rst | ||
setup.cfg | ||
setup.py | ||
tox.ini |
OpenStack-Helm
Mission
The goal of OpenStack-Helm is to provide a collection of Helm charts that simply, resiliently, and flexibly deploy OpenStack and related services on Kubernetes.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Storyboard
Bugs and enhancements are tracked via OpenStack-Helm's Storyboard.
Installation and Development
Please review our documentation. For quick installation, evaluation, and convenience, we have a kubeadm based all-in-one solution that runs in a Docker container. The Kubeadm-AIO set up can be found here.
This project is under active development. We encourage anyone interested in OpenStack-Helm to review our Installation documentation. Feel free to ask questions or check out our current Storyboard backlog.
To evaluate a multinode installation, follow the Bare Metal install guide.
Repository
Developers wishing to work on the OpenStack-Helm project should always base their work on the latest code, available from the OpenStack-Helm git repository.