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

Posted to dev@stratos.apache.org by "Reka Thirunavukkarasu (JIRA)" <ji...@apache.org> on 2015/04/30 12:08:06 UTC

[jira] [Updated] (STRATOS-1297) Stratos 4.1.0: Updating deployment policy Min/Max has no effect on instance count of applications referring to the affected policy.

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

Reka Thirunavukkarasu updated STRATOS-1297:
-------------------------------------------
    Fix Version/s: 4.1.0 Beta2

> Stratos 4.1.0: Updating deployment policy Min/Max has no effect on instance count of applications referring to the affected policy.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: STRATOS-1297
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1297
>             Project: Stratos
>          Issue Type: Bug
>          Components: Cloud Controller
>    Affects Versions: 4.1.0 Alpha
>            Reporter: Martin Eppel
>             Fix For: 4.1.0 Beta2
>
>
> Application created which references a deployment policy should inherit any changes to the PartitionMin/Max settings, otherwise we have no way to changing the number of instances without deleting the application instances.
> Please refer also to the email exchange on the dev mailing list:
> "[Discuss] Cartridge definition doesn't need "maxInstanceLimit" property anymore" for more detail.



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