it should be only governance registry if at all possible But problem is that with different registries we have two concepts.
1. idea of local, config, and governance category based on the function 2. Scope of replication (seen by) - local is local to the node, config is seen cluster wide, and governance is seen enterprise wide a) Is there any config that need to be seen across the enterprise? If yes we have a problem as that will force us to put configs in the governance registry b) But putting policies in the governance registry should be ok as it is anyway seen across the enterprise Does this make sense? If a = no and b=yes, policies must go in to governance registry only. --Srinath On Thu, Feb 17, 2011 at 4:57 PM, Amila Jayasekara <[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? > > According to my understanding it should always be governance registry. > > Thanks > AmilaJ > >> /sumedha >> >> On Thu, Feb 17, 2011 at 7:11 AM, Samisa Abeysinghe <[email protected]> wrote: >>> >>> When I try to add a secure proxy, I see on the UI that I am given the >>> choice to pick the security policy from either config or governance >>> registry. >>> Is this right? >>> I thought, this is a deployment information that we do not expose to user >>> (I mean even the admin user who add a proxy) >>> >>> 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 >>> >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- ============================ Srinath Perera, Ph.D. Senior Software Architect, WSO2 Inc. Visiting Lecturer, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ _______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
