Basically what we need is some kind of a monitoring system to figure out if everything is running smoothly. And possibly have ways to correct inconsistencies/errors that occur. In my view its might not be realistic to log in to servers directly and do modifications when the deployment becomes large.
On Wed, Dec 4, 2013 at 4:56 PM, Ushani Balasooriya <[email protected]> wrote: > Hi, > > Can we have the $subject. During the Automation demo, Internal issue > tracker was down. But when I proceeded with the flow, meantime could get it > up. > > Then when I tried to select the project from the drop down list of the > Issue tracker, the app was not visible since the issue tracker was down > during the app creation. So all the other actions taken was a waste. > > If there is a system to ensure all the other apps needed to this flow is > available, I think we can get rid of these type of issues. > > > Thanks and Regards, > -- > *Ushani Balasooriya* > Software Engineer - QA; > WSO2 Inc; http://www.wso2.com/. > Mobile; +94772636796 > > -- 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
