You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Isuru Haththotuwa (JIRA)" <ji...@apache.org> on 2015/05/11 15:41:01 UTC
[jira] [Comment Edited] (STRATOS-1387) Validate Startup Order and
Dependency Scaling Prefixes at Group Deployment
[ https://issues.apache.org/jira/browse/STRATOS-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537823#comment-14537823 ]
Isuru Haththotuwa edited comment on STRATOS-1387 at 5/11/15 1:40 PM:
---------------------------------------------------------------------
Fixed in commit b946b934e31bc75d2cf7bfc7b94d04c757ebaa50.
was (Author: isuruh):
Fixed in commit b0ef0ccf3491610cf5fbec10b40e955fa31823d3.
> Validate Startup Order and Dependency Scaling Prefixes at Group Deployment
> --------------------------------------------------------------------------
>
> Key: STRATOS-1387
> URL: https://issues.apache.org/jira/browse/STRATOS-1387
> Project: Stratos
> Issue Type: Bug
> Affects Versions: 4.1.0 Beta2
> Reporter: Isuru Haththotuwa
> Assignee: Isuru Haththotuwa
> Fix For: 4.1.0
>
>
> In [1, 2], we have code explicitly depending on two prefixes used for startup order and scaling order, 'cartridge.' and 'group.' .We should validate this at Service Group deployment time, since otherwise startup order / scaling will not work as expected.
> [1]. org.apache.stratos.autoscaler.applications.dependency.DependencyBuilder
> [2]. org.apache.stratos.autoscaler.applications.parser.ParserUtils
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)