The input constraints to scheduler is incorrect

fno2010 commented 6 years ago

The submitted task:

[
  {
    "id": 1,
    "jobs": [
      {
        "potential_srcs": [
          {
            "ip": "10.10.14.6",
            "port": 1234
          }
        ],
        "potential_dsts": [
          {
            "ip": "10.10.14.7",
            "port": 4444
          }
        ],
        "protocol": "tcp",
        "file-size": 100000
      },
      {
        "potential_srcs": [
          {
            "ip": "10.10.14.7",
            "port": 1235
          }
        ],
        "potential_dsts": [
          {
            "ip": "10.10.14.6",
            "port": 4445
          }
        ],
        "protocol": "tcp",
        "file-size": 100000
      }
    ]
  }
]

The orchestrator log:

[2017-11-13 12:40:58,774] [orchestrator] [INFO] Starting a scheduling thread...
[2017-11-13 12:40:58,774] [orchestrator] [DEBUG] Input constraints: [<flow:2> <= 100000000]
[2017-11-13 12:40:58,774] [orchestrator] [INFO] Start scheduling
[2017-11-13 12:40:58,788] [orchestrator] [DEBUG] Output result: {2: 100000000.0}
[2017-11-13 12:40:58,788] [orchestrator] [INFO] Handling the scheduling result...
[2017-11-13 12:40:58,789] [orchestrator] [DEBUG] Applying (job: 1) transfer 10.10.14.7 -> 10.10.14.6 to dtn 131.215.207.189 with rate 100000000

Why there is only one flow in the input constraints?

fno2010 commented 6 years ago

Further log message:

[2017-11-13 12:55:41,449] [orchestrator] [DEBUG] Resource query to Caltech-Campus get response:{'meta': {'code': 'success'}}
[2017-11-13 12:55:41,944] [orchestrator] [DEBUG] update resource query: Caltech-Campus
[2017-11-13 12:55:41,945] [orchestrator] [DEBUG] Get resouirce query lock: add_resource_query_response
[2017-11-13 12:55:42,283] [orchestrator] [INFO] Resource query complete, contains 1 domains
[2017-11-13 12:55:42,283] [orchestrator] [INFO] Resource query update
[2017-11-13 12:55:42,284] [orchestrator] [DEBUG] Get resouirce query lock: resource_query_complete_operation
[2017-11-13 12:55:42,284] [orchestrator] [DEBUG] resource query response before rsa: {'ane-matrix': [[{'flow-id': '2'}]], 'anes': [{'availbw': 100000000}]}
[2017-11-13 12:55:42,407] [orchestrator] [DEBUG] resource query response after rsa: {'anes': [{'availbw': 100000000}], 'ane-matrix': [[{'flow-id': '2'}]]}

resource query only get one flow :(

fno2010 commented 6 years ago

This is an issue from alto-unicorn rpc in ODL.

# curl -v -u admin:admin http://sdn0-odl:8181/restconf/operations/alto-unicorn:resource-query -H 'Content-type: application/json' -d '{"input":{"resource-query-desc":[{"flow-id":0,"flow":{"src-ip":"10.10.14.6/32","dst-ip":"10.10.14.7/32"}}, {"flow-id":1,"flow":{"src-ip":"10.10.14.7/32","dst-ip":"10.10.14.6/32"}}]}}'

{"output":{"anes":[{"availbw":100000000,"ane-flow-coefficient":[{"flow-id":1}]},{"availbw":100000000,"ane-flow-coefficient":[{"flow-id":1}]}]}}

yjlcoder commented 6 years ago

The problem is made by the odl adapter of domain agents. Closed.

openalto / alto-orchestrator

The input constraints to scheduler is incorrect #14