baf5356a4f
Currently there is fake rpc call "pod_health_probe_method_ignore_errors" that is passed to the service, just to find out if it is responding. Because such method does not exist, it is needed to catch and handle the exception that is inevitably thrown by the service. While this is technically working correctly, the exceptions pollute the log files and make it harder for user to see possible real errors. This is how the error looks like: ERROR oslo_messaging.rpc.server [-] Exception during message handling: oslo_messaging.rpc.dispatcher.UnsupportedVersion: Endpoint does not support RPC version 1.0. Attempted method: pod_health_probe_method_ignore_errors ERROR oslo_messaging.rpc.server Traceback (most recent call last): ERROR oslo_messaging.rpc.server File "/var/lib/openstack/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) ERROR oslo_messaging.rpc.server File "/var/lib/openstack/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 276, in dispatch ERROR oslo_messaging.rpc.server raise UnsupportedVersion(version, method=method) ERROR oslo_messaging.rpc.server oslo_messaging.rpc.dispatcher.UnsupportedVersion: Endpoint does not support RPC version 1.0. Attempted method: pod_health_probe_method_ignore_errors This situation is new since https://review.openstack.org/#/c/639711/ which (correctly) increased the default level of logging. Before 639711 error messages from oslo (both real and ones that could be ignored) were not present in nova logs at all. Fortunatelly, nova's BaseAPI class provides 'ping' method that is can be used for this basic purpose by all nova components. Change-Id: I0062e74bed399206becb8d9e00f9ec805da864a3 |
||
|---|---|---|
| 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 | ||
| 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.