TECHZEN Zenoss User Community ARCHIVE  

Circular ZenPack installation

Subject: Circular ZenPack installation
Author: Luke Lofgren
Posted: 2017-06-27 08:36

We have a moderate size Zenoss implementation (~10k devices) using a single collector. I love the ability to have "no downtime zenpack installs" with 5.2.4, but I've had limited success so far. The Cisco ZenPack install (albeit when we were on 5.2.3) kept doing its long process...and then restarting. Somehow that evening it didn't keep going in circles. Today I tried to do the Layer2 ZenPack, but after 4 loops, I shut down ZenModeler and then tried it again, only to have a couple more loops. Any suggestions on anything else I could shut down to allow a "zero downtime" zenpack install? Also, weirdly, it seems to have "committed" the ZenPack since my the new container for Layer2 relationships is now showing up at the root (and hey, that doesn't belong there -- find a sub-branch!).

Maybe ZenPack documentation now needs to start suggesting what containers are needed to be shut down for their installation.

------------------------------
Luke Lofgren
Infrastructure Architect
Acxiom Corporation (home based associate)
Waterford PA
------------------------------


Subject: RE: Circular ZenPack installation
Author: Luke Lofgren
Posted: 2017-06-28 07:43

I still had trouble getting Layer 7 to install after having many things shut down (but not all); then I remembered we have a pretty constant stream of ZenJobs from "trap triggered switch re-discoveries". So I was able to get Layer 2 ZenPack to install without disabling user access to Zope after turning off (stopping) ZenJobs. I did also have most everything else stopped at the same time, so this isn't definitive, but something I'll be trying to replicate in the future.

------------------------------
Luke Lofgren
Infrastructure Architect
Acxiom Corporation (home based associate)
Waterford PA
------------------------------


< Previous
Memory requirements for installing ZenPacks
  Next
Use API to poll device / change device config
>