You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2014/09/26 01:19:35 UTC

[jira] [Resolved] (SLIDER-441) Rename DO_NOT_PROPAGATE to be more user-friendly

     [ https://issues.apache.org/jira/browse/SLIDER-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Mohanty resolved SLIDER-441.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Slider 0.60

> Rename DO_NOT_PROPAGATE to be more user-friendly
> ------------------------------------------------
>
>                 Key: SLIDER-441
>                 URL: https://issues.apache.org/jira/browse/SLIDER-441
>             Project: Slider
>          Issue Type: Improvement
>          Components: appspec
>    Affects Versions: Slider 0.50
>            Reporter: Andrew Grande
>            Assignee: Sumit Mohanty
>            Priority: Minor
>             Fix For: Slider 0.60
>
>
> As discussed on the list, the DO_NOT_PROPAGATE is a critical option for scenarios where e.g. a farm of containers is being deployed with unique ports. The param ensures 'flex' command and registry report correct port assignments (they don't get sticky port values).
> Internals of a Slider container lifecycle are too much to understand for a newcomer, make this property into more obvious PER_CONTAINER or PER_INSTANCE for example.



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