da508727b6
Health_probe for neutron pods accomplish both liveness and readiness probe. Neutron DHCP/L3/OVS agents: Sends an RPC call with a non-existence method to agent’s queue. Assumes no other agent subscribed to tunnel-update queue other than OVS. Probe is success if agent returns with NoSuchMethod error. Neutron Metadata agent: Sends a message to Unix Domain Socket opened by Metadata agent. Probe is success if agent returns with HTTP status 404. In both the cases, if agent is not reachable or fails to respond in time, returns failure to probe. Readiness probe for Neutron L3/DHCP/Metadata/SRIOV agents Following are the operations executed on the pod as part of readiness probe on the neutron agents: - Check if the agent process is up and running. - Retrieve the sockets associated with the process from the /proc fs. - Check the status of tcp sockets related to Rabbitmq communication. - Check the reachability of the rabbitmq message bus from the agent. - For SRIOV Agent, check if VFs are configured properly for the configured NICs in sriov_agent.ini conf file Change-Id: Ib99ceaabbad1d1e0faf34cc74314da9aa688fa0a |
||
---|---|---|
barbican | ||
ceilometer | ||
cinder | ||
congress | ||
doc | ||
glance | ||
heat | ||
horizon | ||
ironic | ||
keystone | ||
magnum | ||
mistral | ||
neutron | ||
nova | ||
rally | ||
senlin | ||
tempest | ||
tests | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
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-5 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.