| 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 line | Assignee: | Bill Peck <bpeck> |
| Status: | CLOSED NOTABUG | QA Contact: | yanfu,wang <yanwang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.7 | CC: | 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
Bulk reassignment of issues as Bill has moved to another team. 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? 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. So could I file it as a feature? |