Mark Burnett 0982a823e1 RabbitMQ: use DNS for cluster discovery, not etcd
Implements: blueprint rabbitmq-dns-discovery

Some useful things to note:

1. This uses a StatefulSet instead of a Deployment.  The reason for this
   is that when RabbitMQ uses DNS for peer discovery, the first thing it
   does when trying to join a node is attempt a reverse-dns lookup.
   This reverse lookup works when using a StatefulSet, but not a
   Deployment.
2. The RabbitMQ configuration was updated to use the new sysctl-style
   format.  It seems that the new format is required to configure the
   new autoclustering features.  Additionally, I found that this
   generate much clearer error messages than the straight erlang format.
3. I removed the `is-node-properly-clustered` test in the liveness and
   readiness probes.  This probe isn't directly supported in 3.7.0,
   and it wasn't clear that a clustering check was appropriate for each
   node.

Change-Id: Ieefbb2205bd77fbac04abcd051fb06fce62e8d97
2017-05-05 09:48:18 -05:00
2017-05-02 07:08:30 -07:00
2017-04-18 09:28:17 -05:00
2017-04-06 15:15:32 -05:00
2017-05-02 22:31:26 -05:00
2017-04-26 11:02:15 +00:00
2017-04-18 09:32:28 -05:00
2017-04-25 08:54:31 -05:00
2017-04-28 11:04:02 -05:00
2017-04-25 15:31:39 -05:00
2017-05-02 04:34:20 -05:00
2017-05-03 10:48:27 -05:00
2017-05-02 03:51:28 -05:00
2017-04-11 07:03:45 -05:00
2017-04-22 16:31:08 -05:00
2016-11-12 14:26:57 -05:00
2017-05-03 10:48:27 -05:00

Openstack-Helm

Openstack-Helm is a fully self-contained Helm-based OpenStack deployment on Kubernetes. It will provide baremetal provisioning, persistent storage, full-stack resiliency, full-stack scalability, performance monitoring and tracing, and an optional development pipeline (using Jenkins). This project, along with the tools used within are community-based and open sourced.

Mission

The goal for Openstack-Helm is to provide an incredibly customizable framework for operators and developers alike. This framework will enable end-users to deploy, maintain, and upgrade a fully functioning Openstack environment for both simple and complex environments. Administrators or developers can either deploy all or individual Openstack components along with their required dependancies. It heavily borrows concepts from Stackanetes and other complex Helm application deployments. This project is meant to be a collaborative project that brings Openstack applications into a Cloud-Native model.

Communication

  • Join us on Slack - #openstack-helm
  • Join us on IRC: #openstack-helm on freenode
  • Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-5 on freenode
  • Meeting Agenda Items: Agenda
  • Community Roadmap Items: Roadmap Docs

Open Releases

Until a 1.0.0 release, this collection is a work in progress and components will continue to be added or modified over time. Please review our Milestones, and Releases for more information.

Installation and Development

This project is under heavy development. We encourage anyone who is interested in Openstack-Helm to review our Installation documentation, complete with verification procedures. Feel free to ask questions or check out our current Issues and Bugs.

Openstack-Helm is intended to be packaged and served from your own Helm repository. However, for quick installation, evaluation, and convenience, you can use our online Helm repository. After you've configured your environment for Minikube (for hostPath) or Bare Metal.

Description
Helm charts for deploying OpenStack on Kubernetes
Readme 116 MiB
Languages
Smarty 64.2%
Shell 33.8%
Python 1.3%
Makefile 0.7%