Show internal scheduler information
Currently, NoValidHost exception happend without any detail information.
The only way to find out the reason is looking through nova logs. But if there
are thousands of host, it will make sysadmin crazy.
So the blueprint propose an API to show internal information of scheduler process.
The API shows the filter result of each host and the reason why the host is failed.
The API looks like bellow:
GET /v2/{tenant}
{
"schedule_
{
"host": "ops1",
},
{
"host": "ops2",
},
{
"host": "ops3",
}
]
}
Blueprint information
- Status:
- Not started
- Approver:
- Andrew Laski
- Priority:
- Undefined
- Drafter:
- Tiantian Gao
- Direction:
- Needs approval
- Assignee:
- Qiu Yu
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Bug #1161661: Rescheduling loses reasons | Fix Released |
Bug #1165034: nova scheduler overwrites instance fault and masks underlying compute driver problems | Confirmed |
Sprints
Whiteboard
@Tiantian, as we discussed in Hong Kong summit. I'd like to assign myself to this BP. Besides, it could be related to BP record-
[1] https:/
Please find more discussion at following link. --qiuyu
http://
[alaski] Can this be accomplished by just storing the reason in an instance-
[qiuyu] Yes, that's what I'm trying to do by storing such infomation into instance-
https:/
[qiuyu] The orignal requirement shall be addressed after following two bp [1][2]have been finished. Could someone assign me the bp so that I could update the bp dependency here?
[1] https:/
[2] https:/
[1] https:/
Please find more discussion at following link. --qiuyu
http://
[alaski] Can this be accomplished by just storing the reason in an instance-
[qiuyu] Yes, that's what I'm trying to do by storing such infomation into instance-
https:/
[qiuyu] The orignal requirement shall be addressed after following two bp [1][2]have been finished. Could someone assign me the bp so that I could update the bp dependency here?
[1] https:/
[2] https:/
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)@Tiantian, as we discussed in Hong Kong summit. I'd like to assign myself to this BP. Besides, it could be related to BP record-
[1] https:/
Please find more discussion at following link. --qiuyu
http://
[alaski] Can this be accomplished by just storing the reason in an instance-
[qiuyu] Yes, that's what I'm trying to do by storing such infomation into instance-
https:/
[qiuyu] The orignal requirement shall be addressed after following two bp [1][2]have been finished. Could someone assign me the bp so that I could update the bp dependency here?
[1] https:/
[2] https:/
[1] https:/
Please find more discussion at following link. --qiuyu
http://
[alaski] Can this be accomplished by just storing the reason in an instance-
[qiuyu] Yes, that's what I'm trying to do by storing such infomation into instance-
https:/
[qiuyu] The orignal requirement shall be addressed after following two bp [1][2]have been finished. Could someone assign me the bp so that I could update the bp dependency here?
[1] https:/
[2] https:/
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)
Work Items
Dependency tree
* Blueprints in grey have been implemented.