Associate existing subnet GUIDs when configuring director networks

[RageZBla]

Ref #558

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[RageZBla]

Let me know if the comparison should be made on more fields. In theory it does not really matter since the other field would be updated.

[wyike]

In my case, when the az configuration is:

az-configuration:
  - name: AZ1
    iaas_configuration_name: default
    clusters:
      - cluster: os-compute-cluster-1
        drs_rule: MUST
        guid: 5a132e367e2a82348a21
        host_group: null
        resource_pool: PKS
      - cluster: os-compute-cluster-1
        drs_rule: MUST
        guid: d59e16f5431b8beeb615
        host_group: null
        resource_pool: PKSWorkerPool
    guid: 54e4cdfc17edc55ae5d

and will meet error when staging back the director configuration:

cc
{"errors":{"base":["Cannot delete the cluster 'os-compute-cluster-1' in the availability zone 'AZ1' of a deployed product","Cannot have multiple clusters with the same guid. Guid: 5a132e367e2a82348a21"]}}
0

This change doesn't work to fix the problem. But I can use this change to simple fix my problem: https://gitlab.eng.vmware.com/PKS/gear2/-/commit/28838ed57a3edf699ea1e619c0bc45d363df00a2, not sure if you guys can open it.

[xtremerui]

@dtimm @jaristiz FYI ^^

[rhall-pivotal]

Closing due to age. If this is still needed, please resubmit.
-TAS Operability