Changes between Initial Version and Version 1 of GEC18Agenda/CodingSprintTutoring


Ignore:
Timestamp:
09/15/13 22:14:03 (11 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC18Agenda/CodingSprintTutoring

    v1 v1  
     1[[PageOutline]]
     2
     3= Coding Sprint, Experimenter Tutoring and Operations Hands-On =
     4
     5The joint software coding sprint, experimenter tutoring session, and
     6operations hands-on-with-GENI session is an informal session where
     7aggregate and tool developers will discuss software details,
     8experimenters will run though GENI tutorials or ask questions of the
     9GPO for help running experiments, and GPO operations staff will help site ops/admins folks with anything they're interested in.
     10
     11== Schedule ==
     12
     13Thursday, 1:00pm - 3:30pm
     14
     15== Session Leaders ==
     16{{{
     17#!html
     18<table  cellspacing=0  style="border:2px solid gray;">
     19<tr  style="border-style:solid; border-color:gray;">
     20<th colspan='2'  style="border:1px solid gray;">Developers</th>
     21<th  style="border:1px solid gray;">Experimenters</th>
     22<th  style="border:1px solid gray;">Operations</th>
     23</tr>
     24<tr align='center'>
     25<td> <a href="http://www.geni.net/?page_id=2353"><img src="http://www.geni.net/wp-content/uploads/2012/06/edwards_sarah.jpg" height='120px'/></a></td>
     26<td><a href="http://www.geni.net/?page_id=1931"><img src="http://www.geni.net/wp-content/uploads/2012/08/helsinger_aaron_IMG_1112_edit_170web.jpg" height='120px'/></a></td>
     27<td><a href="http://www.geni.net/?page_id=1934"><img src="http://www.geni.net/wp-content/uploads/2012/08/riga_niky_1118_edit_crop_180x176web.jpg" height='120px'/></a></td>
     28<td><a href="http://www.geni.net/?page_id=1515"><img src="http://www.geni.net/wp-content/uploads/2012/08/smift_josh_1152-web180x120.jpg" height='120px'/></a></td>
     29</tr>
     30<tr align='center'  style="border:1px solid gray;">
     31<td  style="border:1px solid gray;">Sarah Edwards<br/>GPO</td>
     32<td style="border:1px solid gray;"> Aaron Helsinger<br/>GPO</td>
     33<td style="border:1px solid gray;">Niky Riga<br/>GPO</td>
     34<td style="border:1px solid gray;">Josh Smift<br/>GPO</td>
     35</tr>
     36</table>
     37}}}
     38
     39
     40If you have any questions or comments before/after the tutorial, please find one of us!
     41
     42
     43 Developers: Sarah Edwards, Aaron Helsinger, GENI Project Office
     44
     45 Experimenters: Niky Riga, GENI Project Office
     46
     47 Operations: Josh Smift, GENI Project Office
     48
     49== Agenda / Details ==
     50
     51This software development session provides an opportunity for GENI engineers to collaborate in real time on a particular software or documentation issue. The topic will be selected well in advance of the conference, based on need and key party availability.
     52
     53The GPO will also hold a tutoring session for GENI experimenters, where experimenters can come and work on various online GENI tutorials. The list of available tutorials will be advertised in advance of the GEC. The GPO will answer questions and provide assistance. Experimenters with an idea they want to work on are encouraged to come do so in the same room, so that they can have support from the on site GPO staff and other experimenters.
     54
     55GPO operations staff will also be available to help GENI ops/admin
     56folks who'd like a hand getting set up with GENI credentials, the Omni
     57command-line tool, etc. This can be useful if you're running a GENI
     58aggregate, so you can create a slice and some slivers, and test for
     59yourself whether the aggregate manager is working like you expect. We'll also be happy to discuss any other topics of
     60interest to the ops/admin community.
     61
     62== Session Summary ==
     63
     64At the joint Coding Sprint, Experimenter Tutoring and Operations
     65Hands-On session, each of the three groups had productive discussions.
     66
     67There were several experimenters who came to the session for one on
     68one help running exercises from the tutorials. Operators worked out
     69some issues with reporting monitoring data. And developers worked through a
     70handful of issues to provide added functionality for experimenters.
     71
     72Overall, developers agreed to:
     73 - Collect ports used by GENI services, for use in testing networks for tutorials
     74 - Implement a `geni-get-info` script for each compute aggregate and substrate to provide slice and aggregate information within a node
     75 - Negotiate a new AM API v3 operational action for changing SSH keys installed on an existing node
     76 - Some conventions for tools to work with the ExoSM, an aggregate of aggregates
     77
     78=== Developer Coding Sprint Session Details ===
     79
     80Niky raised the issue of running tutorials on new networks, where
     81ports may be blocked. InstaGENI and ExoGENI agreed to provide lists of
     82the ports their services use.
     83
     84Following on from the [wiki:GEC17Agenda/UniformExperimenterExperience Uniform Experimenter Experience session], we
     85discussed what information experimenters would like to have available
     86from within a reserved compute resource. Starting with wish lists from
     87GENI Desktop, the data currently available at InstaGENI and ExoGENI,
     88and other voices in the room, we compiled a consolidated wish
     89list of information, including the local `client_id`, the
     90aggregate URN, the slice manifest, and user accounts and SSH keys. We
     91discussed how to get this data, and noted that the actual mechanism
     92would depend on the aggregate and substrate (VM vs bare metal). To hide this, we agreed to provide a
     93common script that could be available at all aggregates, whose
     94implementation would hide the aggregate specific differences. We
     95agreed to work out the implementation details in coming weeks.
     96
     97Following on from the Developer sessions, we discussed how to provide
     98`Update()`-like functionality, before a full `Update()` is
     99implemented. We agreed that aggregates could update the installed SSH
     100keys using a new operational action with
     101`PerformOperationalAction()`. The GPO agreed to propose something, and
     102has since posted a proposal on
     103[wiki:GAPI_AM_API_DRAFT#ChangeSetQ:Supportchangingusersandkeysonexistingcomputeslivers the AM API Draft wiki page]. Rob Ricci suggested that with some
     104changes, InstaGENI experimenters could make an aggregate-local LAN
     105shared, and then connect new nodes to this shared LAN. InstaGENI will
     106work to add this capability.
     107
     108We then discussed how to support the ExoGENI ExoSM in tools. The ExoSM
     109is an aggregate of multiple component managers, and this breaks some
     110assumptions in existing tools. After some discussion, the solution
     111appears to be that the sliver_id in manifest RSpecs will reflect the
     112aggregate that issued the reservation, while the component_id and
     113component_manager_id will reflect the component manager (i.e. the
     114specific ExoGENI rack). Note that tools will require some extra
     115workflow to identify the aggregate where the experimenter wants a
     116reservation, and to deal with unbound requests.