On 2 February 2016 at 14:11, Sascha Vogt wrote:
> Hi,
>
> Am 31.01.2016 um 18:57 schrieb John Garbutt:
>> We need to make sure we don't have configuration values that change
>> the semantic of our API.
>> Such things, at a minimum, need to be discoverable, but are best
Hi,
Am 31.01.2016 um 18:57 schrieb John Garbutt:
> We need to make sure we don't have configuration values that change
> the semantic of our API.
> Such things, at a minimum, need to be discoverable, but are best avoided.
I totally agree on that. I
>> I think an off-loaded / shelved resource
On 27 January 2016 at 16:59, Sascha Vogt wrote:
> Hi Andrew,
>
> Am 27.01.2016 um 10:38 schrieb Andrew Laski:
>> 1. This allows for a poor experience where a user would not be able to
>> turn on and use an instance that they already have due to overquota.
>> This is a
Hi Andrew,
Am 27.01.2016 um 10:38 schrieb Andrew Laski:
> 1. This allows for a poor experience where a user would not be able to
> turn on and use an instance that they already have due to overquota.
> This is a change from the current behavior where they just can't create
> resources, now
On Tue, Jan 26, 2016, at 07:46 AM, Christian Berendt wrote:
> After offloading a shelved instance the freed compute resources are
> still accounted.
>
> I think it makes sense to make this behavior configurable. We often have
> the request to not account the freed compute resources after an
After offloading a shelved instance the freed compute resources are
still accounted.
I think it makes sense to make this behavior configurable. We often have
the request to not account the freed compute resources after an
instances was offloaded to be able to spawn new instances or to