Aggregate Status

[Ben Newton]

I am working to create education modules for inexperienced students to get hands-on experience with GENI and networking analysis tools.  Unfortunately one of the most difficult and timely tasks of each module is just getting resources allocated, and ready to use.  

One issue seems to be that some aggregates currently work better than others for our modules.  instageni.illinois, for example, requires a lengthy amount of time for DNS updates to propagate and make the nodes usable.  In Flack, I've also had a "Problem creating on " instageni.ku.gpeni.net and missouri.   Other issues have been seen on other aggregates as well.  

My question:  Is there a list somewhere of which aggregates are currently the most reliable?   I assume this list will change over time, so it would be nice if we had a central list which could be updated, and my modules could reference and link to.  

If not, is there a subset of aggregates you would suggest I have students pull resources from, to avoid most of these issues?

Thanks,

  Ben Newton  

[Niky Riga]

Hi Ben,

I know that this is not a perfect answer, but Brecht has put together a great tool for monitoring
AM status that gives you a quick visualization of what currently works, what doesn't and it keep
history per AM to see how frequent failures are:
http://monitor.ilabt.iminds.be/scenarios.php?filter=international

I don't know exactly what test is being performed to declare success or failure, Brecht can probably
provide some details, but it might be a start for what you are looking for.

Cheers,
Niky

Ben Newton

June 17, 2014 at 11:09 AM

--
GENI Users is a community supported mailing list, so please help by responding to questions you know the answer to.
 
If this is your first time posting a question to this list, please review http://groups.geni.net/geni/wiki/GENIExperimenter/CommunityMailingList
---
You received this message because you are subscribed to the Google Groups "GENI Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geni-users+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Brecht Vermeulen]

http://monitor.ilabt.iminds.be/scenarios.php?filter=international

I don't know exactly what test is being performed to declare success or failure, Brecht can probably
provide some details, but it might be a start for what you are looking for.

we (it's not me, but our team who has developed this) actually do full login tests, this means:
- testing getversion
- creating a sliver (1 node with default image)
- waiting till the sliver is up and running
- doing a real ssh login test and "ls && uname /"

(you see all the logs if you click 'log')

The columns mean the following:
- last test duration: how long it took till actual ssh login
- last partial success: if all the AM calls were succesful or not
- last full success: if the ssh login succeeded or not
- time since last failure: we do these tests two times per day, and this is how many days it was since last failure of the test
- last log: detailed log of all calls of last test
- history: overview of all tests over time



Brecht

[Ben Newton]

Thanks!  This is helpful.  

Ben