Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Login to aeolus cli 2.issue the command aeolus-image import -h Actual results: Observed that in the out put of this command just 'id' was mentioned, this is confusing in terms of rhevm/vsphere images as user wont be knowing which id to put.(if the image was build/pushed from same machine) aeolus-image import -h Usage: aeolus-image import [command options] Options: -d, --id ID id for a given object -r, --description NAME description (e.g. "<image><name>MyImage</name></image>" or "/home/user/myImage.xml") -A, --account NAME,NAME name of specific account to import to -E, --environment ENVIRONMENT environment to import into -h, --help Get usage information for this command Examples: aeolus-image import --account my-ec2 --id $ami_id --environment default # import an AMI from the specified provider aeolus-image import --account my-ec2 --id $ami_id --environment default --description '<image><name>My Image</name></image>' # import an AMI from the specified provider Expected results: So it will be good to add either an example of rhevm/vsphere image import, or add description for -d option saying ami id for ec2 and template id in case of rhevm/vsphere providers. Additional info: rpm -qa | grep aeolus aeolus-conductor-doc-0.8.12-1.el6_2.noarch aeolus-configure-2.5.3-1.el6.noarch aeolus-conductor-daemons-0.8.12-1.el6_2.noarch aeolus-conductor-0.8.12-1.el6_2.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.8.12-1.el6_2.noarch rubygem-aeolus-cli-0.3.1-1.el6.noarch
This will be address as we migrate to imgfac2.0/tim + thor-cli tools.