XenAPI text console support
Bug #1004175 reported by
Mohammed Naser
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned | ||
Bug Description
At the moment, there is no support for XenAPI text console.
https:/
According to this blueprint, there is a feature in XS 6 that allows us to check it, but I'm still doing my readings...
https:/
| Changed in nova: | |
| assignee: | nobody → Mohammed Naser (mnaser) |
Revision history for this message
| Mohammed Naser (mnaser) wrote | #1 |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #2 |
| Changed in nova: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| tags: | added: xenserver |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #3 |
| Changed in nova: | |
| assignee: | Mohammed Naser (mnaser) → stelford (stef-ummon) |
| status: | Triaged → In Progress |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #4 |
| Changed in nova: | |
| assignee: | stelford (stef-ummon) → nobody |
| status: | In Progress → Confirmed |
Revision history for this message
| John Garbutt (johngarbutt) wrote | #5 |
| Changed in nova: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
So after further research, I have found a way to get all the console output from a specific point onwards. This would mean that the output is empty if we connect right away.
The resolution I see is to have a daemon that runs and keeps in track with all the consoles, however I am not sure on the best way to approach this.