
This PS adds octavia chart and its deployment scripts. Blueprint name : openstack-helm-octavia - Deployments : api, worker, housekeeping - Daemonset : health-manager - health-manager daemonset creates o-hm device on each controller node. - This is for multi node deployment. - 180-create-resource-for-octavia.sh : Create openstack resources (network, sec groups, flavor, keypair, image for development) - 190-create-octavia-certs.sh : Create certificates to use Octavia (the certs is passed into pod using secret and volume for development) - 200-octavia.sh : Deploy Octavia chart Note: This chart doesn't include amphora image itself and its build. Change-Id: I0bb7dfc7c15d77287c05a8542347e19fc269aba4 Signed-off-by: hagun.kim <hagun.kim@samsung.com>
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.