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/18 16:29:33 UTC
[jira] [Updated] (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 updated SLIDER-441:
---------------------------------
Assignee: Sumit Mohanty
> 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
>
> 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)