Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers

discuss AT

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers

Chronological Thread 
  • From: Peter Green <peter AT>
  • To: discuss AT
  • Subject: Re: [opennic-discuss] Policy proposal for removal of non-responding T2 servers
  • Date: Wed, 10 Oct 2012 13:19:11 +0100


My thoughts are for the first two it should be the shorter of the times you suggest and for the third the longest.

And thanks to all that offer custom code to the project! :-)

- --
Wanged from my Kaiser by a mischievous pixie!

Jeff Taylor <shdwdrgn AT> wrote:
Regarding the previous discussion about automating the removal of dead
or failing Tier-2 servers...

First off, a big thanks to Brian for getting the administrative tools
created so we can better manage the status of these servers! We now
have the tools in place to mark servers as offline or deleted, and
handle each case appropriately. Please note that if your server is
marked offline and you are able to repair it, you can contact Brian or
myself to re-enable your server on the wiki.

I am currently testing some new code which will automatically moving
failing servers to an offline status (and remove them from the zone
file). Servers that are marked offline will continue to be tested for
functionality, and could potentially be automatically changed to an
online status when they resume service. In looking through this threa d,it does not appear we ever really established a policy that I could put
into the code, so I would like to take a quick vote to see what everyone
thinks would be best...

Policies for marking servers as offline:
1) Testing fails more than (7, 14, 28) days
2) Connection fails more than (2, 3, 7, 14) days

Policies for marking an offline server as functional again:
3) Passes all tests for at least (1, 2, 7) days

My thoughts on this are that connection failures are more serious that
testing failures, and should be given a stricter criteria. Also note
that I *can* resolve the test times in hours rather than days, but at
the moment it seems best to work on a day-by-day basic to give admins
time to fix problems with their systems. Please let me know what values
you think are best for the three questions above, and I'll tally up the
results in a couple of days and start implementing the ne w automation.

You are a member of the OpenNIC Discuss list.
You may unsubscribe by emailing discuss-unsubscribe AT

-----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iQFBBAEBCAArBQJQdWe/JBxQZXRlciBHcmVlbiA8cGV0ZXJAZ3JlZW5wZXRlLmNv LnVrPgAKCRDwSqngs+9nOfdqB/0V2KhcGgAacDwIf/XU2FyJamJz/ASpbL0w6nv7 994dR1sWK6YXSwOTuNAuwsqZ+lVhOePGEuDktoZmNsrYIbML6BWoZ0yaDRUw9Fkl pwb6BFtdtnelc7IMhSgULB6mCdsS3pMaZXr7lIeuo9Bwt4sJkLouPywl8nklL4MP /Y5vidY91X3h6KXLYNGrD4puhcw1pyTIqgmy5kwHARL749/BWfGnU5CIdp+82Qhf Wct2+qEW9c6zbu/FeKuuGlW++BplLxyPJbhXRhUDSEl1RpaiNUe4dbbDVbgWa3R6 WUJrxBB7+bMrTuGIf9hUibabMlyasqvk37hOeCU+rUzoPdu8 =hSBW -----END PGP SIGNATURE-----

Archive powered by MHonArc 2.6.19.

Top of Page