In accordance to our Release Policy we’re continuing support of generation of 19.1 releases. NOC 19.1.1 collects 114 bugfixes, optimization and improvements, while fully preserves 19.1 API. Migration Migration from 19.1 release is straightforward. Just deploy 19.1.1 or stable-19.1 tags from Tower. Bugfixes MR Title !1560 fm-alarm i18n !1561 Add tags field to managedobject BI extractor. !1563 Add 40G interfaces support to Cisco.
In accordance to our Release Policy we’re proudly present release 19.2. 19.2 release contains of 337 bugfixes, optimisations and improvements. Highlights ConfDB 19.2 introduces new configuration processing framework, the ConfDB. ConfDB is the crystallisation of our over decade experience of configuration processing. Set of carefully designed tools, clean API and flexible query language offer the unified way of configuration parsing, validation, processing and converting. Target area covers data extraction (without complex scripts), config validation, querying and inter-vendor configuration conversions.
In accordance to our Release Policy we’re continuing support of generation of 18.1 releases. NOC 18.1.1 collects 35 bugfixes, optimization and improvements, while fully preserves 18.1 API. Migration Migration from 18.1 release is straightforward. Just deploy 18.1.1 or stable-18.1 tags from Tower. Bugfixes MR Title !1215 Fix platform field in Platform Card. !1208 #947 Fix MAC ranges optimization !
In accordance to our Release Policy we’re proudly present release 19.1. 19.1 release contains of 272 bugfixes, optimisations and improvements. Highlights Usability NOC Theme 19.1 introduces genuine NOC theme intended to replace venerable ExtJS’ gray. New flat theme is based upon Triton theme using NOC-branded colors. NOC theme can be activated via config on per-installation basis. We expect to make it default several releases later. Collection Sharing Collections is the viable part of NOC.
In accordance to our Release Policy we’re starting generation of 18.1 releases. microservices branch has been forked from main tree about 3 years ago and bring massive architecture changes addressing performance, stability and scalability issues. Considering amount of changes, we’d recommend migration to microservices only for advanced users, seeking particular benefits. All development efforts was focused on microservices and we must admit we’d reached excellent result. Microservices’ offsprings monitor very large networks and we’d got invaluable experience of dealing with 300k+ boxes by single cluster.