Use resource statistics to adjust resource score

[soichih]

/resource/stats/:id API now provides following statistics

  "find": {
    "resource_id": "57902acad5db11477c94c1aa"
  },
  "counts": {
    "finished": 4,
    "running": 3,
    "removed": 1,
    "failed": 1
  },
  "services": [
    {
      "_id": {
        "service": "soichih/app-test",
        "status": "failed"
      },
      "count": 1
    },
    {
      "_id": {
        "service": "soichih/app-test",
        "status": "running"
      },
      "count": 2
    },
    {
      "_id": {
        "service": "brain-life/app-networkneuro",
        "status": "running"
      },
      "count": 1
    },
    {
      "_id": {
        "service": "soichih/app-test",
        "status": "removed"
      },
      "count": 1
    },
    {
      "_id": {
        "service": "soichih/app-test",
        "status": "finished"
      },
      "count": 4
    }
  ]
}

I should polish this (maybe allow querying based on service so that I can make a single query to get all info?) and adjust resource score based on past service performance on that resource. For example, there is no point of keep submitting to resource that the service always fails.

[soichih]

If I do provide service centric stats, for each resource, I should also include average waiting / running time. Such information is valuable for determining the final resource score.

The service centric stats can also be used by warehouse under application detail page to show some interesting statistics about the app.