magnum/magnum/drivers
Feilong Wang 15a4ea14e1 Support TimeoutStartSec for k8s systemd services
Now Magnum is using podman and systemd to manage the k8s components.
In cases where the nodes pull images from docker.io or another
mirror registry with high latency, some of the components may take long
time to start, which is causing timeout when bootstraping k8s
cluster for fedora atomic/coreos drivers. This patch fixes it by
adding TimeoutStartSec for the systemd services.

Task: 37251
Story: 2006459

Change-Id: I709bac620e4ceec1858672076eb0aef997704b62
2019-11-13 22:19:51 +13:00
..
common Support TimeoutStartSec for k8s systemd services 2019-11-13 22:19:51 +13:00
heat Merge "bug: Cluster should be creatable w/o fixed subnet" 2019-10-19 08:25:20 +00:00
k8s_coreos_v1 ng-12: Label nodegroup nodes 2019-10-16 11:53:44 +00:00
k8s_fedora_atomic_v1 ng-12: Label nodegroup nodes 2019-10-16 11:53:44 +00:00
k8s_fedora_coreos_v1 ng-12: Label nodegroup nodes 2019-10-16 11:53:44 +00:00
k8s_fedora_ironic_v1 ng-12: Label nodegroup nodes 2019-10-16 11:53:44 +00:00
mesos_ubuntu_v1 ng-10: Fix cluster template conditions 2019-10-16 11:53:44 +00:00
swarm_fedora_atomic_v1 ng-10: Fix cluster template conditions 2019-10-16 11:53:44 +00:00
swarm_fedora_atomic_v2 ng-10: Fix cluster template conditions 2019-10-16 11:53:44 +00:00
__init__.py Bay driver implementation 2016-07-05 22:30:31 +02:00