What I am doing is putting credentials into user sessions on the instance. -Matt On Tue, Jul 24, 2012 at 10:10 AM, Martin Packman < martin.packman at canonical.com> wrote: > On 24/07/2012, Jay Pipes <jaypipes at gmail.com> wrote: > > > > The OpenStack Compute API POST /servers command creates a server UUID > > that is passed back in the initial response and allows the user to query > > the status of the server throughout its launch sequence. > > I'm not really seeing how that improves on the situation compared to > the EC2 api. If a server needs to know its own id, it must either > communicate with an external service or be able to use the compute > api, which means putting credentials on the instance. Or am I missing > a trick? > > Martin > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120724/ae0c13bf/attachment.html>