Bug 754633

Summary: Let workflow-kernel support multihost test with --servers=SERVERS and --clients=CLIENTS options like workflow-simple by command line
Product: [Retired] Beaker Reporter: yanfu,wang <yanwang>
Component: command lineAssignee: Bill Peck <bpeck>
Status: CLOSED NOTABUG QA Contact: yanfu,wang <yanwang>
Severity: medium Docs Contact:
Priority: medium    
Version: 0.7CC: bpeck, dcallagh, mcsontos, mishin, rmancy, stl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: CommandLineEnhancements
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-24 13:38:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description yanfu,wang 2011-11-17 06:37:13 UTC
Description of problem:
If workflow-kernel could submit multihost test by command line?
And I knew workflow-simple have --servers=SERVERS and --clients=CLIENTS options, so could let workflow-kernel support that way by command line.

Version-Release number of selected component (if applicable):
$ rpm -qa|grep beaker
beaker-redhat-0.1.42-1.el6eso.noarch
beakerlib-1.3-7.el6.noarch
beakerlib-redhat-1-5.el6.noarch
beaker-client-0.7.3-4.el6eso.noarch
beaker-redhat-repo-0.2-6.el6eso.noarch
beaker-0.7.3-4.el6eso.noarch


Steps to Reproduce:
Seems can't use workflow-kernel to submit multihost test job by command line and specify hosts to be involved in multihost test for servers and clients.
I have to modify XML by manual.

Actual results:
can't use workflow-kernel to submit multihost test job by command line.

Expected results:
use workflow-kernel to submit multihost test job by command line.

Additional info:

Comment 1 Nick Coghlan 2012-10-17 04:36:17 UTC
Bulk reassignment of issues as Bill has moved to another team.

Comment 2 Nick Coghlan 2012-10-24 03:45:48 UTC
Bill, assigning this one back to you for the moment. How would you like to handle the maintenance of the workflow-kernel subcommand now? It's there for the kernel team, so perhaps it makes sense for you to have a a direct say in any additions?

Comment 3 Bill Peck 2012-10-24 13:38:31 UTC
The kernel group who wrote and maintains this workflow feel that this feature would not be good.  The kernel workflow produces a large matrix and adding these options would multiply that already large matrix even more.

Comment 4 yanfu,wang 2012-10-29 06:16:01 UTC
So could I file it as a feature?