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

Posted to dev@stratos.apache.org by "Akila (JIRA)" <ji...@apache.org> on 2015/10/11 22:30:05 UTC

[jira] [Resolved] (STRATOS-1578) Removing a member from CloudControllerContext and Topology should be executed atomically

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

Akila resolved STRATOS-1578.
----------------------------
       Resolution: Fixed
    Fix Version/s:     (was: FUTURE)
                   4.1.4

Fixed in 8d46fab0f921e37d5f6da11f8006b68b3743226d

> Removing a member from CloudControllerContext and Topology should be executed atomically
> ----------------------------------------------------------------------------------------
>
>                 Key: STRATOS-1578
>                 URL: https://issues.apache.org/jira/browse/STRATOS-1578
>             Project: Stratos
>          Issue Type: Bug
>          Components: Cloud Controller
>    Affects Versions: 4.0.0, 4.1.0, 4.1.1, 4.1.2, 4.1.3
>            Reporter: Akila
>            Assignee: Akila
>             Fix For: 4.1.4
>
>
> When terminating a member, CC should handle the flow of operations such that Topology model and CloudControllerContext is consistent. In order to achieve that it should treat all CRUD operations related to Topology and CloudControllerContext as atomic transactions. If an operation on Topology fails it should not proceed or rollback the relevant operation executed on CloudControllerContext.



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