I too agree on a roll-back mechanism, I think it's the best, if it's possible to implement such. I guess we need to analyse and see whether it's possible to roll-back all the operations done in this process.
On Mon, Jan 6, 2014 at 10:33 AM, Janaka Ranabahu <[email protected]> wrote: > Hi Manjula, > > > On Mon, Jan 6, 2014 at 10:24 AM, Manjula Rathnayake <[email protected]>wrote: > >> Hi all, >> >> Another option is to retry to create the application even after failed. >> There we create the application again and again until it get created. If it >> fails, users should be able to role back. In this process, for example, if >> application rxt adding process succeeds but creating git repo fails, we >> should be able to create git repo and continue without trying to add the >> rxt. >> > If I understood you correctly, then what we need to do is to retry the > failed process/action a number of times. But that can not guarantee whether > the app creation would complete successfully. Say that the git repo > creation(or any other task) failed due to a network error or some other > serious issue. Then retrying will not solve the issue. IMO, what we need in > the first place is the rollback functionality and as an improvement we can > do the retry logic. > > WDYT? > > Thanks, > Janaka > >> >> thank you. >> >> >> On Mon, Jan 6, 2014 at 10:06 AM, Ashansa Perera <[email protected]> wrote: >> >>> Hi all, >>> >>> To make the application creation process resilient we discussed to >>> implement a rollback mechanism so that if any resource/infrastructure >>> creation failed while creating the application we can rollback the app >>> creation. With this we would be able to reuse the same application key and >>> utilize the resources. >>> Another suggestion was to ping the external servers before starting >>> application creation process, but since pinging servers cannot guarantee >>> anything >>> as server can fail in between, we will be going ahead with the rollback >>> application creation. >>> >>> -- >>> Thanks & Regards, >>> >>> Ashansa Perera >>> Software Engineer >>> WSO2, Inc >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Manjula Rathnayaka >> Software Engineer >> WSO2, Inc. >> Mobile:+94 77 743 1987 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Janaka Ranabahu* > Senior Software Engineer; WSO2 Inc.; http://wso2.com > > > * E-mail: [email protected] <http://wso2.com>**M: **+94 718370861 > <%2B94%20718370861>* > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks & regards, Nirmal Senior Software Engineer- Platform Technologies Team, WSO2 Inc. Mobile: +94715779733 Blog: http://nirmalfdo.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
