Bug 752520

[root@qeblade31 ~]# aeolus-cli --help
Usage: aeolus-cli [list|build|push|import|delete] [general options] [command options]

General options:
    -d, --id ID                      id for a given object
        --description NAME           description (e.g. "<image><name>MyImage</name></image>" or "/home/user/myImage.xml")
    -r, --provider NAME1,NAME2       name of specific provider (ie ec2-us-east1)
    -T, --target TARGET1,TARGET2     provider type (ec2, rackspace, rhevm, etc)
    -h, --help                       Get usage information for this tool

List options:
    -i, --images                     Retrieve a list of images
    -b, --builds ID                  Retrieve the builds of an image
    -P, --providerimages ID          Retrieve the provider images from a target image
    -g, --targets                    Retrieve the values available for the --target parameter
    -p, --providers                  Retrieve the values available for the --provider parameter
    -a, --accounts                   Retrieve the values available for the --account parameter

Build options:
    -e, --template FILE              path to file that contains template xml

Push options:
    -t, --targetimages ID            Retrieve the target images from a build
    -A, --account NAME               name of specific provider account to use for push

Delete options:
    -I, --image ID                   delete build image and associated objects
    -B, --build ID                   delete build and associated objects
    -m, --targetimage ID             delete target image and its provider images
    -D, --providerimage ID           delete provider image

List Examples:
aeolus-cli list --images                    # list available images
aeolus-cli list --builds $image_id          # list the builds of an image
aeolus-cli list --targetimages $build_id    # list the target images from a build
aeolus-cli list --providerimages $target_id # list the provider images from a target image
aeolus-cli list --targets                   # list the values available for the --target parameter
aeolus-cli list --providers                 # list the values available for the --provider parameter
aeolus-cli list --accounts                  # list the values available for the --account parameter

Build examples:
aeolus-cli build --target ec2 --template my.tmpl        # build a new image for ec2 from based on the given template
aeolus-cli build --target ec2,rhevm --template my.tmpl  # build a new image for ec2 and for rhevm based on the given template

Push examples:
aeolus-cli push --account ec2-account,ec2-account2 --targetimage $target_image_id   # Push target images to each of the specified account
aeolus-cli push --account ec2-account,rhevm-account --build $build_id               # Push target images attached to a particular build to each of the specified accounts
aeolus-cli push --account ec2-account,rhevm-account --image $image_id               # Push target images attached to a particular image to each of the specified accounts

Import examples:
aeolus-cli import --provider ec2-us-east-1 --target ec2 --id $ami_id # import an AMI from the specified provider
aeolus-cli import --provider ec2-us-east-1 --target ec2 --id $ami_id --description '<image><name>My Image</name></image>' # import an AMI from the specified provider
aeolus-cli import --provider ec2-us-east-1 --target ec2 --id $ami_id --description <path_to_xml_file> # import an AMI from the specified provider

Delete examples: (DELETE CURRENTLY NOT IMPLEMENTED) 
aeolus-cli delete --image $image_id               # deletes a image and all associated builds
aeolus-cli delete --build $build_id               # deletes a build and all associated targetimages
aeolus-cli delete --targetimage $target_image     # deletes a target image and all associated provider images
aeolus-cli delete --providerimage $provider_image # deletes a provider image

removing bugs from ce-sprint from the tracker.. you can find these bugs by querying the "qa whiteboard" for ce-sprint-60

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0591.html