On Mon, Jan 6, 2014 at 12:10 PM, Shamika Ariyawansa <[email protected]>wrote:
> Hi, > > Is there any possibility of showing the user that what step of this > is exactly failed ?. So that user would know that due to that failure the > application creation process is cancelled and rolled back. > +1. That would help the user to get an understanding on why(or where) the app creation failed. Thanks, Janaka > > Regards > > > On Mon, Jan 6, 2014 at 11:57 AM, Ashansa Perera <[email protected]> wrote: > >> The main error situations would be the failures on any of the following >> actions >> - Repository creation >> - Build job creation >> - Issue repository creation >> - Authorize roles >> - Add users to application >> >> >> On Mon, Jan 6, 2014 at 11:12 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> What are the error situations that we roll back on? Are they numerous or >>> are they handful? >>> >>> Thanks, >>> Samisa... >>> >>> >>> Samisa Abeysinghe >>> >>> Vice President Developer Evangelism >>> >>> WSO2 Inc. >>> http://wso2.com >>> >>> >>> >>> On Mon, Jan 6, 2014 at 11:04 AM, Ashansa Perera <[email protected]>wrote: >>> >>>> @Ramith >>>> Application creation process do >>>> - repository creation >>>> - jenkins job creation >>>> - publish application creation ( which calls all the application event >>>> listeners ) >>>> >>>> >>>> On Mon, Jan 6, 2014 at 10:55 AM, Ashansa Perera <[email protected]>wrote: >>>> >>>>> Agree with Janaka's idea of having rollback mechanism first and of >>>>> course we can have retry logic in each operation as well. >>>>> >>>>> >>>>> On Mon, Jan 6, 2014 at 10:48 AM, Ramith Jayasinghe <[email protected]>wrote: >>>>> >>>>>> Shall we list down what are the steps involved in creating a >>>>>> application. then what needs to be to undo each step that was performed? >>>>>> >>>>>> >>>>>> On Mon, Jan 6, 2014 at 10:45 AM, Gayan Dhanushka <[email protected]>wrote: >>>>>> >>>>>>> Hi Janaka, >>>>>>> >>>>>>> IMO it is ok for us to have a mechanism for retrying. If it was an >>>>>>> intermittent issue that interrupted the system from creating the >>>>>>> application this will solve it. If the application creation failed after >>>>>>> retrying for a few times we can roll back the entire process. If it is >>>>>>> some >>>>>>> other serious issue rolling back and trying to start the application >>>>>>> creation process from the begining still won't work. >>>>>>> >>>>>>> WDYT? >>>>>>> >>>>>>> GayanD >>>>>>> >>>>>>> Gayan Dhanuska >>>>>>> Software Engineer >>>>>>> http://wso2.com/ >>>>>>> Lean Enterprise Middleware >>>>>>> >>>>>>> Mobile >>>>>>> 071 666 2327 >>>>>>> >>>>>>> Office >>>>>>> Tel : 94 11 214 5345 >>>>>>> Fax : 94 11 214 5300 >>>>>>> >>>>>>> Twitter : https://twitter.com/gayanlggd >>>>>>> >>>>>>> >>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ramith Jayasinghe >>>>>> Technical Lead >>>>>> WSO2 Inc., http://wso2.com >>>>>> lean.enterprise.middleware >>>>>> >>>>>> E: [email protected] >>>>>> P: +94 776715671 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Thanks & Regards, >>>>> >>>>> Ashansa Perera >>>>> Software Engineer >>>>> WSO2, Inc >>>>> >>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> >>>> Ashansa Perera >>>> Software Engineer >>>> WSO2, Inc >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Thanks & Regards, >> >> Ashansa Perera >> Software Engineer >> WSO2, Inc >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Shamika Ariyawansa > Senior Software Engineer > WSO2, Inc.; http://wso2.com > > LK - +94 7639629 Ext 5999 > US - +1 408 754 7388 Ext 51732 > Mob:+ 94 772929486 > > *twitter: > **https://twitter.com/Amila_Shamika*<https://twitter.com/Amila_Shamika> > * linked-in: *http://www.linkedin.com/pub/dir/Shamika/Ariyawansa > > > *Lean . Enterprise . Middleware* > > _______________________________________________ > 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* Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
