Jean-Philippe Evrard ed200cb3b0 Wait for pods for openstack-support scenario
The wait for pods is not consistently used in the
openstack-support scenario.

This is a problem, as some helm charts deploys are
basically masking issues that can arise.

This should fix it.

Change-Id: Ib3e8f16bea701bf20375d4deec7c7869e7bf85c2
2019-05-28 07:51:34 +00:00
2019-04-21 15:46:16 +00:00
2019-05-21 17:15:48 -05:00
2019-05-23 23:06:11 +00:00
2019-05-24 06:31:09 -05:00
2019-05-14 17:04:52 -05:00
2019-04-20 20:50:59 +00:00
2019-04-20 20:50:59 +00:00
2019-05-17 08:17:32 +00:00
2019-05-17 08:17:32 +00:00
2019-05-27 17:05:26 +00:00
2019-05-17 08:17:32 +00:00
2019-05-17 08:17:32 +00:00
2019-04-20 20:50:59 +00:00
2019-05-14 17:04:52 -05:00
2019-05-17 08:17:32 +00:00
2019-05-17 08:17:32 +00:00
2019-05-17 08:17:32 +00:00
2019-05-14 17:04:52 -05:00
2019-05-10 01:17:21 +00:00
2019-04-19 19:34:11 +00:00
2019-02-27 15:02:06 +08:00
2018-05-15 13:04:28 -05:00
2018-10-05 16:19:35 +00:00

Openstack-Helm-Infra

Mission

The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.

For more information, please refer to the OpenStack-Helm repository.

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

Launchpad

Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.

Description
Helm charts for deploying OpenStack on Kubernetes
Readme 127 MiB
Languages
Smarty 82.1%
Shell 16%
Python 1.4%
Jinja 0.3%
Makefile 0.2%