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
..
__init__.py	Refactor driver interface (pt 1)	2016-12-01 09:23:46 -06:00
driver.py	Fix join of status_reason	2020-03-18 10:39:51 +00:00
k8s_coreos_template_def.py	Add calico_ipv4pool_ipip label	2020-01-09 14:22:23 +01:00
k8s_fedora_template_def.py	Merge "Add cinder_csi_enabled label"	2020-03-16 06:43:47 +00:00
k8s_template_def.py	Use cluster name for fixed_network instead of private	2020-03-24 06:38:38 +00:00
swarm_fedora_template_def.py	Docker volume size from nodegroups	2019-10-23 11:08:27 +00:00
swarm_mode_template_def.py	Docker volume size from nodegroups	2019-10-23 11:08:27 +00:00
template_def.py	Docker volume size from nodegroups	2019-10-23 11:08:27 +00:00