[hobbit] New enable/disable tool ready for testing

[kevin hanrahan]

OK, I installed the new patch without any problems but I get odd results
when trying to use it. Using it from the Info page:
	Microsoft IE - "A runtime error has occurred. Line 267 - Object
expected
		selecting a different server produces a different line
number but the same error

	Firefox Mozilla - clicking on the disable button does absolutely
nothing

>From the Enable/Disable page:
	Seems to work fine
	The history keeps a record of who disabled and why


Kevin

 

-----Original Message-----
From: Henrik Stoerner [mailto:henrik at hswn.dk] 
Sent: Saturday, April 16, 2005 2:26 PM
To: hobbit at hswn.dk
Subject: Re: [hobbit] New enable/disable tool ready for testing
Importance: Low

OK, it seemed like most of you liked this new feature, but all of you
still wanted a way of disabling stuff on many hosts at once. So I've
been busy adding - essentially creating a Hobbit-version of the full
maint.pl script.

The result is an updated maintenance-feature patch, available as always
from http://www.hswn.dk/beta/maintenance-feature-v2.patch

This is against the 4.0.2 release, like the first version of the patch.

The patch implements the same feature as the first version - you can
disable tests for a single host from the "info" page - but it adds an
extra script "hobbit-enadis.cgi" that takes over from the maint.pl
script. hobbit-enadis.cgi displays an administration page very much like
the maint.pl one; I've unashamedly stolen Tom's JavaScript code and used
it in my implementation. (I hope he doesn't mind - I'll ask for his
permission). However, to better cope with the enormous host-list I've
added the ability to filter hosts using three regular expressions -
against the hostname, the pagename of the host, and the IP address. That
makes it slightly more usable to me...


And:

On Thu, Apr 14, 2005 at 10:35:44AM -0400, Tom Georgoulias wrote:
> 
> 2.  I found it confusing to have both the "disable now" and "schedule 
> disable" buttons right next to each other, and the cause field over 
> the schedule disable.

This has been fixed. I think the current display is very intuitive.


> I want to log a cause for every disable/enable, scheduled or  
> immediate.

This is now forced via some Javascript validation, which also makes sure
you don't hit the "Apply" button without selecting hosts, tests,
entering a valid duration etc.


Regards,
Henrik

To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe at hswn.dk