Bug 584555 - [RFE] Need a web UI for scheduling jobs
Summary: [RFE] Need a web UI for scheduling jobs
Status: NEW
Alias: None
Product: Beaker
Classification: Community
Component: web UI   
(Show other bugs)
Version: 0.5
Hardware: All Linux
medium vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact:
Whiteboard: UX
Keywords: FutureFeature, Regression, Triaged
Depends On:
Blocks: 1063555
TreeView+ depends on / blocked
Reported: 2010-04-21 20:41 UTC by Zack Cerza
Modified: 2018-11-09 23:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Zack Cerza 2010-04-21 20:41:46 UTC
Currently, the only way to schedule a job is via a previously-prepared XML file. RHTS allowed us to easily submit one-off jobs without that overhead. I'm assuming it's planned to re-add that feature, but I need a bug to add the the sign-off page.

Comment 1 Bill Peck 2010-04-22 14:24:03 UTC
This is not something that is going to happen for live.  You can input an xml from scratch on the UI if need be.

Comment 2 Chris Ward 2010-05-26 11:26:11 UTC
"This is not something that is going to happen for live." I'm not sure i understand this response. Does it mean 'this will never happen' or 'this feature will not block beaker and legacy rhts tear down'

Comment 5 Dan Callaghan 2010-10-19 06:28:46 UTC
(In reply to comment #4)
> Its possible we
> could even use the xsd to generate the forms?  

That is a very interesting idea.

I'm picturing kind of like a guided XML editor (in js on the client side) with collapsible elements. The users starts with an empty <job/> element and can fill in new recipes by starting with the minimum mandatory set of elements for a recipe. The ui would make it easy to add optional child elements, and to fill in element content and attribute values. It could display documentation for each element/attribute in a little box beside where the user is editing. And all of it would be generated from the XSD (or the RELAX NG schema).

Let me think some more about how impossible that will be :-)

Comment 6 David Kovalsky 2010-11-18 16:26:03 UTC
This requires UI changes, further work is scheduled for 0.6. 

We won't block RHTS decomission for this bug anyway, so I'm moving it to HotBeakerBugs for further tracking.

Note You need to log in before you can comment on or make changes to this bug.