50 likes | 199 Views
Current GEMINI use of instrumentize script to initialize & configure services. Hussam Nasir University of Kentucky. GEMINI Configuration and Initialization. GEMINI requires RSPEC extensions: http :// groups.geni.net/geni/wiki/GEMINIIntegrationTasks# RSpecExtensions
E N D
Current GEMINI use of instrumentizescript to initialize & configure services Hussam Nasir University of Kentucky
GEMINI Configuration and Initialization • GEMINI requires RSPEC extensions: • http://groups.geni.net/geni/wiki/GEMINIIntegrationTasks#RSpecExtensions • The RSPEC extensions specify: • The Nodes to monitor (measurement points (MP) nodes) • For each MP Node GEMINI extension attributes defines which services (active or passive) to install and enable • The (Global) Node that does the monitoring, data collection, and rendering. It also acts a gateway to the MP nodes • For each GN Node, GEMINI extension attributes define which AMs nodes to monitor. • Because the GN serves both as a gateway to reach MP nodes, and as a data collection point, we initialize the GN in two phases: • Initialize access to MP nodes: • Sets up basic ssh access to the MP Nodes via the GN Node (accessible viathe GENIDesktop) • Initialize I&M code and services: • Install and configure passive and active data/stats collection
GEMINI Key Components • Key components of GEMINI • the GeniDesktopParser – parses the slice configuration (e.g., the RSPEC) • UNIS – stores the current configuration and status of the slice • Parser talks to the AMs , SAs and CH to obtain user information , slice information and topology information for the slice. It makes this information available to various GEMINI Services and the GeniDesktop • UNIS initially gets information from the Parser, but then interacts with GEMINI Services to keep track of, and manage, their configuration. It provides a “live” view of the slice configuration that GEMINI services can contact to discover what to do and how to communicate with other GEMINI services. Used to start/stop GEMINI services.
Known (Remaining) Challenges • Need to test using big multi-aggregate experiments (withinProtogeni) • Improve scripts efficiency by parallelizing the install/configure process when using multi-aggregate experiments. • Test using credentials from non-protogeni Control Frameworks like planetlab , Portal CH etc. • Add support for more Oses. • Harden the current implementation and improve status reporting while scripts are running. • Update the parser code when there is new information required by the monitoring services or when the manifest/rspec format changes.