5f3f13cc0a
Replace socket-based liveness checks with scripts The current TCP socket-based liveness/readiness check for Ceph doesn't accurately reflect when daemons are live, doesn't handle multiple OSDs on a host, and doesn't work when hostNetworking is in use and the Ceph network is different from the one associated with the hostname. This change adds new scripts for checking Ceph monitor and OSD liveness/readiness that query the Ceph Unix domain sockets to get daemon status and exits 0 iff all sockets report that their daemons are in an "active" state. This isn't perfect: we don't know how many daemons SHOULD be active, so if only a subset is live and the others have no sockets (yet?), we'll still claim the pod is ready. The scripts also don't distinguish between liveness and readiness for OSDs. Change-Id: I5d370b4bc4025fece2e640355c3a29167afca871
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-5 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad.
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, and the gate scripts, use are supported on any fresh Ubuntu, CentOS or Fedora machine.
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 Issues and Bugs.
To evaluate a multinode installation, follow the Bare Metal install guide.