create_instance - are public addresses returned ?

[Michael Neale]

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?

> From: [e-mail]

[mailto:deltacloud-
> [e-mail]] On Behalf Of Michael Neale
> Sent: Thursday, October 29, 2009 7:17 AM
> To: [e-mail]
> 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 Neale]

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  wrote:
> > From: [e-mail]
>
> [mailto:deltacloud-
> > [e-mail]] On Behalf Of Michael Neale
> > Sent: Thursday, October 29, 2009 7:17 AM
> > To: [e-mail]
> > 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.

[Bob McWhirter]

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  wrote:
> > > From: [e-mail]
> >
> > [mailto:deltacloud-
> > > [e-mail]] On Behalf Of Michael Neale
> > > Sent: Thursday, October 29, 2009 7:17 AM
> > > To: [e-mail]
> > > 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
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

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  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  wrote:
> > > > From: [e-mail]
> > >
> > > [mailto:deltacloud-
> > > > [e-mail]] On Behalf Of Michael Neale
> > > > Sent: Thursday, October 29, 2009 7:17 AM
> > > > To: [e-mail]
> > > > 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
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Ivan Meredith]

I would think the only thing that MUST be returned is a status url to
monitor the setup. The data such is image, name, etc that was used the
create the instance would be there too I guess.

We are changing our API around a bit to return the ID of the instance, then
as the instance is created we will populate the missing bits.

2009/10/30 Michael Neale
> 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 
> 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  wrote:
> > > > > From: [e-mail]
> > > >
> > > > [mailto:deltacloud-
> > > > > [e-mail]] On Behalf Of Michael Neale
> > > > > Sent: Thursday, October 29, 2009 7:17 AM
> > > > > To: [e-mail]
> > > > > 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
> > > [e-mail]
> > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
>
> --
> Michael D Neale
> home: www.michaelneale.net
> blog: michaelneale.blogspot.com
> _______________________________________________
> deltacloud-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/deltacloud-devel

[Michael Neale]

yes - well it says "an xml representation of the instance" - which is
shown above. That includes mostly links to the image/flavor etc (which
you know, as you say). Part of that representation is a link to
retrieve it in future, so yes, that is all good.
I don't think a change is needed more just peoples expectations and
that reflected in the doco.

Michael.

On Fri, Oct 30, 2009 at 12:23 PM, Ivan Meredith  wrote:
> I would think the only thing that MUST be returned is a status url to
> monitor the setup. The data such is image, name, etc that was used the
> create the instance would be there too I guess.
> We are changing our API around a bit to return the ID of the instance, then
> as the instance is created we will populate the missing bits.
>
> 2009/10/30 Michael Neale
> > 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 
> > 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  wrote:
> > > > > > From: [e-mail]
> > > > >
> > > > > [mailto:deltacloud-
> > > > > > [e-mail]] On Behalf Of Michael Neale
> > > > > > Sent: Thursday, October 29, 2009 7:17 AM
> > > > > > To: [e-mail]
> > > > > > 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
> > > > [e-mail]
> > > > https://fedorahosted.org/mailman/listinfo/deltacloud-devel
> >
> > --
> > Michael D Neale
> > home: www.michaelneale.net
> > blog: michaelneale.blogspot.com
> > _______________________________________________
> > deltacloud-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/deltacloud-devel