> All I am saying is that Nova knows the instance's ID at the time that a
> config-drive can be created and installed into the instance. You can't
> do that with the "user data" EC2 API stuff, but you can with
> config-drive. Which is why I was recommending using config-drive.
>
> Best,
> -jay
>
>
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.pack...@canonical.com> wrote:
> On 24/07/2012, Jay Pipes wrote:
> >
> > The OpenStack Compute API POST /servers command creates a server UUID
> > that is pa
On 07/24/2012 01:10 PM, Martin Packman wrote:
> On 24/07/2012, Jay Pipes 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
On 24/07/2012, Jay Pipes 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
On 07/24/2012 12:47 PM, Martin Packman wrote:
> On 23/07/2012, Jay Pipes wrote:
>>
>> This is only due to the asinine EC2 API -- or rather the asinine
>> implementation in EC2 that doesn't create an instance ID before the
>> instance is launched.
>
> So, I'm curious, how do you allocate a server
On 23/07/2012, Jay Pipes wrote:
>
> This is only due to the asinine EC2 API -- or rather the asinine
> implementation in EC2 that doesn't create an instance ID before the
> instance is launched.
So, I'm curious, how do you allocate a server id in advance using the
openstack api so you can pass it
Scott thanks =P
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
On Sat, 21 Jul 2012, Matt Joyce wrote:
> Preamble:
>
> Until now, all data that is made available by the metadata server has been
> data that cannot be found anywhere else at the time it may be needed.
>
> In short, an instance can't be passed it's instance id before it's instance
> id has been al
Thanks Matt, comments inline...
On 07/23/2012 05:25 PM, Matt Joyce wrote:
> > I wish to add some data to the metadata server that can be found
> > somewhere else. That a user could jump through a hoop or two to
> add to
> > their instances. Esteemed personages are concerned that
> Agreed. I wish people didn't use the EC2 API at all, since it's a
> complete bag of fail and a beautiful example of a terribly thought-out
> API. That said, the OpenStack Compute API v2 has its share of pockmarks
> to be sure.
>
> But... unfortunately, if you're going to use the EC2 API this hard
On 07/21/2012 09:00 PM, Matt Joyce wrote:
> Preamble:
>
> Until now, all data that is made available by the metadata server has
> been data that cannot be found anywhere else at the time it may be needed.
>
> In short, an instance can't be passed it's instance id before it's
> instance id has bee
11 matches
Mail list logo
