Description of problem:
This bug was originally about enabling owners to use the CSV interface itself, as discussed on the mailing list , but after seeing bug 1117016, I'd like to file this as a list of "features", since the interface isn't all that important as the ability to perform the actions.
Therefore please allow system owners to modify the following in a more script-friendly way (ie. for modifying >10 machines at a time):
- basic details
- owner (if possible)
- current user (if possible)
- active loan (if possible)
- mac address
- architectures list
- key/values (if possible)
- groups list
- ACL details
- power config
- install options (per-arch lines)
These are the fields I use/modify when setting up (sometimes lots of) machines or virtual machines and the ability to do it without control-tab-ing through 20 tabs in the browser multiple times would be really welcome.
The ability to "set" instead of "add"/"remove" would also be useful to maintain consistency across machines.
Version-Release number of selected component (if applicable):
Please note that this RFE could be solved in more ways than one - it's about doing changes in batches, which could be done via the WebUI as well - something like "select the fields you want to copy from machine X and enter a list of machines as destinations".
Reviewing which of these are already scriptable:
System loans: loan-grant/loan-return
Manual reservations: system-reserve/system-release
Bug 804479 covers adding a change-condition command
Bug 1118884 covers adding a change-owner command
For the others, a generally available CSV import/export option actually may be the best answer.
Andrew, would you be able to provide some feedback on Jiri's problem description here? For folks with full admin access, how much of this functionality does the existing CSV import/export capability cover?
(In reply to Nick Coghlan from comment #4)
> Reviewing which of these are already scriptable:
> System loans: loan-grant/loan-return
> ACLs: policy-grant/policy-revoke
While that's certainly useful, a better approach for my case would be "set these ALCs, overriding anything original". Presuming that the machines are all in a certain state is not a good idea.
> Manual reservations: system-reserve/system-release
> Bug 804479 covers adding a change-condition command
> Bug 1118884 covers adding a change-owner command
> For the others, a generally available CSV import/export option actually may
> be the best answer.
(In reply to Nick Coghlan from comment #5)
> Andrew, would you be able to provide some feedback on Jiri's problem
> description here? For folks with full admin access, how much of this
> functionality does the existing CSV import/export capability cover?
Sorry for the really late response. But 90% of all of these things are doable via a csv. And for the things that are not the new cli options address this.
Normally I have a bunch of csv templates that I use to build my configs so I'm not writing them by hand which helps.
Another option to solve the use case of editing lots of nearly-identical machines would be to add a "templating" system where most of the properties could be shared between systems (acls, install options, excluded families, etc.) within a pool, which is IIRC already possible for ACLs.