OK, I have changed my expectation to not expect it...
The docs are a bit vague - shoudl we make it explicit that things like address might not be set in the intitial response? (that is probably about it)?
On Thu, Oct 29, 2009 at 11:29 PM, Bob McWhirter bmcwhirt@redhat.com wrote:
No expectation it's there in the 1st response. Amazon might take minutes to fire up a node far enough to get an IP.
Oddly, if you terminate a node before it's completely up and has an address, it'll immediately obtain one. But it's useless, since your node is then shutting down.
-Bob
On Oct 29, 2009, at 4:47 AM, Michael Neale wrote:
I agree re async, but its not clear if the public address is expected in that initial response with a link etc...
On Thu, Oct 29, 2009 at 7:07 PM, Itamar Heim iheim@redhat.com wrote:
From: deltacloud-devel-bounces@lists.fedorahosted.org
[mailto:deltacloud-
devel-bounces@lists.fedorahosted.org] On Behalf Of Michael Neale Sent: Thursday, October 29, 2009 7:17 AM To: deltacloud-devel@lists.fedorahosted.org Subject: [deltacloud-devel] create_instance - are public addresses returned ?
I note that according to the spec when creating an instance an XML representation of that instance should be returned immeditately... however, on ec2, at least on its web console, it doesn't assign the public address until it is out of "pending" status ?
So should we not expect public addresses to be set until the server is ready?
[IH] to keep the responsiveness, such cases of async data should be considered as state (this doesn't qualify as statistics) and be polled/listened for.
-- Michael D Neale home: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel