Bug 1118884

Summary:	RFE: ability to change system owner from CLI
Product:	[Retired] Beaker	Reporter:	Keith Fryklund <kfryklun>
Component:	command line	Assignee:	Amit Saha <asaha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.17	CC:	aigao, asaha, dcallagh, ebaak, jzhao, rmancy
Target Milestone:	19.0	Keywords:	FutureFeature, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1119930 (view as bug list)		Environment:
Last Closed:	2014-11-25 07:18:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1014438
Bug Blocks:	1119930

Description Keith Fryklund 2014-07-11 19:19:31 UTC

Your team recently added the ability to "loan-grant" and "loan-return" via beaker-client which has been a very useful addition.

It would be helpful to the eng-ops labs and fls teams if we could also change a beaker systems "Owner" and "Condition" via beaker-client.  

-Keith Fryklund

Comment 2 Nick Coghlan 2014-07-15 21:26:34 UTC

This fits with the general theme of moving towards better support for using Beaker as a backend service platform rather than going through the main web UI, so ack'ing this one.

I'm going to split it into two RFEs though, since the two commands can be implemented and tested separately. This one can cover change-owner, and I'll move the change-condition RFE out to a new one.

Comment 3 Amit Saha 2014-08-15 02:30:45 UTC

On Gerrit: http://gerrit.beaker-project.org/#/c/3251/

Comment 4 Dan Callaghan 2014-08-18 01:20:53 UTC

change-owner is not a great name for a subcommand, since it's not clear that it's changing the system owner. Also, to avoid subcommand proliferation and to match the existing job-modify, I suggest we do

    bkr system-modify FQDN --owner=USERNAME

Similarly the other bug 1119930 would be

    bkr system-modify FQDN --condition=Broken

Comment 5 Amit Saha 2014-08-18 05:10:15 UTC

(In reply to Dan Callaghan from comment #4)
> change-owner is not a great name for a subcommand, since it's not clear that
> it's changing the system owner. Also, to avoid subcommand proliferation and
> to match the existing job-modify, I suggest we do
> 
>     bkr system-modify FQDN --owner=USERNAME
> 
> Similarly the other bug 1119930 would be
> 
>     bkr system-modify FQDN --condition=Broken

Yeah, this sounds better. Also leaves the option for adding support for modifying other system attributes.

Comment 6 Nick Coghlan 2014-08-18 05:38:42 UTC

A system-modify subcommand sounds good to me.

Comment 7 Amit Saha 2014-09-22 02:38:54 UTC

http://gerrit.beaker-project.org/#/c/3251/

Comment 10 Dan Callaghan 2014-11-25 07:18:27 UTC

Beaker 19.0 has been released.