On Fri, Apr 20, 2012 at 11:23 AM, Supun Kamburugamuva <[email protected]>wrote:
> In general I think having two ways of configuration is a mistake. Having > that kind of a model confuses users and make the life harder for developers > as well. Also it means we haven't figured out the correct places for > correct configuration as well. If there are two ways of configurations they > should be synched. For example if both carbon.xml and UI are allowed, a > change done in UI should be reflected in carbon.xml and vise versa. Which makes things very messy! :) We just need to keep this simple, identify the roles people play, and then decide what to have in the UI and what to have in the config files. It is a myth that UIs are more user friendly and config files are not. Depending on the situation & requirement, UIs or config files should be chosen. We have gained a lot of experience in managing Carbon production deployments through running StratosLive production clusters, and now have quite a good idea where each have their uses. Clearly, our techops team will never use the UIs to configure SLive, so that gives a good indication of how other techops & admin teams will configure our servers. > > Thanks, > Supun.. > > > On Fri, Apr 20, 2012 at 1:49 AM, Nuwan Dias <[email protected]> wrote: > >> Ok then, we'll have both options. If configurations are specified in >> carbon.xml, run the UI in read-only mode and display an Information >> Message. If not, allow users to configure through the UI. >> >> Thanks, >> NuwanD. >> >> >> On Fri, Apr 20, 2012 at 11:13 AM, Afkham Azeez <[email protected]> wrote: >> >>> >>> >>> On Fri, Apr 20, 2012 at 11:02 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>>> >>>> >>>> On Fri, Apr 20, 2012 at 11:00 AM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> >>>>> >>>>> On Fri, Apr 20, 2012 at 10:58 AM, Hiranya Jayathilaka < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Fri, Apr 20, 2012 at 10:47 AM, Miyuru Wanninayaka <[email protected] >>>>>> > wrote: >>>>>> >>>>>>> One alternative is support both registry and carbon.xml >>>>>>> configuration and give priority to carbon.xml. So if someone configured >>>>>>> deployment synchronizer by editing carbon.xml, UI will just run on >>>>>>> read-only mode. UI should only allow configuring if dep-sync is not >>>>>>> configured in carbon.xml. >>>>>> >>>>>> >>>>>> That is how it's presently implemented. So just leave the code as it >>>>>> is without removing anything, and it'll work just fine. >>>>>> >>>>> >>>>> See my previous mail. I don't believe this is useful in the Carbon >>>>> console since configuring this is not part of the Carbon admin's role. >>>>> >>>> >>>> That's not true. We already have users who extensively use this UI. >>>> It's great in dev and staging environments where developers can access the >>>> system over the web and try out stuff. >>>> >>> >>> OK. Let's leave it at it then. The UI looks great, and information like >>> last checked out time & commit now are useful. However, I don't see the >>> configuration part of this being used in SLive like production setups. See >>> Sanjaya's response. >>> >>>> >>>> Thanks, >>>> Hiranya >>>> >>>> >>>>> >>>>>> Thanks, >>>>>> Hiranya >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Apr 20, 2012 at 10:27 AM, Sanjaya Ratnaweera < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Apr 19, 2012 at 2:59 PM, Afkham Azeez <[email protected]>wrote: >>>>>>>> >>>>>>>>> What do you mean this will make the carbon.xml based synchronizer >>>>>>>>> obsolete? You mean we won't be able to configure the server using the >>>>>>>>> carbon.xml file and will be forced to use the UI to do that? If so, >>>>>>>>> -1. It >>>>>>>>> will be a huge usability issue for sysadmins. Talk to Sanjaya & see >>>>>>>>> how we >>>>>>>>> do things to manage Carbon servers in production. >>>>>>>>> >>>>>>>>> >>>>>>>> Yes, we never touch UI when managing deployments. For example in >>>>>>>> Stratoslive we change configuration files and keep them in a separate >>>>>>>> location. At the deployment time we unzip a fresh pack and sync changed >>>>>>>> configurations with that. If we store those configurations in local >>>>>>>> registry we may have to login to each and every instance and change. >>>>>>>> This >>>>>>>> is not a one time change, because sometimes we delete the pack and >>>>>>>> unzip a >>>>>>>> fresh one when there are file corruptions, etc. >>>>>>>> >>>>>>>> Anyway keeping configurations in a XML file is much easier for >>>>>>>> production deployment. >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> ~sanjaya >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Apr 19, 2012 at 1:52 PM, Nuwan Dias <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> Hi Hiranya, >>>>>>>>>> >>>>>>>>>> Thanks for the suggestions, will increase the SVN URL field >>>>>>>>>> length. Yes, input validations have been done. >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> NuwanD. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Apr 19, 2012 at 1:47 PM, Hiranya Jayathilaka < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Looks pretty good. Please increase the length of the SVN URL >>>>>>>>>>> input field. URL fields are usually long. I hope proper input >>>>>>>>>>> validations >>>>>>>>>>> are all in place. >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Hiranya >>>>>>>>>>> >>>>>>>>>>> On Thu, Apr 19, 2012 at 12:18 PM, Nuwan Dias <[email protected]>wrote: >>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> I have developed a UI for the SVN based deployment synchronizer >>>>>>>>>>>> as per the task in https://wso2.org/jira/browse/ESBJAVA-893. >>>>>>>>>>>> This will make is possible to provide svn parameters for the svn >>>>>>>>>>>> based >>>>>>>>>>>> deployment synchronizer through the UI. It will however make the >>>>>>>>>>>> existing >>>>>>>>>>>> server configuration based (carbon.xml) deployment synchronizer >>>>>>>>>>>> obsolete >>>>>>>>>>>> and will be using the local registry to store and retrieve svn >>>>>>>>>>>> parameters. >>>>>>>>>>>> >>>>>>>>>>>> A screenshot of the deployment synchronizer page is attached >>>>>>>>>>>> herewith. Suggestions welcome. >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> -- >>>>>>>>>>>> Nuwan Dias >>>>>>>>>>>> >>>>>>>>>>>> Software Engineer - WSO2, Inc. >>>>>>>>>>>> Integration Technologies Team >>>>>>>>>>>> email : [email protected] >>>>>>>>>>>> Phone : +94 777 775 729 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Nuwan Dias >>>>>>>>>>>> >>>>>>>>>>>> Software Engineer - WSO2, Inc. >>>>>>>>>>>> Integration Technologies Team >>>>>>>>>>>> email : [email protected] >>>>>>>>>>>> Phone : +94 777 775 729 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Dev mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Hiranya Jayathilaka >>>>>>>>>>> Associate Technical Lead; >>>>>>>>>>> WSO2 Inc.; http://wso2.org >>>>>>>>>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>>>>>>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Nuwan Dias >>>>>>>>>> >>>>>>>>>> Software Engineer - WSO2, Inc. >>>>>>>>>> Integration Technologies Team >>>>>>>>>> email : [email protected] >>>>>>>>>> Phone : +94 777 775 729 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Afkham Azeez* >>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>>>>>> * <http://www.apache.org/>** >>>>>>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>>>>>> twitter: >>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>>>>>> * >>>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>>>>>> * >>>>>>>>> * >>>>>>>>> *Lean . Enterprise . Middleware* >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Dev mailing list >>>>>>>>> [email protected] >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sanjaya Ratnaweera >>>>>>>> Senior Software Engineer; WSO2 Inc; http://www.wso2.com/. >>>>>>>> >>>>>>>> blog: http://www.samudura.org >>>>>>>> homepage: http://www.samudura.net >>>>>>>> twitter: http://twitter.com/sanjayar >>>>>>>> >>>>>>>> >>>>>>>> Lean . Enterprise . Middleware >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thanks, >>>>>>> Miyuru >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Hiranya Jayathilaka >>>>>> Associate Technical Lead; >>>>>> WSO2 Inc.; http://wso2.org >>>>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Associate Technical Lead; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Nuwan Dias >> >> Software Engineer - WSO2, Inc. >> Integration Technologies Team >> email : [email protected] >> Phone : +94 777 775 729 >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Supun Kamburugamuva > Member, Apache Software Foundation; http://www.apache.org > E-mail: [email protected] <[email protected]>; Mobile: +94 77 431 3585 > Blog: http://supunk.blogspot.com > > > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
