DPM should consume the port in the contract

[haboy52581]

Current implementation DPM doesn't consume this port for now and make the default value 50001 as ACA's port. We need to

1. Update DPM contract to include this field
2. DPM implementation and test update.

[haboy52581]

this one would be done when contract change in future and port manager should provide this in the contract as well

[xieus]

Hey @haboy52581 How is this issue? If it has been resolved by previous PR, can you link the PR here? Thanks.

[xieus]

This is the server port defined in NodeInfo. In the future, DPM could communicate with Node Metadata Manager to cache the node info so that DPM could find the target gRPC port from its own memory quickly.

{
  "nodeInfos": [
    {
      "node_id": "9192a4d4-ffff-4ece-b3f0-8d36e3d85002",
      "node_name": "node2",
      "local_ip": "10.213.43.161",
      "mac_address": "90:17:ac:c1:34:64",
      "veth": "eth0",
      "server_port": 50001
    }
  ]
}

[haboy52581]

DPM not supposed to talk but ok to cache data

[xieus]

Current implementation DPM doesn't consume this port for now and make the default value 50001 as ACA's port. We need to

1. Update DPM contract to include this field
2. DPM implementation and test update.

@haboy52581 In short-term, we can use existing channels by asking PM to pass down the ACA gRPC port. Do we still update the DPM contract to do that, or it is already updated?

[haboy52581]

the current dpm contract does not contain port info and this is in the configuration of dpm, if you want we could add them then change pm