Closed timdengyun closed 1 year ago
In the beginging, the deployed cluster1 datastore naming convention is fixed as:
# 'datastore': {'datastore': 'datastore-13', # 'datastore (1)': 'datastore-17', # 'vsanDatastore': 'datastore-49' }}}
However, the datastore naming is changed with dynamic naming format that is changed according to ESXi host ip name like:
# 'datastore': {'datastore-10.221.121.47': 'datastore-32', # 'datastore-10.221.121.48': 'datastore-36', # 'vsanDatastore': 'datastore-49'},}}
This patch is to support deployed cluster1 datastore naming convention change to rebuild datastore name in mapping from dynamic datastore name input and output a fixed datastore name mapping, one for nsx_datastore and one for edge_datastore.
Signed-off-by: Yun Dengdengyu@vmware.com
In the beginging, the deployed cluster1 datastore naming convention is fixed as:
{'concourse_dc1': {'cluster': {'cluster1': 'domain-c9'},
However, the datastore naming is changed with dynamic naming format that is changed according to ESXi host ip name like:
{'concourse_dc1': {'cluster': {'cluster1': 'domain-c27'},
This patch is to support deployed cluster1 datastore naming convention change to rebuild datastore name in mapping from dynamic datastore name input and output a fixed datastore name mapping, one for nsx_datastore and one for edge_datastore.
Signed-off-by: Yun Dengdengyu@vmware.com