| 1 | [[PageOutline]]
|
|---|
| 2 |
|
|---|
| 3 | = GEMINI Topics, Issues and Tasks =
|
|---|
| 4 |
|
|---|
| 5 | Notes and tasks from 3/22/12 GEMINI status call: [[BR]]
|
|---|
| 6 | - Additions and corrections after call on 3/27/12 with Martin: [[BR]]
|
|---|
| 7 | - Additions and corrections after team call on 3/29/12, and call on 3/30/12 with Jim: [[BR]]
|
|---|
| 8 | - Additions and changes after call with Martin and Jim on 4/4/12: [[BR]]
|
|---|
| 9 | - Addtions and changes after call with Jim and Charles on 4/17/12: [[BR]]
|
|---|
| 10 | - Additions and changes after call with Martin on 4/18/12: [[BR]]
|
|---|
| 11 | - Additions and changes after team call 4/19/12: (sections are rearranged) [[BR]]
|
|---|
| 12 | - Additions and changes after team call 4/26/12:
|
|---|
| 13 | - Additions and changes after team call 5/3/12:
|
|---|
| 14 |
|
|---|
| 15 | * 4/5/12 topics : [[BR]]
|
|---|
| 16 | 2d) ABAC [[BR]]
|
|---|
| 17 | 4d) Old UNIS vs new UNIS [[BR]]
|
|---|
| 18 | 5j') Use of Gush [[BR]]
|
|---|
| 19 |
|
|---|
| 20 | + 4/12/12 topics suggested by Harry: [[BR]]
|
|---|
| 21 | 3g) review access to http on VM (Hussam+) [[BR]]
|
|---|
| 22 | 5i) who will help formulate final MDOD schema? [[BR]]
|
|---|
| 23 | 5j') report on Gush (Jeanne) [[BR]]
|
|---|
| 24 | 7h) review current status of baseline configuration to gather host metrics (Guilherme, and all) [[BR]]
|
|---|
| 25 | 8) agree on steps towards GEMINI tutorials at GEC14 (all) [[BR]]
|
|---|
| 26 | 9) agree on configuration to collect network measurements (all) [[BR]]
|
|---|
| 27 | 9l) review preliminary test plan for colelcting network measurements (Jeanne) [[BR]]
|
|---|
| 28 |
|
|---|
| 29 | + 4/19/12 topics suggested by Harry: [[BR]]
|
|---|
| 30 | 3g) review access to http on VM (Hussam+) [[BR]]
|
|---|
| 31 | 4d) Old UNIS vs new UNIS: understand transition plan (?) [[BR]]
|
|---|
| 32 | 5i) who will help formulate final MDOD schema? (Martin on4/18: Ezra and Omer) [[BR]]
|
|---|
| 33 | 5j') report on Gush (Jeanne) (delayed) [[BR]]
|
|---|
| 34 | 6d) provide a more complete view of GEMINI portal service (Jim, Charles on 4/18/12) [[BR]]
|
|---|
| 35 | 7h) review current status of baseline configuration to gather host metrics (Guilherme, and all) [[BR]]
|
|---|
| 36 | 8) agree on steps towards GEMINI tutorials at GEC14 (all) [[BR]]
|
|---|
| 37 | 9) agree on configuration to make active network measurements (all) [[BR]]
|
|---|
| 38 | 9l) review updated test plan for making active network measurements (Jeanne) [[BR]]
|
|---|
| 39 |
|
|---|
| 40 | + 4/26/12 topics suggested by Harry: [[BR]]
|
|---|
| 41 | 3g) review access to http on VM (Hussam+) [[BR]]
|
|---|
| 42 | 5j') report on Gush (Jeanne) (delayed) [[BR]]
|
|---|
| 43 | 6d) provide a more complete view of GEMINI portal service (Jim, Charles on 4/18/12) [[BR]]
|
|---|
| 44 | 7l) review updated test plan for making active network measurements (Jeanne) [[BR]]
|
|---|
| 45 | 8a) review current status of baseline configuration to gather host metrics (Guilherme, and all) [[BR]]
|
|---|
| 46 | 9) agree on steps towards GEMINI tutorials at GEC14 (all) [[BR]]
|
|---|
| 47 | 9a) agree on plan to coordinate configurations to make active network measurements and to collect basic host metrics in one slice (all) [[BR]]
|
|---|
| 48 | 9d) agree on schedule [[BR]]
|
|---|
| 49 |
|
|---|
| 50 | + 5/3/12 topics suggested by Harry: [[BR]]
|
|---|
| 51 | 5j') report on Gush (Jeanne) (delayed) [[BR]]
|
|---|
| 52 | 6d) provide a more complete view of GEMINI portal service (Jim, Charles on 4/18/12) [[BR]]
|
|---|
| 53 | 7l) review updated test plan for making active network measurements (Jeanne) [[BR]]
|
|---|
| 54 | 8a) review current status of baseline configuration to gather host metrics (Guilherme, and all) [[BR]]
|
|---|
| 55 | 9a) agree on plan to coordinate configurations to make active network measurements and to collect basic host metrics in one slice (all) [[BR]]
|
|---|
| 56 |
|
|---|
| 57 | + 5/9/12 design review topics suggested by Harry: [[BR]]
|
|---|
| 58 | 2d) need a drawing and technical review of using ABAC for AA (Guilherme) [[BR]]
|
|---|
| 59 | 6d) provide a more complete view of GEMINI portal service (Jim, Charles on 4/18/12) [[BR]]
|
|---|
| 60 | 7) review current status of baseline configuration to make active network measurements (Guilherme, and all) [[BR]]
|
|---|
| 61 | 7m) formulate tutorial for users at GEC14. [[BR]]
|
|---|
| 62 | 8a) review current status of baseline configuration to gather host metrics (Guilherme, and all) [[BR]]
|
|---|
| 63 | 8a''') need to add libvert to InstaGENI rack; is this OK? Martin to provide description.[[BR]]
|
|---|
| 64 | 9j) Formulate tutorial for users at GEC14.[[BR]]
|
|---|
| 65 | 9a) agree on plan to coordinate configurations to make active network measurements and to collect basic host metrics in one slice (all) [[BR]]
|
|---|
| 66 | 9e) need to agree on schedule for GEC14 tools:[[BR]]
|
|---|
| 67 |
|
|---|
| 68 | == 1) Authentication and authorization: multiple actor options: ==
|
|---|
| 69 |
|
|---|
| 70 | a) tool (outside slice) to !AggMgr srvc; AM API; XMl-RPC + ssl [protoGENI cert + GENI credential]
|
|---|
| 71 |
|
|---|
| 72 | b) tool (outside slice) to host (Slice A); ssh, scp [private/public keys]
|
|---|
| 73 |
|
|---|
| 74 | c) tool (outside slice) to I&M srvc (Slice A); http(s) [in LAMP, browser to GUI, https with protoGENI cert] [can private/public keys be used for access to a GUI?] [in OMF, signed messages using private/public keys; more details?]
|
|---|
| 75 |
|
|---|
| 76 | d) I&M srvc (Slice A) to I&M srvc (Slice A); http(s) [in LAMP, service to service, https with LAMP cert, from LAMP CA] [in GIMI/OML, not using http; what is done there?]
|
|---|
| 77 |
|
|---|
| 78 | e) I&M srvc (Slice A) to I&M srvc (Slice B); http(s) [in European perfSONAR, SOAP interface with security tokens] [can delegated GENI credentials be used?] [can credentials based on ABAC be used?]
|
|---|
| 79 |
|
|---|
| 80 | f) I&M srvc (Slice A) to UNIS srvc; http(s) [in LAMP, service to UNIS, https with protoGENI cert]
|
|---|
| 81 |
|
|---|
| 82 | g) tool (outside slice) to iRODS archive srvc; what is interface to iRODS? ftp(s)? can it be http(s)? how is authentication/authorization handled? [need info from Shu] Note; iRODS review call on 4/12, 9:30am.
|
|---|
| 83 |
|
|---|
| 84 | h) option: I&M srvc (Slice A) to iRODS archive srvc; is there any way to move data from MC direct to iRODS? perhaps mount iRODS on node with MC? [need info from Shu]
|
|---|
| 85 |
|
|---|
| 86 |
|
|---|
| 87 |
|
|---|
| 88 |
|
|---|
| 89 | == 2) Authentication and authorization: multiple methods: ==
|
|---|
| 90 |
|
|---|
| 91 | a) [for ssh, ssl, etc.] private/public keys
|
|---|
| 92 |
|
|---|
| 93 | a') [in OMF] signed messages using private/public keys
|
|---|
| 94 |
|
|---|
| 95 | b) user certificates
|
|---|
| 96 |
|
|---|
| 97 | c) GENI credentials (user and slice)
|
|---|
| 98 |
|
|---|
| 99 | c') [in IMF, GENI credentials included with XML messages, for authorization? how? reuse?]
|
|---|
| 100 |
|
|---|
| 101 | d) ABAC [Harry: GPO believes that ABAC may eventually be used for resource assignment, but not soon] [What code is available from ISI? Jim is checking with Teb Faber; waiting for a response]
|
|---|
| 102 |
|
|---|
| 103 | ABAC references: [[BR]]
|
|---|
| 104 | Deter web site: http://abac.deterlab.net/ [[BR]]
|
|---|
| 105 | Authorization storyboard from Jeff Chase: http://groups.geni.net/geni/wiki/AuthStoryBoard [[BR]]
|
|---|
| 106 | Slides on credential store from Jeff Chase: http://groups.geni.net/geni/attachment/wiki/AuthStoryBoard/certstore.ppt [[BR]]
|
|---|
| 107 | Slides on future of authorization in GENI from Tom Mitchell: http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/Authorization/AuthFuture.pdf [note options without and with credential store] [[BR]]
|
|---|
| 108 | Summary of GENI authorization discussion at GEC13 (and before): http://groups.geni.net/geni/wiki/GeniAuthorization [[BR]]
|
|---|
| 109 |
|
|---|
| 110 | *4/5/12 notes from Jeanne: [[BR]]
|
|---|
| 111 | Jim got code from Ted Faber. Looking through it. Looking at example code. [[BR]]
|
|---|
| 112 | ABAC is not currently implemented (at ISI?) as a service. This needs to be done. Ted thinks this should be trivial. Looks like (via papers) ORCA has implemented as a server (ORCA Pod?) with RESTful interface. [[BR]]
|
|---|
| 113 | Jim contacted Jeff Chase to get code. Making some progress, still some unknowns. [[BR]]
|
|---|
| 114 | Martin: Thinks we perhaps can use UNIS for source of constraints or reference (URL) to constraints. Use libabac to prove the chain of assertions. [[BR]]
|
|---|
| 115 | All agree that we should have a central location for rules. [[BR]]
|
|---|
| 116 | Guilherme: Dont want the rules to be exposed. [[BR]]
|
|---|
| 117 | Is the proving done at the service or at the authenticating application? [[BR]]
|
|---|
| 118 | Task: Harry suggests drawing up a proposal for using ABAC. Jim: Jim and Martin to discuss, learn more, and come up with a proposal. [[BR]]
|
|---|
| 119 |
|
|---|
| 120 | 5/2: Guilherme looked at ABAC code for AA
|
|---|
| 121 | - on 5/2: need a drawing and technical reivew at design review
|
|---|
| 122 |
|
|---|
| 123 | == 3) Target protoGENI environments: ==
|
|---|
| 124 |
|
|---|
| 125 | a) servers: relatively few; public IP available
|
|---|
| 126 |
|
|---|
| 127 | b) VMs: OpenVZ; expect move to LXC; internal to an aggregate, private host name, private IP addresses, need more details
|
|---|
| 128 |
|
|---|
| 129 | c) To date, all LAMP/periscope has been on servers
|
|---|
| 130 |
|
|---|
| 131 | c') Task: try to run all LAMP nodes (or just measurement nodes) on VMs (Matt Jaffe)
|
|---|
| 132 |
|
|---|
| 133 | d) To date, all INSTOOLS has been with MC on server, and MPs on VMs
|
|---|
| 134 |
|
|---|
| 135 | e) Task: Try to run INSTOOLS MC in a VM; Nasir on 3/30: still runs, although might need some small code changes; but would need to open http port, perhaps with extension to rspec; need to discuss with protoGENI (Jonathan Deurig) about adding to mapping agent; Jim had discussed with Jonathan and Rob earlier, quite doable, but would have to restart mapping agent; perhaps could "piggyback" on opening ssh port?
|
|---|
| 136 |
|
|---|
| 137 | f) Task: can ssh into public host name (or public IP) , with special 5+ digit port number (from manifest) from port map
|
|---|
| 138 |
|
|---|
| 139 | g) Task: (see e) above) how to access http interface? tunnel through ssh? port map, like ssh? perhaps could "piggyback" on opening ssh port? setup a separate proxy? [[BR]]
|
|---|
| 140 |
|
|---|
| 141 | - See [http://groups.geni.net/geni/wiki/RspecExtensionProposal_PortMapping Port mapping proposal from Hussam] [[BR]]
|
|---|
| 142 | - Jim on 4/12: Talked with Rob Ricci. He is willing to work on it, since many needs to proxy to VMs. (In INSTOOLS, used VNC) [[BR]]
|
|---|
| 143 | - On 4/12: protoGENI considering using OPS server to provide persistent proxy. [[BR]]
|
|---|
| 144 | - Jim on 4/19: Long term solution: Gary Wong at Utah is considering a proxy service per testbed, advertised in manifest. [[BR]]
|
|---|
| 145 | - Jim of 4/19: Short term solution: user can get to http port via ssh and port forwarding; Hussam has script. [[BR]]
|
|---|
| 146 | - On 4/26: short term solution: for 1st, put MC only on a server; concern: some servers have limited capacity. [[BR]]
|
|---|
| 147 | - On 4/26: long term solution: wait for Utah proxy service per testbed; when? perhaps soon?[[BR]]
|
|---|
| 148 |
|
|---|
| 149 | h) Task: what about vnc tunnels? how were they done in INSTOOLS? which port on host? (who?)
|
|---|
| 150 |
|
|---|
| 151 | i) Task: what happens when VMs are on one aggregate? can reach each other via private IP addresses
|
|---|
| 152 |
|
|---|
| 153 | i') Task: what happens when VMs are on multiple aggregates? (who?)
|
|---|
| 154 |
|
|---|
| 155 |
|
|---|
| 156 |
|
|---|
| 157 |
|
|---|
| 158 |
|
|---|
| 159 |
|
|---|
| 160 | == 4) UNIS service ==
|
|---|
| 161 |
|
|---|
| 162 | Per call with Martin on 3/27/12:
|
|---|
| 163 |
|
|---|
| 164 | a) Question: In LAMP, is there a local UNIS, or not??
|
|---|
| 165 | (Martin on 3/27:) Not yet; needs to be, with push from local UNIS to global UNIS.
|
|---|
| 166 |
|
|---|
| 167 | b) How does UNIS authenticate/authorize when receiving data?
|
|---|
| 168 | (Martin on 3/27:) [in LAMP, service to UNIS, https with protoGENI cert]
|
|---|
| 169 |
|
|---|
| 170 | c) Question: Use web interface on common node to configure services, tests; how does this push config to UNIS? What authentication/authorization steps are included?
|
|---|
| 171 |
|
|---|
| 172 | d) Old UNIS vs new UNIS: [[BR]]
|
|---|
| 173 |
|
|---|
| 174 | 4/5/12 notes from Jeanne: What is the transition plan?
|
|---|
| 175 | Both can run in parallel until full functionality is available with new UNIS. Then turn down old UNIS. [[BR]]
|
|---|
| 176 | Local vs. global UNIS hierarchy: Will new UNIS have local and global configuration? Yes, probably not by GEC14. [[BR]]
|
|---|
| 177 | 4/18/12 notes from Harry: Martin indicates that Old UNIS and New UNIS can run in parallel, and in sync, until Old UNIS is eventually turned down. [[BR]]
|
|---|
| 178 | Guilherme on 4/19: Expect Old UNIS and New UNIS to contain smae information, but no 1:1 mapping [[BR]]
|
|---|
| 179 | Guilherme on 4/19: Could write a wrapper for perfSONAR services to talk with New UNIS, but significant effort. [[BR]]
|
|---|
| 180 |
|
|---|
| 181 | == 5) User workspace service ==
|
|---|
| 182 |
|
|---|
| 183 | Current view: (Harry)
|
|---|
| 184 |
|
|---|
| 185 | a) Persistent Linux environment, with file system, key/certificate/credential store, dedicated to the user; also rspec store, etc.
|
|---|
| 186 |
|
|---|
| 187 | b) Place for tools, e.g., Gush and OMNI, and EC, and scripts; can easily call one another; not in slice; could deal with multiple slices
|
|---|
| 188 |
|
|---|
| 189 | c) Place for "portals"; but what are they? (see below)
|
|---|
| 190 |
|
|---|
| 191 | d) Task: Setup user workspace using server (or VM) in BBN Cambridge lab; begin to include tools, etc . (Jeanne)
|
|---|
| 192 | - On 3/30/12: Done on VM in BBN Cambridge lab, ubuntu 10.04, internal to BBN.
|
|---|
| 193 | - **Next: external to BBN
|
|---|
| 194 |
|
|---|
| 195 | e) Task: Consider VM to distribute user workspace (Matt); e.g, ubuntu on virtual box [similar to what has been done at GEC tutorials]
|
|---|
| 196 |
|
|---|
| 197 | f) Task: What is required to secure keys/certificates/credentials? passphrase? other? [Per Tom Mitchell, OMNI does not require passphrase, but FLACK does currently require passpharase] [Per Jim protoGENI cert does require passphrase] [Vic to check with Steve Schwab; need to balance security and ability ot use scripts.]
|
|---|
| 198 |
|
|---|
| 199 | g) Start with CNRI: Directory Archive (DA) service, which can push data to DOA service, using OI service [[BR]]
|
|---|
| 200 | - Then replace DOA with iRODS [[BR]]
|
|---|
| 201 | - Have iRODS at IU for NetKarma; Jim and Wesley talking with Ilia and Shu [[BR]]
|
|---|
| 202 | - Or, do we use IRODS client to push/pull date to/from IRODS? [[BR]]
|
|---|
| 203 | - on 5/2: now assuming IRODS client to push/pull date to/from IRODS
|
|---|
| 204 |
|
|---|
| 205 | h) Include MDOD creator/editor (CNRI, GPO)
|
|---|
| 206 |
|
|---|
| 207 | i) Task: Need help with final formulation of MDOD (Ezra and Omer from GEMINI) (Shu from GIMI)
|
|---|
| 208 |
|
|---|
| 209 | j) Task: Define view of user workspace service (Jeanne, Matt, Harry, Jim, Martin, Niky) [[BR]]
|
|---|
| 210 | [Jeanne to add security policy into view] [[BR]]
|
|---|
| 211 |
|
|---|
| 212 | j') Use of GUSH: [[BR]]
|
|---|
| 213 | - *4/5/12 notes from Jeanne: [[BR]]
|
|---|
| 214 | - What does Gush provide vs. Flack? Why would user use Gush? [[BR]]
|
|---|
| 215 | - Working with VMs. According to Vic, Jeannie A. says Gush will work with anything that allows SSH. [[BR]]
|
|---|
| 216 | - Jeanne O. has experienced some issues with VMs in Gush. Investigate further. [[BR]]
|
|---|
| 217 | - Issues with hostnames? Need to investigate this further. [[BR]]
|
|---|
| 218 | - Harry: Suggest Jeanne talk with Luisa about Gush information. She has worked with it a lot. [[BR]]
|
|---|
| 219 | - Jim asks Martin: How does Gush integrate with UNIS? [[BR]]
|
|---|
| 220 | - Discussion of using UNIS to store/access information about the slices for the experiment rather than passing around rspecs. [[BR]]
|
|---|
| 221 | - How do we keep this UNIS information up-to-date? [[BR]]
|
|---|
| 222 | - Guilherme suggests things that are outside of slice introspection, user needs to push to UNIS. [[BR]]
|
|---|
| 223 | - 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]]
|
|---|
| 224 | - Task: Things to investigate regarding Gush (Jeanne will report next week): [[BR]]
|
|---|
| 225 | - 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]]
|
|---|
| 226 | - 2. How does Gush work with protogeni VMs? [[BR]]
|
|---|
| 227 | - 4/12: Jeanne reports: Certain commands (slice add, renew, update) apply only to PlanetLab. [[BR]]
|
|---|
| 228 | - Issue: Gush takes hostname and goes to physical node, not VMs; considering how to rectify. [[BR]]
|
|---|
| 229 | - In ORCA, this works. hostname in manifest is not the same as the hostname reported for the node. [[BR]]
|
|---|
| 230 | - 4/12: Jim asks: How would be run shell scripts on nodes? scp between nodes? [[BR]]
|
|---|
| 231 | - 4/26: Known issue: Gush does not find ssh port on VMs properly; can this be fixed soon? if not, cannot use Gush for GEC14
|
|---|
| 232 | - 4/26: Jeanne will consider using just ssh for tests, not Gush, to load code and manage processes
|
|---|
| 233 | - on 5/2: needed fix for Gush is delayed; therfore, will not use Gush for GEC14 testing; perhaps later, if can find support for Gush
|
|---|
| 234 |
|
|---|
| 235 | == 6) Portal services ==
|
|---|
| 236 |
|
|---|
| 237 | a) Option 1: "portal to UIs". [Is this close to Jim's proposal?]
|
|---|
| 238 |
|
|---|
| 239 | b) Option 2: a more complete tool for managing I&M services, as is implied in the SOW, so that it can view, orchestrate, edit MDOD, manage archiving, etc. [Is this close to Max's proposal]
|
|---|
| 240 |
|
|---|
| 241 | c) Task: understand options for authentication and authorization at a web interface. (who?)
|
|---|
| 242 |
|
|---|
| 243 | d) Task: provide a more complete view of GEMINI portal service (Jim and Charles) [[BR]]
|
|---|
| 244 |
|
|---|
| 245 | Task: Jim and Charles plan to provide in a week or two. [[BR]]
|
|---|
| 246 |
|
|---|
| 247 | Task: Charles needs to find a name for the service [[BR]]
|
|---|
| 248 |
|
|---|
| 249 | After discussion on 3/31/12 with Jim, Harry feels that this is very close to Option 1: "portal to UIs". [[BR]]
|
|---|
| 250 |
|
|---|
| 251 | Jim expects User to have a capable browser, e.g., one that runs HTML-5 [[BR]]
|
|---|
| 252 |
|
|---|
| 253 | Jim expects portal to manage windowing to various GUIs. [[BR]]
|
|---|
| 254 |
|
|---|
| 255 | Jim expect all interactions to be via browser, so there are window(s) to login to shell(s), etc. [[BR]]
|
|---|
| 256 |
|
|---|
| 257 | Jim does not specify whether browser is looking at GUI in slice, or a tool; tools are not in a specified place.
|
|---|
| 258 |
|
|---|
| 259 | Harry feels that portal and other tools are in a "user workspace", in a persistent Linux environment, with file system, key/certificate/credential store, dedicated to the user; could also have rspec store, etc. ; then, all tools have ready access to required info, and can readily call one another. [[BR]]
|
|---|
| 260 |
|
|---|
| 261 | Harry thinks of "persistent Linux environment" on infrastructure, e.g., a server under your desk or in the lab; not your laptop; Jim agrees, and has thought portal would be hosted on infrastructure at Kentucky [[BR]]
|
|---|
| 262 |
|
|---|
| 263 | Harry feels that this is just a strucutre, that there is much more work to define tools, interfaces, etc.; Jim agrees, was concerned it was the final configuration. [[BR]]
|
|---|
| 264 |
|
|---|
| 265 | Task: Harry will modify drawing to reflect discussion with Jim, and then two perspectives can be compared. [[BR]]
|
|---|
| 266 |
|
|---|
| 267 | Done on 4/4; agree that portal can be in user workspace, or somewhere else. [[BR]]
|
|---|
| 268 | See updated drawing. [[BR]]
|
|---|
| 269 |
|
|---|
| 270 | Jim and Charles on 4/17: showed early demo; portal is very thin, and runs in a server; user logs into portal with browser, typically using HTML5 that runs in browser; portal includes plugins that interface to various parts of the system, parts of slice and/or tools; tools can run in user workspace; portal remembers parameters, but is NOT persistent; common denominator is a web GUI, even when interfacing to a CLI; expect user's identity to pull credentials from store ("ABAC" approach); expect various rspecs to be stored in UNIS.
|
|---|
| 271 |
|
|---|
| 272 | Guiherme on 4/19: saw demo of portal
|
|---|
| 273 |
|
|---|
| 274 | Jim and Charles on 4/17/12: next step is to further define portal, and write it up.
|
|---|
| 275 |
|
|---|
| 276 | e) Task: Understand NICTA's iREEL portal service; is this a more complete tool for managing I&M services?
|
|---|
| 277 |
|
|---|
| 278 | - Get login, and survey (Jeanne)
|
|---|
| 279 |
|
|---|
| 280 | - Provide more info (NICTA, e.g., Christoph)
|
|---|
| 281 |
|
|---|
| 282 |
|
|---|
| 283 | == 7) Configuration 1: make active network measurements ==
|
|---|
| 284 |
|
|---|
| 285 | a) follows p15 Operator A slice, like LAMP project.
|
|---|
| 286 |
|
|---|
| 287 | a') for GEC14, consider: use LAMP code with perhaps minor modifications
|
|---|
| 288 |
|
|---|
| 289 | a!'') Start: each node on a server, with an available public IP address single aggregate or multiple aggregates
|
|---|
| 290 |
|
|---|
| 291 | a!''') Second: all nodes on VMs, or all nodes on VMs except common node on server
|
|---|
| 292 |
|
|---|
| 293 | b) One common node (e.g., node n+1) to: configure measurements, collect data, present data
|
|---|
| 294 |
|
|---|
| 295 | c) Multiple measurement nodes (e.g., nodes 1, 2, ..., n)
|
|---|
| 296 |
|
|---|
| 297 | d) Start: one slice, classic pS interface, with data pulled from measurement node, authorized with GENI credential or ?
|
|---|
| 298 |
|
|---|
| 299 | e) Global old UNIS as shown; include local UNIS on common node?
|
|---|
| 300 |
|
|---|
| 301 | f) Load software onto common node with image; as option, load package
|
|---|
| 302 |
|
|---|
| 303 | g) Load software onto measurement node with image; as option, load package after app
|
|---|
| 304 |
|
|---|
| 305 | g') Use Gush to manage processes, so that can easily switch between app and active network measurements; good for establishing continuity and available bandwidth at beginning of experiment.
|
|---|
| 306 |
|
|---|
| 307 | h) Use web interface on common node to configure services, tests, like LAMP; how does this push config to UNIS?? How do we let only user do this with keys, etc.
|
|---|
| 308 |
|
|---|
| 309 | i) Use web interface on common node to present/observe data, like LAMP How do we let only user do this with keys, etc.
|
|---|
| 310 |
|
|---|
| 311 | j) Demo all of the perfSONAR network performance tools, tests, as was done in LAMP project
|
|---|
| 312 |
|
|---|
| 313 | 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?
|
|---|
| 314 |
|
|---|
| 315 | l) Provide regression tests of various configurations, features, etc., driven by scripts (Jeanne)
|
|---|
| 316 |
|
|---|
| 317 | m) Formulate tutorial for users at GEC14. What is content of the tutorial, i.e., what are the use cases? what is different between the test plan and the tutorial?
|
|---|
| 318 |
|
|---|
| 319 | n) Coordinate tutorial content with GPO (Mark, Niky) when? starting in mid-May how?
|
|---|
| 320 |
|
|---|
| 321 |
|
|---|
| 322 |
|
|---|
| 323 | == 8) Configuration 2: gather basic host metrics ==
|
|---|
| 324 |
|
|---|
| 325 | a) follows p15 Experimenter C slice
|
|---|
| 326 |
|
|---|
| 327 | a') Need baseline configuration ASAP [[BR]]
|
|---|
| 328 | - 4/12: (Guilherme) considering overall framework, working on interfaces, considering UNIS functions and schema. [[BR]]
|
|---|
| 329 | - 4/19: (Guilherme) Need baseline config for GEC14 tutorials ASAP [[BR]]
|
|---|
| 330 | - 4/26: (Guilherme) Need baseline config for GEC14 tutorials ASAP
|
|---|
| 331 | - on 5/2: all components underway; some documentation; some timelines
|
|---|
| 332 |
|
|---|
| 333 | a!'') Need MP to gather host metrics (Guilherme)
|
|---|
| 334 | - easy for raw servers; hard for VMs
|
|---|
| 335 | - considering BLiPP (Matt) to gather all utilization metrics; how to refactor BLipp?
|
|---|
| 336 | - plan to use libvirt to gather metrics from VMs and hypervisor node
|
|---|
| 337 | - on 4/26: *** need to talk with InstaGENI to get libvert installed!
|
|---|
| 338 | - Could still use SNMP daemon from INSTOOLS to gather table info (Jim, Hussam)
|
|---|
| 339 | - Use netflow to gather flow metrics; need to be able to turn on/off since uses many resources
|
|---|
| 340 | - on 4/26: for 1st, do not include netflow, because of capacity issues
|
|---|
| 341 | - Could associate netflow with both hosts and switches.
|
|---|
| 342 |
|
|---|
| 343 | a!''') Need to define which host metrics to gather
|
|---|
| 344 | - 4/12: For those gathered by INSTOOLS, see [http://groups.geni.net/geni/attachment/wiki/GEMINI_TopicsIssuesTasks/012312_INSTOOLS_Measurements.txt list] by Hussam
|
|---|
| 345 | - Talking to Dan about use cases for gathering host metrics.
|
|---|
| 346 | - 4/19: see list on github at: [https://github.iu.edu/GEMINI/GEMINI/wikis/user-stories-for-instrumenting-an-experimenters-slice list]
|
|---|
| 347 | - 4/19: start with utilization metrics
|
|---|
| 348 | - 4/19: later, add netflow metrics
|
|---|
| 349 | - 4/26: need up-to-date list
|
|---|
| 350 | - on 5/2: need to add libvert to InstaGENI rack; is this OK? Martin to porvide description.
|
|---|
| 351 |
|
|---|
| 352 |
|
|---|
| 353 | b) MP pushes to Measurement Store (MS)
|
|---|
| 354 | - Use http? POST to port? what about authentication and authorization?
|
|---|
| 355 | - Use XSP, for streaming? Martin on4/26: working well.
|
|---|
| 356 |
|
|---|
| 357 | c) Need to realize new MS
|
|---|
| 358 | - using on SQL for data
|
|---|
| 359 | - How many options?
|
|---|
| 360 | - One per Aggregate?
|
|---|
| 361 | - Can also be arranged for publish/subscribe; how?
|
|---|
| 362 |
|
|---|
| 363 | d) Uses new UNIS
|
|---|
| 364 | - Uses RESTful interface, replaces older UNIS with SOAP interface
|
|---|
| 365 | - Allows drawing topology
|
|---|
| 366 | - Used to configure services?
|
|---|
| 367 | - Prototype underway (Ahmed)
|
|---|
| 368 |
|
|---|
| 369 | e) Need to realize MAP service
|
|---|
| 370 |
|
|---|
| 371 | - Start with modified Periscope service
|
|---|
| 372 | - Later: include druple from INSTOOLS?
|
|---|
| 373 | - Uses new MS
|
|---|
| 374 | - Uses new UNIS
|
|---|
| 375 |
|
|---|
| 376 | f) Later: Extend to gathering data from an application
|
|---|
| 377 |
|
|---|
| 378 | g) Task: Prototype soon when? (Guilherme)
|
|---|
| 379 |
|
|---|
| 380 | h) Backup option: Use what capabilities are in LAMP?
|
|---|
| 381 |
|
|---|
| 382 | i) Provide regression tests of various configurations, features, etc., driven by scripts (Jeanne)
|
|---|
| 383 |
|
|---|
| 384 | j) Formulate tutorial for users at GEC14. What is content of the tutorial, i.e., what are the use cases? what is different between the test plan and the tutorial?
|
|---|
| 385 |
|
|---|
| 386 | k) Coordinate tutorial content with GPO (Mark, Niky) when? how?
|
|---|
| 387 |
|
|---|
| 388 |
|
|---|
| 389 | == 9) Steps toward GEC14 tutorials ==
|
|---|
| 390 |
|
|---|
| 391 | a) Need plan to coordinate configurations to provide make active network measurements and to collect basic host metrics in the same slice
|
|---|
| 392 | - 4/19: For GEC13, LAMP code and INSTOOLS code were both loaded; portal was pointed to both GUIs
|
|---|
| 393 | - 4/19: Plan to load both types of code
|
|---|
| 394 | - 4/26:: plan for host monitoring to be ON by default; need to specifically enable network measurements
|
|---|
| 395 | - 4/19: Perhaps UK could work on unified deployment plan. Note: Cannot use UpdateSlice.
|
|---|
| 396 | - 4/26: Harry suggests using perfSONAR config GUI to config host measurements
|
|---|
| 397 |
|
|---|
| 398 | b) Long term strategy: unified set of tools
|
|---|
| 399 |
|
|---|
| 400 | c) Start with protoGENI tutorial? LAMP tutorial? INSTOOLS tutorial?
|
|---|
| 401 |
|
|---|
| 402 | d) Arrange user workspace (GPO, Jeanne)
|
|---|
| 403 |
|
|---|
| 404 | e) Need to agree on schedule for GEC14 tools:
|
|---|
| 405 | - Design review week of 5/7? includes arch, configuration, use cases
|
|---|
| 406 | - Development complete (freeze) on 6/15
|
|---|
| 407 | - Testing and bug fixes: +2 weeks
|
|---|
| 408 | - Prepare and test turotrial: +1 week
|
|---|
| 409 | - also INSTOOLS to GENI summer camp, 5/29 - 6/2
|
|---|
| 410 | - also INSTOOLS to TridentCom 6/15
|
|---|
| 411 |
|
|---|
| 412 |
|
|---|
| 413 |
|
|---|
| 414 | == 10) GEMINI project documentation ==
|
|---|
| 415 |
|
|---|
| 416 | a) Code on IU github Good: all relevant code appears to be here, including Kentuck code
|
|---|
| 417 |
|
|---|
| 418 | b) Jira Good: being used by IU to track project Concern: Kentucky effort not reflected here
|
|---|
| 419 |
|
|---|
| 420 | c) GENI trac for GEMINI Include TopicsTasksIssues Include drawings |
|---|
