[ANN] Spike Asset Manager release 0.13

[mh]

Spike Asset Manager (SAM) is an open-source cross-platform framework
written in python for probing a system for components and reporting
them. It includes a driver file that probes for components commonly
found in a LAMPJ stack (Apache, MySQL, PHP, Tomcat, etc). Note that
the L in LAMP could be Linux, Solaris, Windows or Mac. SAM can find
multiple versions that are installed, query the rpm database and
indicate whether components are running.

Release 0.13 changes:
- Migrate to ElementTree from minidom
- Migrate to Cheetah from xsl
- Preliminary MacOSX support

thanks

Matt

 

[Skip Montanaro]

Matt> Spike Asset Manager (SAM) is an open-source cross-platform
Matt> framework written in python for probing a system for components
Matt> and reporting them.

Matt,

That's a pretty generic description. Pardon my ignorance, but what's the
advantage over, for example, "rpm -aq | grep httpd"?

 

[Fredrik Lundh]

Matt> Spike Asset Manager (SAM) is an open-source cross-platform
Matt> framework written in python for probing a system for components
Matt> and reporting them.

That's a pretty generic description. Pardon my ignorance, but what's the
advantage over, for example, "rpm -aq | grep httpd"?

C:\>rpm -aq | grep httpd
'rpm' is not recognized as an internal or external command,
operable program or batch file.

(on the other hand, it doesn't find any Python installation on my machine, which
I do find a bit strange...)

</F>

 

[mh]

The idea is to have a framework to do this in a semi-crossplatform
manner. The framework could be updated to know about apt, portage
repositories as well as talk to to the windows registry.
Not everyone is running redhat

 

[mh]

Fredrik-

This is a known issue. The tool currently only looks in certain
locations or hints rather then spidering the whole hard drive (which
could take a bit of time). If you have installed in a non-standard
location (or are using a platform or version of software that hasn't
been tested against) the tool won't find the component.

One way around this is manually enter more "hints" but this doesn't
scale. I'm open to suggestions for handling this in a better way.

matt

ps-I assume you are running on windows. Where is python installed on
your machine?

 

[David Fraser]

Fredrik-

This is a known issue. The tool currently only looks in certain
locations or hints rather then spidering the whole hard drive (which
could take a bit of time). If you have installed in a non-standard
location (or are using a platform or version of software that hasn't
been tested against) the tool won't find the component.

One way around this is manually enter more "hints" but this doesn't
scale. I'm open to suggestions for handling this in a better way.

matt

ps-I assume you are running on windows. Where is python installed on
your machine?

Windows also has package management in the form of Windows Installer, it
would be better to use that on windows than simply look in locations...

David