Re: Module writing docs/coding guidelines

Aaron Peeler wrote: --On October 9, 2009 12:07:54 PM -0400 Sean Dilda wrote: 1. Use API calls instead of provided perl scripts - My experience writing cacti and nagios checks with the VIPerl Toolkit has shown that there's a heavy CPU hit for a few seconds while perl processes all of the VIPe

Re: Module writing docs/coding guidelines

--On October 9, 2009 12:07:54 PM -0400 Sean Dilda wrote: 1. Use API calls instead of provided perl scripts - My experience writing cacti and nagios checks with the VIPerl Toolkit has shown that there's a heavy CPU hit for a few seconds while perl processes all of the VIPerl libraries. Call

Re: Module writing docs/coding guidelines

Andy Kurth wrote: Hi Sean, Welcome! As Aaron mentioned, here is the provisioning module specification: http://cwiki.apache.org/confluence/display/VCL/Provisioning+Engine+Module+Interface+Specification If you haven't done so already, browse the pages under the following URL to familiarize yours

Re: Module writing docs/coding guidelines

Hi Sean, Welcome! As Aaron mentioned, here is the provisioning module specification: http://cwiki.apache.org/confluence/display/VCL/Provisioning+Engine+Module+Interface+Specification If you haven't done so already, browse the pages under the following URL to familiarize yourself with the backen

Re: Module writing docs/coding guidelines

Hi Sean, This should get you started: Aaron --On October 8, 2009 9:58:55 AM -0400 Sean Dilda wrote: I'm about to embark on writing a new provisioning module for VCL based on some existing per