On Thu, Sep 10, 2015 at 1:29 AM, Akila Ravihansa Perera <raviha...@wso2.com> wrote:
> > Shall we call the topic as 'initializer' to be generic? We can further > extend this to Application hierarchy model initialization and tenant model > initialization using the same topic. These are also published periodically > by AS and SM respectively. > +1 A great thought! On Thu, Sep 10, 2015 at 1:29 AM, Akila Ravihansa Perera <raviha...@wso2.com> wrote: > Hi Imesh, > > Great thought. This will considerably speed up instance activation process. > > Shall we call the topic as 'initializer' to be generic? We can further > extend this to Application hierarchy model initialization and tenant model > initialization using the same topic. These are also published periodically > by AS and SM respectively. > > Thanks. > > On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne <im...@apache.org> wrote: > >> Hi Devs, >> >> I would like to propose $subject. >> >> Currently we do this with a one minute interval and its causing the >> cartridge agent and the servers to wait for around two minutes (in the >> worst case) to start. In Docker this is a considerable amount of delay. >> >> I think we can implement $subject by introducing another topic (say >> topology-init) and asking the clients to request Complete Topology event >> via the new topic. This can be done in messaging component without >> affecting the main modules (AS, CC, SM, CEP, JCA). PCA needs to be updated >> accordingly. WDYT? >> >> Thanks >> >> -- >> Imesh Gunaratne >> >> Senior Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > Akila Ravihansa Perera > WSO2 Inc.; http://wso2.com/ > > Blog: http://ravihansa3000.blogspot.com > -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
