You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/10/02 19:34:34 UTC

[jira] [Commented] (SLIDER-105) Agent provider service/client should reject component instance count when it exceeds the specified maximum or below the minimum

    [ https://issues.apache.org/jira/browse/SLIDER-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156825#comment-14156825 ] 

Steve Loughran commented on SLIDER-105:
---------------------------------------

if this meta-info is in the app spec, the AM app state could track this. provider would pass ranges of component types to AM and it would look at things.

Issue: how to react to not enough components? we could/should reject too large, too small is a config check ... the allocated nodes may be less than this.


> Agent provider service/client should reject component instance count when it exceeds the specified maximum or below the minimum
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SLIDER-105
>                 URL: https://issues.apache.org/jira/browse/SLIDER-105
>             Project: Slider
>          Issue Type: Bug
>          Components: agent-provider
>    Affects Versions: Slider 0.30
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>
> metainfo.xml provides the minimum and maximum count of instances for each component. Agent provider should enforce this when application is created or flexed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)