-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/17/2015 08:16 AM, Jim Perrin wrote:
I've been asked a couple times privately for information about this, so here's my current thinking on the project goals.
Just a note that we'll want to migrate development-focused conversations to cents-devel. It's OK that things are all over the place right now, that's part of getting started. :)
All students should be subscribed to that list as well.
Regards - Karsten
must-have:
- be able to exec (or otherwise connect to a container) and
perform a 'yum update' of the container, commiting the results upon successful completion. eg - yum dockerupdate -y centos # run yum -y update in the centos:latest container.
- Traditional yum interaction is expected (prompting for 'y/n',
or accepting options like -y)
Passing exit values from the container to the host.
Exit with message on unsupported containers.
documentation and invalid-command syntax fails to usage/help.
nice-to-have:
- tab complete support for commands as well as available
containers. 2. support for non-rpm based updates (support apt for debian/ubuntu based containers)
questionable:
glob/regex support to perform update on every matching container
Comments/Questions?
- -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41