Puppet users - Apr 2008 - automate things that don't have CLI (ie Cacti)

Hi Just curious how do you automate things like Cacti device creations
(not just installing it) that don''t have a command line.  I figured
either develop shell/perl/ruby scripts that directly touch the SQL
tables or do URL POST/GETs pretending to a web browser.  Neither would
really nice.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

From additional research I found out Cacti (as of 0.8.7) added a CLI.
The rpm we use from DAG for some reason doesn''t add it.  But I would
be curious how others handle issues that don''t have CLI options and
are just web/GUI based.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Wed, Apr 23, 2008 at 5:03 PM, Larry Ludwig <larrylud@gmail.com>
wrote:
>
>  From additional research I found out Cacti (as of 0.8.7) added a CLI.
>  The rpm we use from DAG for some reason doesn''t add it.  But I
would
>  be curious how others handle issues that don''t have CLI options
and
>  are just web/GUI based.
>
Honestly, I tend to pick other tools.

If you don''t have that option, you are left with two nasty ones:

A) Use something like WWW::Mechanize to fetch, parse, and manipulate
the Web UI.  This can really suck to maintain, since any changes to
the UI may break things.

B) Talk directly to the underlying datastructures (the database.)
This can be both time consuming to implement, as you have to
reverse-engineer the schema, and fragile in the same way as
manipulating the Web UI.

Having walked both roads, my answer is C: get a new tool.

Adam

-- 
HJK Solutions - We Launch Startups - http://www.hjksolutions.com
Adam Jacob, Senior Partner
T: (206) 508-4759 E: adam@hjksolutions.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 23/04/2008, Larry Ludwig <larrylud@gmail.com>
wrote:
>  Hi Just curious how do you automate things like Cacti device creations
>  (not just installing it) that don''t have a command line.  I
figured
>  either develop shell/perl/ruby scripts that directly touch the SQL
>  tables or do URL POST/GETs pretending to a web browser.  Neither would
>  really nice.
In theory, you could probably export and collect exec''s to make other
nodes execute commands on your node that hosts cacti. I don''t know
what the cacti web interface is like but this is the basic idea:

class cacti::host {
  Exec <<| tag == ''cacti'' |>>
}

class cacti::client {
  @@exec{ "/usr/bin/add_to_cacti $hostname $ipaddress":
    tag => ''cacti'',
    unless => "/usr/bin/command_that_checks_if_host_is_already_added
$host",
  }
}

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On 24/04/2008, ben <pr0ncracker@gmail.com> wrote:
> In theory, you could probably export and collect exec''s to make
other
>  nodes execute commands on your node that hosts cacti. I don''t
know
>  what the cacti web interface is like but this is the basic idea:
should say CLI    ^^^

I think I also misread your original message and assumed you were
asking how to use the CLI with puppet. Sorry to confuse.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---