These slides are a compare and contrast between Core 3 and Core 4.

1. HardCore4
Zenoss BoF @ LISA 2011, Boston
Simon Jakesch, simon@zenoss.com

2. State of Affairs
●
3.x has been out for about 1.5 years
●
about 70% of users on 3.x
●
new UI is helping especially new users
2

3. 3.x Lifetime
●
UI issues are resolved
●
completed SNMPv3 support (incl. Traps)
●
more pages transitioned
3

4. 3.x Problems
●
increased number of async. requests
●
big number of components and devices
●
lots of events
4

5. 5

6. Core 4: High Level Goals
●
solve current problems
●
prepare platform for the future
●
improve reliability and scale
●
provide further plugin points
6

7. RRDCached
●
lowered IO load
●
improved collection capabilities per
collector
7

8. Common Collector Framework
●
common functionality has been abstracted
●
improved consitency across all collection
8

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
9

10. Re-written Event System
●
RabbitMQ as event system backbone
●
multi-stage/process event pipeline
●
Lucene index backed event store
●
multi-threaded Java based event service
with REST api
10

11. 11

12. Core 4 Timelines
●
code available for build in January
●
alphas available at roughly the same time
●
release end of February
●
move to Github and JIRA April/March
12

13. Other Changes
●
Open Source release of zenwinperf
●
improved ZenPack landscape
●
native CentOS/RH 6.x builds
●
Core development on Github
●
switch to JIRA
13