81 | | **Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment [[BR]] |
| 81 | **Starts with INSTOOLS, which provide easy-to-use tools in GENI environment for experimenters [[BR]] |
| 82 | ++Fold features into LAMP to form GEMINI tools, and then discontinue [[BR]] |
| 83 | |
| 84 | Focus: I&M use cases for experiments [[BR]] |
| 85 | Supported aggregates: protoGENI servers/VMs? [[BR]] |
| 86 | Utilized experiment control tools: FLACK, with additions [[BR]] |
| 87 | Utilized interfaces: protoGENI API for resources; ns3 for topology; ssh for image loading; vnc for server login; [[BR]] |
| 88 | |
| 89 | Portal to find presentation services in each Measurement Collector; includes vnc for login to server [[BR]] |
| 90 | |
| 91 | Can use Kentucky and CNRI archive services [[BR]] |
| 92 | |
| 93 | |
| 94 | **Starts with LAMP [[BR]] |
| 95 | First focus on providing easy-to-use tools in GENI environment for experimenters [[BR]] |
| 96 | Setup within an experimenters slice [[BR]] |
| 97 | Basic user node image contains suite of perfSONAR tools; application loaded next; provides perfSONAR data interface [[BR]] |
| 98 | Measurement Collector image contains UNIS registry (lookup and toplogy) and Periscope portal services [[BR]] |
| 99 | MC uses protogENI credential to pull data from perfSONAR data interface on each user node [[BR]] |
| 100 | MC and user nodes can be anywhere in GENI [[BR]] |
| 101 | |
| 102 | Supported aggregates: protoGENI servers/VMs? [[BR]] |
| 103 | Utilized experiment control tools: ?? [[BR]] |
| 104 | Utilized interfaces: protoGENI API for resources; ns3 for topology; ssh for image loading; [[BR]] |
| 105 | |
| 106 | Move to: ORCA aggregate/rack, or ? [[BR]] |
| 107 | Move to: GUSH experiment control tools, with OMNI, or ? [[BR]] |
| 108 | Move to: GENI AM API for resources; ns3 for topology; ssh for image laoding; or ? [[BR]] |
| 109 | |
| 110 | Continue to setup within resources assigned by slice mechanism, but modify request rspec to add I&M features before submitting; how to pass manifest to UNIS?; how to create and edit MDOD?[[BR]] |
| 111 | |
| 112 | Extend with LAMP features: [[BR]] |
| 113 | Consider how to load tools on top of basic image [[BR]] |
| 114 | Consider how to extend Periscope to include druple content management service [[BR]] |
| 115 | Consider how to add xserver to basic node image, to login from portal using vnc protocol [[BR]] |
| 116 | |
84 | | First focus: I&M use cases for experiments [[BR]] |
85 | | First supported aggregates: protoGENI servers/VMs; can these be used for HP racks? [[BR]] |
86 | | First utilized experiment control tools: FLACK, with additions [[BR]] |
87 | | First utilized interfaces: protoGENI API for resources; ns3 for topology; ssh; [[BR]] |
88 | | |
89 | | *Continues portal to presentation service; need to add documentation service to create and edit MDOD. Can portal be shared with GIMI project? [[BR]] |
90 | | |
91 | | *Continues use of Kentucky and CNRI services for user workspace and archive. Consider move to iRODS? [[BR]] |
92 | | |
93 | | **Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data [[BR]] |
94 | | Continue to setup within resources assigned by slice mechanism [[BR]] |
| 119 | Consider how to add interface to archive service, e.g., iRODs [[BR]] |
| 120 | |
| 121 | Second focus on I&M use cases for infrastructure measurement [[BR]] |
| 122 | *Continues to provide for infrastructure measurement, and for sharing of data [[BR]] |
| 123 | *Continues compatibility with perfSONAR services [[BR]] |
| 124 | *Continues home and global Lookup Services [[BR]] |
| 125 | |
| 126 | Show how to setup slice that provides perfSONAR data interface, and registers it with globalLookupService [[BR]] |
| 127 | Show how to setup slice with Periscope service and gather data from perfSONAR data interface on another slice [[BR]] |
| 128 | |
97 | | |
98 | | First focus on I&M use cases for infrastructure measurement [[BR]] |
99 | | First supported aggregates: protoGENI servers/VMs; can these be used for HP racks? [[BR]] |
100 | | First utilized experiment control tools: FLACK, with additions [[BR]] |
101 | | First utilized interfaces: protoGENI API for resources; ns3 for topology; ssh; [[BR]] |
102 | | |
103 | | *Continues home and global Lookup Services [[BR]] |
104 | | Create and map MDOD into metadata that is registered [[BR]] |
105 | | |
106 | | *Continue to use perfSONAR clients to present data; can these be integrated into portal? [[BR]] |
107 | | |
108 | | **Consider how INSTOOLS and LAMP/perfSONAR tools might be merged [[BR]] |