Suggestion to make remote recovery easier

[Justin M. Wray]

I will look at your script as soon as I get to my desk.

As for the project, let's set it up on sourceforge and on launchad.

You want to create the projects, as you came up with the idea to start with?

As for a name, I personally donot like remote help, nor remote recover.  And Remote Assistance is taken :(

We need some good name ideas...

Thanks,
Justin M. Wray

Sent via BlackBerry by AT&T

-----Original Message-----
From: Andrew Sayers <andrew-ubuntu-devel at pileofstuff.org>

Date: Thu, 08 May 2008 01:35:50 
To:ubuntu-devel-discuss at lists.ubuntu.com
Subject: Re: Suggestion to make remote recovery easier


Okay, I've got the auction part of the dash adventure completed.  In
principle, the rest should be relatively easy.  The code isn't vastly
useful or commented so far, it's just a proof of concept really.

The script doesn't prune unlikely matches (e.g. socat+ssh when ssh is
already provided), because that doesn't work in the general case: say
there are two pipelines, a->b->c and a->c->b.  If a->b->c fails, it
could be due to a problem in a, b, c, or some interaction between the
three.  Without knowing more about the error, we can't assume that
a->c->b will fail.  Here's a rough guide to the script:

* Right now, the script reads bids from remote_help.txt, but will
  eventually take bids by polling a separate set of module scripts

* A module script is run with a to-be-decided set of command line
  arguments.  I'm currently thinking it'll be something like:

  my-module.sh --want remote-shell --remoteuser andrew \
	 --remotehost example.com

  this will have to be decided as modules are written - there'll
  doubtless be some rules, some precedents, and some totally
  protocol-specific things

* Modules that sub-contract part of the job will be assumed to handle
  subcontracts internally (it's just a matter of calling remote_help.sh
  again with the appropriate arguments)

* Every module is polled in every auction.  Inapplicable scripts will
  return no bids, bids with a variety of subcontractors will return
  multiple bids

* A bid is a line printed on standard output, of the form:

  <integer> <command line>

  The integer is the bid, the remainder of the line is a command to pass
  to /bin/sh

* The highest bidder is repeatedly run until a bidder returns
  successfully (note: currently, all bids are run)

* This would have been a lot easier if I could rely on `sort` and `head`
  existing!

How should we proceed with this?  Set up some space on Sourceforge?  Do
you have any better ideas for names than "remote help"?

	- Andrew

-- 
Ubuntu-devel-discuss mailing list
Ubuntu-devel-discuss at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss