Hi Scott,
There was some ambiguity with one of the BZs that this patch tried to address.
After some conversation with imcleod on Friday we've now cleared up how aoelus-image
push should work. So this patch won't be going in.
Cheers
Martyn
----- Original Message -----
From: "Scott Seago" <sseago(a)redhat.com>
To: aeolus-devel(a)lists.fedorahosted.org
Sent: Saturday, 16 July, 2011 7:12:59 AM
Subject: Re: [PATCH aeolus] BZ#721050 - Removed references to multiple provider push in
docs
On 07/15/2011 05:48 AM, mtaylor(a)redhat.com wrote:
From: Martyn Taylor<mtaylor(a)redhat.com>
---
.../aeolus-image/lib/config_parser.rb | 2 +-
.../image_factory/aeolus-image/lib/push_command.rb | 25 ++++++++++++--------
.../aeolus-image/man/aeolus-image-push.1 | 2 +-
3 files changed, 17 insertions(+), 12 deletions(-)
diff --git a/services/image_factory/aeolus-image/lib/config_parser.rb
b/services/image_factory/aeolus-image/lib/config_parser.rb
index c62b599..60b40cd 100644
--- a/services/image_factory/aeolus-image/lib/config_parser.rb
+++ b/services/image_factory/aeolus-image/lib/config_parser.rb
@@ -141,7 +141,7 @@ module Aeolus
opts.separator ""
opts.separator "Push examples:"
- opts.separator "aeolus-image push --provider ec2-us-east-1,my-rhev-m --id
$image_id # push the image to the specified providers"
+ opts.separator "aeolus-image push --provider ec2-us-east-1 --id $image_id
# push the image to the specified provider"
OK I'm a bit confused
here. We just agreed that we would _not_ support
pushing to one provider now and another provider later (the whole
"latest_unpushed is null problem) since the two images won't be in sync
(for snapshot images).
Doesn't that mean that the only correct way to push to both ec2 US-east
and US-west would be to specify multiple providers on the push call?
Scott
_______________________________________________
aeolus-devel mailing list
aeolus-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/aeolus-devel