Перейти к содержанию

Blog

NOC 19.1.2 is Released

In accordance to our Release Policy we're continuing support of generation of 19.1 releases. NOC 19.1.2 collects 18 bugfixes, optimization and improvements, while fully preserves 19.1 API.

Migration

Migration from 19.1 release is straightforward. Just deploy 19.1.2 or stable-19.1 tags from Tower.

NOC 19.2.1 is Released

In accordance to our Release Policy we're continuing support of generation of 19.2 releases. NOC 19.2.1 collects 69 bugfixes, optimization and improvements, while fully preserves 19.2 API.

Migration

Migration from 19.2 release is straightforward. Just deploy 19.2.1 or stable-19.2 tags from Tower.

NOC 19.1.1. is Released

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.

NOC 18.1.1 is Released

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.

NOC 18.1.a1 is Released

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.

Due to diverge of code base some features of older NOC have not been ported, holding large part of users from migration. So we did our best to close known regression and to streamline migration path.

18.1 generation symbolizes API and codebase stabilization and encourages users of older releases to upgrade. Its main intention is to offer next stable release to migrate and to offer alternative to rolling releases of microservices.

We introduce 18.1a1, first alpha on 18.1. Alpha is not related to performance and stability. We expect the migration from relative fresh microservices will be smooth and similar to simple microservices upgrade. Just select 18.1a1 tag in Tower instead of microservices branch.

For users of NOC 15.05 and 15.05.01 migration path may consider some manual operations and will be detailed by later documents. We expect some glitches on the way and ready to debug and fix them. It is due to migration from elder releases we marked this release as alpha. We consider to hold alpha stage until 01.10.2018, introducing several intermediate alpha releases. Then the branch will be finalized and 18.1 will be marked.

The users of microservices is urged to upgrage if they choose 18.1 for stability. The users of elder releases are asked to join Community and ask the DevTeam to help with migration.

New Release Policy

In order to finalize 3 years of microservices development and to switch from rolling release to more common release practice we introduce a new release policy.