On Thu, Feb 17, 2011 at 12:22 PM, Hiranya Jayathilaka <[email protected]>wrote:
> Hi, > > On Thu, Feb 17, 2011 at 12:15 PM, Hiranya Jayathilaka <[email protected]>wrote: > >> >> >> On Thu, Feb 17, 2011 at 10:50 AM, Samisa Abeysinghe <[email protected]>wrote: >> >>> >>> >>> On Thu, Feb 17, 2011 at 9:12 AM, Sumedha Rubasinghe <[email protected]>wrote: >>> >>>> Are you suggesting something like Security Policy should always come >>>> from a specific registry, thus the user should be prevented from making >>>> that >>>> choice? >>> >>> >>> Yes, from governance registry in case of policies. My understanding was >>> such on these registries. >>> >> >> Configuration registry is where you store product specific configurations >> which need to be shared across multiple nodes in a cluster. Governance >> registry is where you store artifacts which are shared across the >> enterprise. So in case of security policies we need to be able to store it >> in both registry spaces. If the policy is used by a cluster of ESB >> instances, then it should go into the configuration registry. If the policy >> is used by ESB proxy services as well as services deployed in AS, then it >> should go into the governance registry. So IMO it is not correct to restrict >> where the user can store resources like policies. It is going to break our >> clustering story. >> > > +1 for providing the single rooted view in the registry browser though. We > should however a put some mechanism to prevent the user from selecting > resources from invalid locations like /_system/foo. > There are two conflicting requirements here. 1. You need to see everything under root 2. You need not to see some collections under root. Also, there is another use-case. Thinking in terms of Platform Governance, Policies must be under a single home, and not in anywhere inside config or governance. So, IMO, what we need is to only show the governance registry. Thanks, Senaka. > > >> >> Thanks, >> Hiranya >> >> >>> >>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Senior Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
