Bharat Kunwar 2864fc57d4 Use cluster name for fixed_network instead of private ... At present, when a fixed_network is not specified, it is given the name "private" by default. When multiple clusters are created, we end up in a situation where we end up with multiple networks all with the same name. This PS intends to make it easier to see where the resources belong to by using the cluster name. Story: 2007460 Task: 39139 Change-Id: I7f8028b716f9a9eced17d85ca2e46e2b1e34875f		2020-03-24 06:38:38 +00:00
..
common	Merge "calico: Add node/status in ClusterRole"	2020-03-16 21:34:16 +00:00
heat	Use cluster name for fixed_network instead of private	2020-03-24 06:38:38 +00:00
k8s_coreos_v1	Update default calico_ipv4pool	2020-03-16 22:33:10 +00:00
k8s_fedora_atomic_v1	Use cluster name for fixed_network instead of private	2020-03-24 06:38:38 +00:00
k8s_fedora_coreos_v1	Use cluster name for fixed_network instead of private	2020-03-24 06:38:38 +00:00
k8s_fedora_ironic_v1	ng-12: Label nodegroup nodes	2019-10-16 11:53:44 +00:00
mesos_ubuntu_v1	Docker volume size from nodegroups	2019-10-23 11:08:27 +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