A couple of the conversations I've had this week have brought up an important question that I don't think we've gotten into specifics on yet: what functionality will disposable clients need?
Stepping aside from specific cloud/virt systems for the moment, I put
together a list of Requirements, Possible Requirements (stuff we'd need
in order to support certain use-cases) and Nice to Haves for disposable
clients and wanted to see if this makes sense to other folks.
I've tried to abstract this to just what the client VMs would have to
do, so let's stay away from image management/generation methods and
other related topics for this thread.
Thoughts on this list? Did I miss anything or is there something on
this list that shouldn't be there?
Tim
Requirements
------------
* Use anything from a relatively arbitrary list of images
* Destroy-able after every task
* Fast boot time (say, 30 sec at most)
* The same images are available in identical form to all clients
* Ability to log remotely (syslog, taskotron.log, maybe others?)
Possible Requirements
---------------------
* Some capability for graphical connection (required for T377 and
similar tasks)
* Allow users to ssh into VMs for triage purposes
- Find a way to use FAS ssh key for auth? (possible security issues
with this)
- Something other than some global username/password
NTH
---
* capable of building images?
* capable of configuring itself or another host with something like
ansible
* capable of working with multi-host tests (spawning one or more
machines during task)
pgpVf_MAJ5FEo.pgp
Description: OpenPGP digital signature
_______________________________________________ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
