Hide Forgot
Description of problem: ============================== Not sure what the requirements are for this but I imagine customers will want the option to push images into multiple rhevm datacenters. Currently aeolus only supports a single rhevm nfs export domain (which can only be mapped to a single rhevm datacenter). Much like the ec2 model of pushing to us-east vs us-west, we might want to consider changing the aeolus rhevm model to support a rhevm provider per datacenter?
adding to sprint tracker
The Deltacloud part is already here. In Deltacloud you can specify the datacenter you want to speak with using API_PROVIDER (similar to EC2 regions) in form: API_PROVIDER="https:/url:8775/rhevm-api;UUID-OF-DATACENTER" Deltacloud will then use the specified datacenter for listing images/instances/etc. Additionally client should be able to discover all available datacenters in "/api/drivers/rhevm". I think because this bug is IW related (RHEV-M NFS export domain) it should be assigned to someone from IW crew :)
Can we mark this RFE as verified?
good 2 go with: aeolus-all-0.8.0-17.el6.noarch aeolus-conductor-0.8.0-17.el6.noarch aeolus-conductor-daemons-0.8.0-17.el6.noarch aeolus-conductor-doc-0.8.0-17.el6.noarch
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-0583.html