| 87 | | g') New task: **Review possible tunnel through ssh (or use fo ssh to forward http port), to reuse available ssh port mapping. (who?) |
| 88 | | |
| 89 | | g!'') New task: ** Review port mapping for http, like ssh, with protoGENI, to see how it might be done (Nasir/Jim) |
| 90 | | |
| 91 | | g!''') New task: **Review need within GENI/GPO to open ports, and implications for rspec (Harry) |
| | 87 | g') New task: Review possible tunnel through ssh (or use fo ssh to forward http port), to reuse available ssh port mapping. (who?) |
| | 88 | |
| | 89 | g!'') New task: Review port mapping for http, like ssh, with protoGENI, to see how it might be done (Nasir/Jim) |
| | 90 | |
| | 91 | g!''') New task: Review need within GENI/GPO to open ports, and implications for rspec (Harry) |
| 113 | | d) How is data transfer from service to service, in a single slice, authorized? what keys/certificates/credentials are used? what is held by each service? (Martin) [in LAMP, service to service, https with LAMP cert, from LAMP CA] |
| 114 | | |
| | 113 | *topic on 4/5/12: [[BR]] |
| | 114 | d) Old UNIS vs new UNIS: [[BR]] |
| | 115 | *4/5/12 notes from Jeanne: [[BR]] |
| | 116 | What is the transition plan? Both can run in parallel until full functionality is available with new UNIS. Then turn down old UNIS. [[BR]] |
| | 117 | Local vs. global UNIS hierarchy: Will new UNIS have local and global configuration? Yes, probably not by GEC14. [[BR]] |
| 141 | | i) Task: Need help with final formulation of MDOD (Ezra?) |
| 142 | | |
| 143 | | j) Task: Define view of user workspace service (Jeanne, Matt, Harry, Jim, Martin, Niky) |
| 144 | | [Jeanne to add security policy into view] |
| | 144 | i) Task: Need help with final formulation of MDOD (Ezra?) (Shu from GIMI) |
| | 145 | |
| | 146 | j) Task: Define view of user workspace service (Jeanne, Matt, Harry, Jim, Martin, Niky) [[BR]] |
| | 147 | [Jeanne to add security policy into view] [[BR]] |
| | 148 | |
| | 149 | *topic on 4/5/12: [[BR]] |
| | 150 | j') Use of GUSH: [[BR]] |
| | 151 | *4/5/12 notes from Jeanne: [[BR]] |
| | 152 | What does Gush provide vs. Flack? Why would user use Gush? [[BR]] |
| | 153 | Working with VMs. According to Vic, Jeannie A. says Gush will work with anything that allows SSH. [[BR]] |
| | 154 | Jeanne O. has experienced some issues with VMs in Gush. Investigate further. [[BR]] |
| | 155 | Issues with hostnames? Need to investigate this further. [[BR]] |
| | 156 | Harry: Suggest Jeanne talk with Luisa about Gush information. She has worked with it a lot. [[BR]] |
| | 157 | Jim asks Martin: How does Gush integrate with UNIS? [[BR]] |
| | 158 | Discussion of using UNIS to store/access information about the slices for the experiment rather than passing around rspecs. [[BR]] |
| | 159 | How do we keep this UNIS information up-to-date? [[BR]] |
| | 160 | Guilherme suggests things that are outside of slice introspection, user needs to push to UNIS. [[BR]] |
| | 161 | What types of changes can we make to the slice in Gush/Omni/other that I&M and others need to discover from UNIS? [[BR]] |
| | 162 | Task: Things to investigate regarding Gush (Jeanne will report next week): [[BR]] |
| | 163 | 1. Tridentcom paper says gush has ability to add and remove nodes from a slice. How is this done? Under what circumstances does this work? [GENI AM API does not support updateSliver] [[BR]] |
| | 164 | 2. How does Gush work with protogeni VMs? [[BR]] |
| | 165 | |
| 231 | | **Concern: incompatible with earlier UNIS, which will still be required (see 9) below. |
| 232 | | |
| 233 | | e) Later: Extend to gathering data from an application |
| 234 | | |
| 235 | | f) Task: Prototype soon (Guilherme) |
| 236 | | |
| 237 | | - Need baseline configuration ASAP |
| | 252 | e') Concern: new UNIS incompatible with earlier UNIS, which will still be required (see 9) below. |
| | 253 | |
| | 254 | f) Later: Extend to gathering data from an application |
| | 255 | |
| | 256 | g) Task: Prototype soon (Guilherme) |
| | 257 | |
| | 258 | h) Need baseline configuration ASAP When? |
| 256 | | == 9) First configuration, follows p15 Operator A slice, to collect network measurements, like LAMP project: == |
| 257 | | |
| 258 | | a) Start: each node on a server, with an available public IP address (single aggregate or multiple aggregates) |
| 259 | | |
| 260 | | a') Second: all nodes on VMs, or all nodes on VMs except common node on server |
| | 277 | == 9) First configuration, to collect network measurements == |
| | 278 | |
| | 279 | a) follows p15 Operator A slice, like LAMP project. |
| | 280 | |
| | 281 | a') for GEC14, consider: use LAMP code with perhaps minor modifications |
| | 282 | |
| | 283 | a'') Start: each node on a server, with an available public IP address (single aggregate or multiple aggregates) |
| | 284 | |
| | 285 | a''') Second: all nodes on VMs, or all nodes on VMs except common node on server |
| 280 | | k) Extension: pull data from one slice to another, as shown in p15 from Operator A to Operator B; authorize using GENI credentials |
| 281 | | |
| 282 | | l) Provide regression tests of various configurations, features, etc., driven by scripts |
| | 305 | k) Extension: pull data from one slice to another, as shown in p15 from Operator A to Operator B; authorize using GENI credentials; how is this done? |
| | 306 | |
| | 307 | l) Provide regression tests of various configurations, features, etc., driven by scripts (Jeanne) |
| 288 | | == 10) Second configuration to support basic host monitoring using BLiPP, like p15 Experimenter C slice What this means: no SNMP daemon == |
| 289 | | |
| 290 | | **Concern: Per 7) above, still defining intial configuration; need firm plan to meet GEC14 goals; or do we start with earlier INSTOOLS code? |
| 291 | | |
| 292 | | a) Introduces push of data to common node; what protocol? http? XSP? (is this GENI Event Messaging Service?) |
| | 313 | == 10) Second configuration to support basic host monitoring == |
| | 314 | |
| | 315 | a) follows p15 Experimenter C slice |
| | 316 | |
| | 317 | a') for GEC14, need firm plan from 7) ASAP |
| | 318 | |
| | 319 | a'') Introduces push of data to common node; what protocol? http? XSP? (is this GENI Event Messaging Service?) |
| 305 | | a) Code on IU github |
| 306 | | |
| 307 | | Good: all relevant code appears to be here, including Kentuck code |
| 308 | | |
| 309 | | b) Jira |
| 310 | | |
| 311 | | Good: being used by IU to track project |
| 312 | | |
| 313 | | **Concern: Kentucky effort not reflected here |
| 314 | | |
| 315 | | c) GENI trac for GEMINI |
| 316 | | |
| 317 | | Include TopicsTasksIssues |
| 318 | | |
| 319 | | Include drawings |
| | 332 | a) Code on IU github Good: all relevant code appears to be here, including Kentuck code |
| | 333 | |
| | 334 | b) Jira Good: being used by IU to track project Concern: Kentucky effort not reflected here |
| | 335 | |
| | 336 | c) GENI trac for GEMINI Include TopicsTasksIssues Include drawings |
