Provisioning Requisition best practice

So I've got an inventory of ~1000 nodes.  I'm going through and refining 
the data and revisiting the provisioning reqs I'm using and I'm feeling 
kinda stuck.  Currently I have 33 reqs and the new layout is 38.  I've 
broken them down by general technology, polling frequency, division, 
etc.  I'm driving polling by categories so I'm using policies in the req 
definition to apply them.  Every requisition I add increases my overhead 
for imports, rebuilds, turning up a new box, etc.

My question is how detailed is too detailed.  For instance I have Linux 
and Windows servers in separate requisitions.  When multiplied by 
different sites and sometimes divisions it can add up.  I also have 
"core_switch" and "core_router" which multiplies when spread across 
sites and providers.  I've also got separate reqs for NetScaler, Proxy, 
and security, which get multiplied by three different managing 
organizations.  I know this is a bunch or art but I'd really appreciate 
any wisdom people can offer on how to approach this.

Thanks
Bill



_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss