270 likes | 456 Views
Raphael Dourado. LAMP and INSTOOLS A configuration overview. Agenda. Measurement configuration on LAMP INSTOOLS Some considerations Demonstration (Flack) Live Demo (INSTOOLS Web Portal). LAMP. A word about LAMP. How the slice is instrumentized ? (1).
E N D
Raphael Dourado LAMP and INSTOOLSA configuration overview
Agenda • Measurement configuration on LAMP • INSTOOLS • Some considerations • Demonstration (Flack) • Live Demo (INSTOOLS Web Portal)
A word about LAMP Howthesliceisinstrumentized? (1) • On the Rspec, the user chooses which nodes will be “instrumentized” with LAMP • The user also chooses one (or more) node to host the LAMP Web Portal • Using this modified Rspec, the slice is created as usual by the CMF • The slice manifest (returned by the CMF) is converted and sent to UNIS
A word about LAMP Howthesliceisinstrumentized?(2) • Throughthe LAMP Web Portal, onecanenableand configure measurementservicesonall nodes thatcomprisetheslice • The “Portal node” knows the slice’s topology by querying UNIS… • Allchangesmadeonthe Portal are sentto UNIS • All nodes pulls the configuration from UNIS(every 5 minutes) and applies the new configurations on themselves.
A word about LAMP How measurements are configured?
Considerations INSTOOLS and perfSONAR: a love story? • According to Jim Griffioen (2011): • “[...] INSTOOLS does not do well in defining standards so that other user interfaces can get access to the data” • So... • “Our goal is to use perfSONAR and/or the I&M architecture to define standard ways to access the collected data from external visualization tools.”
Considerations INSTOOLS and perfSONAR: a love story? • Some perfSONAR interoperability already exists! • Data is stored in rrd format (that can be understood by pS clients) • “We have implemented (and tested) a perfSONAR service that reads the rrd files on our MC, and, in turn, makes them available to external I&M user interfaces (e.g., existing perfSONAR tools)” • Moreover, pS also brings the ability to perform active measurements [remember that INSTOOLS performs only passive measurements...]
Considerations What exactly can INSTOOLS measure? • All these information is accessible through INSTOOLS Portal, LIVE! • The measurements are gathered via SNMP and SSH
Considerations How does INSTOOLS instrumentize the user’s slice? • 1 MC per Aggregate • Installs additional software on each node (SNMP daemon, tcpdump, netflow, ...) • Each node becomes a MP and send its data to the Aggregate’s MC Researcher
Demonstration FLACK’s “home” screen Aggregates
Demonstration Creating the slice
Demonstration Submitting the slice to be instantiated
Demonstration Each action is logged...
Demonstration Asking ProtoGENI to “instrumentize” the slice with INSTOOLS The green background meansthatthesliceisactive
Demonstration But what really happens after clicking the “Instrumentize” button? • The Component Manager returnsa Manifestinforming: • The slice’stopology • The numberofresourcesandtheircharacteristics • The original Rspecischangedby: • Adding a new sliver (usually a node) toact as the MC • Specifying a custom OS kerneltobeloadedonthe MC • Creatingallnecessary links betweenthe MC andother nodes • Addingmonitoring software toeach node oftheslice/experiment (makingthem MPs) • The modifiedRspecisthensenttothe CM, whorebuildstheslice
Demonstration A new node was automatically created by INSTOOLS: the Measurement Controller Instrumentation completed!
Demonstration But where’s the measurement data? There!
References • GRIFFIOEN, Jim. From INSTOOLS to GEMINI. GEC12 - I&M WorkingGroup, November 2011. http://groups.geni.net/geni/attachment/wiki/GEC12InstMeasWorkingSession/GEMINI_INSTOOLS.pdf • Protogeni Flack: http://www.protogeni.net/flack • Griffioen, James. Architectural Design and Specification of the INSTOOLS Measurement System. 2009. http://groups.geni.net/geni/attachment/wiki/InstrumentationTools/instools-design-doc.pdf