more code to come...
Duncan McGreggor
A hell project I have been working on has finished. Now that I've
started working for Zenoss, I should have some sanity and stability in
my life :-) Right now I'm in Annapolis, MD working with Erik Dahl and
Eric Newton to get up to speed on Zenoss monitoring. I've added some
nice little features (including primitive network visualization support
using graphviz), but mostly learning tons about the system.
Before I left CO for this trip, I wrote some demo code for Nagios
plugins in Zenoss that I took from pymon. It was really good for me to
look over the that part of the pymon code base (ping monitor,
essentially). I've since been thinking about the efficiency improvements
I can make in it and am excited to have my weekends free to work on it.
However, I've also been setting time aside for contributing to twisted
python, so I will need to juggle that, too :-)
I'm trying to get public svn access setup for pymon so folks can start
using and contributing more easily. I'm considering using the new google
project hosting for this... we'll see.
Expect another update in a week or two, accompanied with new code :-)
d
Duncan McGreggor
> I'm trying to get public svn access setup for pymon so folks can start
> using and contributing more easily. I'm considering using the new google
> project hosting for this... we'll see.
At long last, we are approaching a secure solution for svn public access
-- Allan Baily, thanks for facilitating this!
The project is live at the new google code hosting site:
http://code.google.com/p/pymon/
I need to figure out if there's a way I can preserve version history
(importing a dump or somesuch). I will probably just merge the current
branch to trunk and then import that.
I've not dug too deeply, so I'm not sure what it takes to check code out
yet. Anonymous (or google account) access should work. There are
instructions on the site.
Email the list with any questions...
Thanks,
d
Duncan McGreggor
> Duncan McGreggor wrote:
>
>> I'm trying to get public svn access setup for pymon so folks can start
>> using and contributing more easily. I'm considering using the new google
>> project hosting for this... we'll see.
>
> At long last, we are approaching a secure solution for svn public access
> -- Allan Baily, thanks for facilitating this!
Doh! I mean "Bailey" (sorry Allan!)
Duncan McGreggor
>> I'm trying to get public svn access setup for pymon so folks can start
>> using and contributing more easily. I'm considering using the new google
>> project hosting for this... we'll see.
>
> I need to figure out if there's a way I can preserve version history
> (importing a dump or somesuch).
Okay, this support is forth-coming from google:
http://tinyurl.com/ptoyu
http://tinyurl.com/pgvqb
(links are to google groups). As soon as they add this, I will import a
pymon dump and we should be in business.
d
Duncan McGreggor
>> I need to figure out if there's a way I can preserve version history
>> (importing a dump or somesuch).
>
> Okay, this support is forth-coming from google:
>
> http://tinyurl.com/ptoyu
> http://tinyurl.com/pgvqb
>
> (links are to google groups). As soon as they add this, I will import a
> pymon dump and we should be in business.
I've had a change of heart on this. Turns out there's a quota on the
google code hosted projects, and there's a bunch of stuff in trunk that
doesn't need to be there for operational code (image files, etc.)
So here's what I have done:
1) Merged branch to trunk
2) Moved non-essential files out of trunk
3) Updated everything, make a copy of trunk, and removed all the svn files
4) Checked out the new, empty pymon from google
5) Dumped all the current code in the new co, added it, and committed
You can see it here (and see the instructions for checkout from google):
http://code.google.com/p/pymon/source
Keep in mind, I've merged the unstable branch to trunk and am now
working in trunk exclusively for now. This means that the code is not
usable right now, unless you are a developer :-)
As a reminder, the following are part of this work in progress:
* distributed pymon instances
* unit tests
* significant code clean ups
Once that's done, I'll be working from branches again.
d