On 7 June 2016 at 17:41, Jim Rollenhagen wrote:
> On Tue, Jun 07, 2016 at 03:10:24PM +0100, Daniel P. Berrange wrote:
>> On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote:
>> > Right, so that's a third case. How I'd see this working is maybe an
>> > image
On Tue, Jun 07, 2016 at 03:10:24PM +0100, Daniel P. Berrange wrote:
> On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote:
> > On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote:
> > > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
> > >
> > > >
I think nova should completely ignore this issue and boot the image no matter
what. This is an operational 'workflow', and nova doesn't need to know about
the image internals at all. If it boots, then is not nova problem.
Ghe Rivero
Quoting Clif Houck (2016-06-06 23:41:12)
> Hello all,
>
>
On Tue, Jun 07, 2016 at 09:37:25AM -0400, Jim Rollenhagen wrote:
> On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote:
> > On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
> >
> > > Hello all,
> > >
> > > At Rackspace we're running into an interesting problem:
On Tue, Jun 07, 2016 at 08:31:35AM +1000, Michael Still wrote:
> On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
>
> > Hello all,
> >
> > At Rackspace we're running into an interesting problem: Consider a user
> > who boots an instance in Nova with an image which only
On Mon, Jun 6, 2016, at 05:44 PM, Gregory Haynes wrote:
>
> On Mon, Jun 6, 2016, at 05:31 PM, Michael Still wrote:
>> On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
>>> Hello all,
>>>
>>> At Rackspace we're running into an interesting problem: Consider
>>> a user
>>> who
On Mon, Jun 6, 2016, at 05:31 PM, Michael Still wrote:
> On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
>> Hello all,
>>
>> At Rackspace we're running into an interesting problem: Consider
>> a user
>> who boots an instance in Nova with an image which only supports SSH
On Tue, Jun 7, 2016 at 7:41 AM, Clif Houck wrote:
> Hello all,
>
> At Rackspace we're running into an interesting problem: Consider a user
> who boots an instance in Nova with an image which only supports SSH
> public-key authentication, but the user doesn't provide a public
Hello all,
At Rackspace we're running into an interesting problem: Consider a user
who boots an instance in Nova with an image which only supports SSH
public-key authentication, but the user doesn't provide a public key in
the boot request. As far as I understand it, today Nova will happily
boot