You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aurora.apache.org by Amol Deshmukh <am...@apache.org> on 2016/04/30 00:54:00 UTC

Tier Management: Default Tiers

As a follow up to the discussion on the review request at
https://reviews.apache.org/r/46803/ I have updated the tier management
proposal document to compare the options for implementing the defaulting
logic for the tiers.

Please feel free to comment directly in the doc:
https://docs.google.com/document/d/1erszT-HsWf1zCIfhbqHlsotHxWUvDyI2xUwNQQQxLgs/edit#heading=h.x1y1n2g8av7i

Thanks!

Re: Tier Management: Default Tiers

Posted by Maxim Khutornenko <ma...@apache.org>.

Since there are no objections raised in the linked design summary, we are
going to proceed with option B suggested by Amol, namely:

"Scheduler requires a tier; client uses a new scheduler API to determine
the tier options and populates the tier by selecting the default tier
obtained from the API."

On Fri, Apr 29, 2016 at 3:54 PM, Amol Deshmukh <am...@apache.org> wrote:

> As a follow up to the discussion on the review request at
> https://reviews.apache.org/r/46803/ I have updated the tier management
> proposal document to compare the options for implementing the defaulting
> logic for the tiers.
>
> Please feel free to comment directly in the doc:
>
> https://docs.google.com/document/d/1erszT-HsWf1zCIfhbqHlsotHxWUvDyI2xUwNQQQxLgs/edit#heading=h.x1y1n2g8av7i
>
> Thanks!
>