> On Sep 21, 2017, at 10:00 AM, Łukasz Łukasiewicz > <lukasz.lukasiew...@codilime.com> wrote: > > > > On Thu, Sep 21, 2017 at 6:23 PM, Harshad Nakil <hna...@gmail.com > <mailto:hna...@gmail.com>> wrote: > 1. Contrail analytics is sigle repository of all the operational state of the > system. Think of analytics API as “show commands on the router” Over a period > with different requirements from customers, this design has evolved and may > have become complicated. Many operators want streaming API for operational > state. Evil with analytics has been the cassandra DB. Analytics (my be > misnomer) has always been integral part of contrail. > > I think the point here is not to remove analytics completely - analytics > (telemetry) is necessary to keep OpenContrail as a viable product from > network operator perspective. My goal here would be: in case of analytics > failure, your cluster is still operational and the only thing affected by > analytics failure is cluster health visibility by operator. I believe this is > not the case today and failures in analytics may cause funky behavior of the > cluster. Yes cluster should continue to function, that is the aim. Issues you faced were due to bad design choices or bad code and not architectural issues. I don’t agree with your assertion that contrail is viable product without contrail analytics shutdown (operational status) and other services in contrail should not use analytics API (operational status). > > > 5. If juniper makes something proprietary then it is their problem to keep > compatibility as the data is coming or consumed by open source components. > > Agreed, but that's the case for the future. As of today (up until 5.0), we > don't know the details on how this change affects existing codebase. If it > doesn't - nothing changes for us really. If it does - I would expect > blueprints to be there before the code. Especially considering community > being quite active and importance of such change. > > Thanks, > Lukas. > > P.S. Can I get the invite to the next TSC meeting? > > > ------------------------------- > The information in this email is confidential and may be legally privileged, > it may contain information that is confidential in CodiLime Sp. z o. o. It is > intended solely for the addressee. Any access to this email by third parties > is unauthorized. If you are not the intended recipient of this message, any > disclosure, copying, distribution or any action undertaken or neglected in > reliance thereon is prohibited and may result in your liability for damages.
_______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
