We need to understand the different roles here. Clearly, creating the depsync UI shows that we have not understood the different roles people play when it comes to Carbon deployments.
1. sysadmin - Configures Carbon server/SVN repositories/databases/clusters/load balancers/SSL certs, creates backups, applies patches, does software upgrades, does OS hardening, configures firewalls etc. 2. Carbon admin - configures global security policies, adds user stores/keystores etc. 3. Carbon Application deployer - deploys apps/services etc. into Carbon servers 4. Carbon Application users - invoke applications deployed on Carbon servers The depsync functionality is one that falls under the "sysadmin" role. Those guys don't want to configure stuff using Carbon UIs or mess with configurations in DBs. Ideally, they don't even login to the Carbon server. So, I don't think this UI belongs in the Management Console. Thanks Azeez On Fri, Apr 20, 2012 at 10:47 AM, Miyuru Wanninayaka <miy...@wso2.com>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. > > > On Fri, Apr 20, 2012 at 10:27 AM, Sanjaya Ratnaweera <sanj...@wso2.com>wrote: > >> >> >> On Thu, Apr 19, 2012 at 2:59 PM, Afkham Azeez <az...@wso2.com> 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 <nuw...@wso2.com> 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 >>>> <hira...@wso2.com>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 <nuw...@wso2.com> 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 : nuw...@wso2.com >>>>>> Phone : +94 777 775 729 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Nuwan Dias >>>>>> >>>>>> Software Engineer - WSO2, Inc. >>>>>> Integration Technologies Team >>>>>> email : nuw...@wso2.com >>>>>> Phone : +94 777 775 729 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Hiranya Jayathilaka >>>>> Associate Technical Lead; >>>>> WSO2 Inc.; http://wso2.org >>>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>> >>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Software Engineer - WSO2, Inc. >>>> Integration Technologies Team >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> 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: **az...@wso2.com* <az...@wso2.com>* 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 >>> Dev@wso2.org >>> 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 >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thanks, > Miyuru > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
