action #9546
closed
New Backend - Generic KVM over IP Backend
Added by RBrownSUSE about 9 years ago.
Updated almost 9 years ago.
Category:
Feature requests
Description
For use with the incoming Adder IPEPS KVM over IP
It will require effectively 3 settings, to be defined in workers.ini and then used by this backend
VNC Details - to tell the backend where the IPEPS KVM device is..then it'll use the VNC of the device just like we do in our typical qemu backend
SOL Details - This is to connect to the Serial of LAN device of the physical machine under testing. This will probably be in the form of a 'command', the same way we do with cscreen, which sometimes uses ipmitool, or telnet, or whatever.. whatever the command used needs to output a typical serial output, just like we use with cscreen
Power details - The backend will need to be able to control the power switches used in the QA lab for the hardware there, and/or use ipmitool to cycle the power on ipmi driven machines
I think we are missing a category "backend features" for this one. I propose to simply rename the current category "backend refactoring" to "backend" as "refactoring" is part of normal development.
okurz wrote:
I think we are missing a category "backend features" for this one. I propose to simply rename the current category "backend refactoring" to "backend" as "refactoring" is part of normal development.
Agreed - do you have sufficient rights in redmine to do that?
- Target version set to Milestone 1
- Category set to Feature requests
- Assignee changed from dimstar to coolo
it's blocked by lack of hardware
- Status changed from New to In Progress
- % Done changed from 0 to 20
I can't make serial work on the given host. The given port for csreen does not show data
- % Done changed from 20 to 80
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Also available in: Atom
PDF