Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the discussion around the
ideal behaviour.
The bug is at: https://bugs.launchpad.net/nova/+bug/1458122
Basically the problem is this:
When booting up ins
On 26 May 2015 at 03:37, Chris Friesen wrote:
>
> Hi all,
>
> I've just opened a bug around booting multiple instances at once, and it was
> suggested on IRC that I mention it here to broaden the discussion around the
> ideal behaviour.
>
> The bug is at: https://bugs.launchpad.net/nova/+bug/1458
s.net]
Sent: Wednesday, May 27, 2015 3:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] I think nova behaves poorly when booting
multiple instances
On 26 May 2015 at 03:37, Chris Friesen wrote:
>
> Hi all,
>
> I've just opene
On 05/27/2015 05:09 PM, Fox, Kevin M wrote:
If the current behavior is broken, and the behavior is causing problems with
things like fixing quota's, should it just be deprecated and pushed off to
orchestration rather then change it?
Is this causing problems with quotas? The problem I brought u
: Chris Friesen [chris.frie...@windriver.com]
Sent: Wednesday, May 27, 2015 6:38 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [nova] I think nova behaves poorly when booting
multiple instances
On 05/27/2015 05:09 PM, Fox, Kevin M wrote:
> If the current behavior is broken,
On Mon, May 25, 2015 at 11:37 PM, Chris Friesen
wrote:
>
>
> Also, I think that if nova can't schedule "max count" instances, but can
> schedule at least "min count" instances, then it shouldn't put the
> unscheduled ones into an error state--it should just delete them.
>
> Thoughts?
>
Frankly sp
On 27 May 2015 at 23:36, Robert Collins wrote:
> On 26 May 2015 at 03:37, Chris Friesen wrote:
>>
>> Hi all,
>>
>> I've just opened a bug around booting multiple instances at once, and it was
>> suggested on IRC that I mention it here to broaden the discussion around the
>> ideal behaviour.
>>
>>
Le 29/05/2015 14:27, John Garbutt a écrit :
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the discussion ar
On 05/29/2015 06:27 AM, John Garbutt wrote:
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Basically the problem is this:
When booting up instances, nova allows the user to specify a "min count" and
a "max count". So logically, this request sh
John Garbutt wrote:
On 27 May 2015 at 23:36, Robert Collins wrote:
On 26 May 2015 at 03:37, Chris Friesen wrote:
Hi all,
I've just opened a bug around booting multiple instances at once, and it was
suggested on IRC that I mention it here to broaden the discussion around the
ideal behaviour.
On 29 May 2015 at 17:10, Chris Friesen wrote:
> On 05/29/2015 06:27 AM, John Garbutt wrote:
>>
>> On 27 May 2015 at 23:36, Robert Collins wrote:
>>>
>>> On 26 May 2015 at 03:37, Chris Friesen
>>> wrote:
>
>
Basically the problem is this:
When booting up instances, nova allows the
On 05/27/15 at 07:38pm, Chris Friesen wrote:
On 05/27/2015 05:09 PM, Fox, Kevin M wrote:
If the current behavior is broken, and the behavior is causing problems with
things like fixing quota's, should it just be deprecated and pushed off to
orchestration rather then change it?
Is this causing
On Jun 1, 2015, at 8:26 AM, Andrew Laski wrote:
>> In any case, even if we wanted to deprecate it (and I think an argument
>> could be made for that) we still have to decide what the "correct" behaviour
>> should be for the API as it exists today. In my view the current behaviour
>> doesn't m
Andrew Laski said on Mon, Jun 01, 2015 at 09:26:33AM -0400:
> However what these parameters give users, versus orchestrating
> outside of Nova, is the ability to have the instances all scheduled
> as a single block.
We should seek to provide this via persistent claims. IE add to the
API something
Alexis Lee said on Tue, Jun 02, 2015 at 11:28:03AM +0100:
> Paul Murray tells me there was a blueprint for this some time ago, but
> I can't find a spec for it. I'm interested in pushing this, I'll put up
> a spec at some point unless someone beats me to it.
Oops, found it, thanks Paul:
https:
On 06/02/15 at 11:28am, Alexis Lee wrote:
Andrew Laski said on Mon, Jun 01, 2015 at 09:26:33AM -0400:
However what these parameters give users, versus orchestrating
outside of Nova, is the ability to have the instances all scheduled
as a single block.
We should seek to provide this via persist
On 06/02/2015 02:36 PM, Andrew Laski wrote:
There used to be a project that I think was looking for an API like this to
provide a reservation system, Climate or Blazar or something. There was brief
talk of providing something like it for that use case, but the idea was put on
the backburner to w
On 06/02/2015 07:25 PM, Chris Friesen wrote:
On 06/02/2015 02:36 PM, Andrew Laski wrote:
There used to be a project that I think was looking for an API like
this to
provide a reservation system, Climate or Blazar or something. There
was brief
talk of providing something like it for that use cas
On 06/02/2015 07:48 PM, Jay Pipes wrote:
On 06/02/2015 07:25 PM, Chris Friesen wrote:
In many cases only nova-compute can resolve races (resource tracking of
specific CPU cores, specific PCI devices, etc. in the face of parallel
scheduling) so unless we're going to guarantee no races then I th
Le 02/06/2015 22:36, Andrew Laski a écrit :
On 06/02/15 at 11:28am, Alexis Lee wrote:
Andrew Laski said on Mon, Jun 01, 2015 at 09:26:33AM -0400:
However what these parameters give users, versus orchestrating
outside of Nova, is the ability to have the instances all scheduled
as a single bloc
Le 03/06/2015 04:17, Chris Friesen a écrit :
On 06/02/2015 07:48 PM, Jay Pipes wrote:
On 06/02/2015 07:25 PM, Chris Friesen wrote:
In many cases only nova-compute can resolve races (resource tracking of
specific CPU cores, specific PCI devices, etc. in the face of parallel
scheduling) so un
(I unfortunately need to quote a second time since Chris cut half of the
message below)
Le 03/06/2015 03:48, Jay Pipes a écrit :
On 06/02/2015 07:25 PM, Chris Friesen wrote:
On 06/02/2015 02:36 PM, Andrew Laski wrote:
There used to be a project that I think was looking for an API like
this t
22 matches
Mail list logo
