Monitoring Domain Interface info
================================


Goals:

Complete the infrastructure

Extend


Warren has a web service on the PMP. You just ask for a test to be done.
But it only runs it from the local machine to the server... whatever you ask for.

Envisioned: the NMDB machine will be the MDI (==ADI).
The problem with running on a remote machine: Jeff was a bit worried about bandwidth.
He hasn't coded in the ability to do third party tests.
Was a bit worried about, say, running remote tests through ssh.

Warren thinks he can fake things.



Eric would like to do:

The three of us come up with the design we actually want to do.
Decide how achievable it is.

Warren and I have some coding time. Eric has a little.



Atm pipes have:

   BWCTL (iperf wrapper) & owamp deployed on the 11 abeline nodes + hawaii.
   Code is weak on multiple domain stuff.

   They can do scheduling at both ends to make sure there is no contention.


Eric want to be able to contact the MDI with the request shcmea.
Would like the piece of software running on it to decide whether to run a test based on policy/AAA.
If it does, then it should tell the local BWCTL to run a test to the other machine, having talked to the remote MDI.

AES is the securty for BWCTL.


Take a request schema.


First: come up with a design to bounce off people.



I do a first cut at a design docuemtn. Something along the lines of the one for the request schema,
but do a hybrid requirements/design plan.

Warren: requirements are quite clear cut.

Requirements might be:
   configurable policy engine with permission based on some list of things
   

So the idea would be that we come up with a piece of software, that if you ran it in another domain that trusted each other, those domains could talk with each other.
If possible, we could get a standard out of this.



Good idea to split into two parts: requirements, and this is how we're doing it.




Two objectives:  backend stuff
		 frontend stuff




Setting up a domain:
 1st step: be an alpha customer of BWCTL & Owamp. Install them and try to use them.



There's a 12th abeline-like node at NC-state (hawaii). If we want to stay completely out of abeline, we can use that.


Todos:

Start running nodes with these tools installed. Local database to store results.

Paul: requirements and design doc for doing this.


Meeting in 1st week of february.



For implementation: use the CVS repository at piPES.
Warren will send me stuff to do with CVS.


ATMass? workshop. 
NIMI work: they have focussed from the other end. Look at them for inspiration on frontend stuff. piPES will work with them.
They are happy with us working with us on that.   psc.edu
Andy Adams, and another guy maybe Verne Packs.