introduction to core 4
TRANSCRIPT
2
State of Affairs
● 3.x has been out for about 1.5 years
● about 70% of users on 3.x
● 51% are on 3.2.1
● new UI is helping especially new users
3
3.x Lifetime
● Remaining UI has been transitioned to Ext
● completed SNMPv3 support (incl. Traps)
● more pages transitioned
4
3.x Problems
● Zope problems due to increased number of
async. requests
● Scale with big number of components and
devices
● Scale with lots of events
5
6
Core 4: High Level Goals
● solve current problems
● prepare platform for the future
● improve reliability and scale
● provide more plugin points
7
RRDCached
● lowered IO load
● improved collection capabilities per
collector
● more info: http://bit.ly/auyPEU
8
Common Collector Framework
● common functionality has been abstracted
● improved consistency across all collection
daemons
● easier to write your own via ZenPacks
9
RelStorage and memcached
● CMDB/Zope data is no longer stored in flat file but MySQL
instead
● MySQL 5.5.15+ required to take advantage of new InnoDB
plugin
● memcached for intermediary/shared cache for all clients of
CMDB/Zope data
● more info: http://bit.ly/8g5iQ
10
Re-written Event System
● RabbitMQ as event system backbone
● new DB schema + MySQL 5.5+
● multi-stage/process event pipeline
● Lucene index backed event store
● multi-threaded Java based event service with REST api
11
12
Short Demo
behind the scenes
13
Other Changes
● Open Source release of all Windows
monitoring and discovery
● improved ZenPack landscape / ZenPack Repo
● native CentOS/RH 6.x builds
● switch to JIRA
14
Outlook & Questions
● BugHunt is ongoing (http://bit.ly/xeEKkX)
● GA Release expected mid–end May
● next webinar on the 26th of April (event
mgt. and transforms)
● upcoming Core 4 Windows webinar
● IRC: irc.freenode.net #zenoss