Hi, At the time we designed the dashboard aligning to the new registry model, we had a discussion of this, and came to a decision that the Gadgets will reside in the configuration registry, since they are product specific. So at the moment if any one product is in a cluster (i.e. if GS has 3 nodes) and since the config registry is shared among the clustered nodes, the product dashboard can see its own gadgets. (/config/repository/gadget-server/gadgets)
However with the Startos story we will have to re-change this model :), and move the shared gadgets to the governance registry and product specific gadgets to the config registry. Regards, /Nuwan On Sat, Dec 4, 2010 at 10:29 AM, Senaka Fernando <[email protected]> wrote: > > > On Sat, Dec 4, 2010 at 10:13 AM, Afkham Azeez <[email protected]> wrote: > >> >> >> On Sat, Dec 4, 2010 at 1:53 AM, Chintana Wilamuna <[email protected]>wrote: >> >>> Hi, >>> >>> Why gadget XMLs are stored in the config registry and not in >>> governance registry? Since usually config registries are shared >>> between a cluster how would this work if it's GS is clustered? >>> >> >> Correction! Config registries are NOT shared between clusters. Config >> registries are shared by all nodes in A cluster. e.g. a single ESB cluster >> will point to a single config registry, and an AS cluster will point to a >> different config registry. It is the Governance registry that is shared >> across clusters. So, all nodes in the above ESB & AS clusters will point to >> the same Governance registry. >> > > IMO, if we are to share these gadgets among multiple products, which should > be theoretically possible, we need to have them on the governance registry. > > I believe that we had some similar requirement for Stratos? Don't recall > this completely, though. IIRC, the idea was to have product-specific > dashboard configurations on the config registry, and to have gadgets on the > governance registry. > > Thanks, > Senaka. > >> >> >>> >>> Thanks in advance, >>> >>> -Chintana >>> >>> -- >>> Chintana Wilamuna >>> Associate Technical Lead >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> phone: +94 75 211 1106 >>> blog: http://engwar.com/ >>> photos: http://flickr.com/photos/chintana >>> linkedin: http://www.linkedin.com/in/engwar >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >> >> >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; 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* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Senaka Fernando* > Associate Technical Lead & Product Manager - WSO2 G-Reg; > 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] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Thanks & Regards, Nuwan Bandara WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://www.nuwanbando.com <http://www.nuwanbando.com/>
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
