I think we can't remove the existing periodically published complete topology completely until we address all the scenarios that complete topology event used for. This may be impact to the LB extensions as well.As a first step we can remain the complete topology as it is and use the Topology init message for the cartridge agent. Gradually we can address other components as well. BTW I think we can increase the complete topology publisher time interval with the introduction of the topology init functionality.
On Mon, Nov 9, 2015 at 10:24 AM, lahirus <g...@git.apache.org> wrote: > Github user lahirus commented on the pull request: > > https://github.com/apache/stratos/pull/487#issuecomment-154924258 > > Hi Imesh, > > Do we plan to remove existing, periodically published complete > topology? > > Thanks. > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket > with INFRA. > --- > -- Gayan Gunarathne Technical Lead, WSO2 Inc. (http://wso2.com) Committer & PMC Member, Apache Stratos email : gay...@wso2.com | mobile : +94 775030545 <%2B94%20766819985>
