Changes between Version 13 and Version 14 of InstMeasCurrentDesignTopicsAll


Ignore:
Timestamp:
02/15/12 19:10:16 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasCurrentDesignTopicsAll

    v13 v14  
    150150
    151151 a)  Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
    152 
    153  b)  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)
    154 
    155  c)  Want to use MDOD schema to define Event Record schema.  (NetKarma)
    156 
     152 b)  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
     153 c)  Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
    157154 d)  MDOD registry.  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
    158 
    159155 e)  MDOD creation and editing service.  [[BR]]
    160 
    161  f)  Object (e.g., Measurement Data Object or I&M Service) names;  need a public reference;  consider DataCite  [[BR]]
    162 
    163  g)  Object registry, with names and public key. [[BR]]
    164 
    165 
     156 f)  Need object (e.g., Measurement Data Object or I&M Service) names;  need a public reference;  consider DataCite  [[BR]]
     157 g)  Do we need object registry, with names and public key? [[BR]]
    166158
    1671592)  Who:  Jason Zurawski (Internet2);  Ezra Kissel (U Delaware);  Eric Boyd (Internet2);  Beth Plale (IU);  Chris Small (GEMINI, IU);  Scott Jensen (Indiana U);  Larry Lannom (CNRI);  LEAD Giridhar Manepalli (CNRI);  Deniz Gurken (GIMI, UH);  Harry Mussman (GPO)  [[BR]]
     
    1761681)  Definition of topic:  [[BR]]
    177169
    178 a)  Use for messages, not generalized data;  assume relatively low rate.  [[BR]]
    179 
    180 b)  Use for OMF messages.  [[BR]]
    181 
    182 c)  Use for "event record messages", that can be logged.  [[BR]]
    183 
    184 d)  XMPP server, in public IP space.  [[BR]]
    185 
    186 e)  Entities connect, and are authenticated.  [[BR]]
    187 
    188 f)  An entity may start a pub/sub node.  [[BR]]
    189 
    190 g)  When an entity subscribes, a message is sent to publisher requesting authorization.  [[BR]]
    191 
    192 h)  Operations plan for XML Messaging Service.
     170 a)  Use for messages, not generalized data;  assume relatively low rate.  [[BR]]
     171 b)  Use for OMF messages.  [[BR]]
     172 c)  Use for "event record messages", that can be logged.  [[BR]]
     173 d)  XMPP server, in public IP space.  [[BR]]
     174 e)  Entities connect, and are authenticated.  [[BR]]
     175 f)  An entity may start a pub/sub node.  [[BR]]
     176 g)  When an entity subscribes, a message is sent to publisher requesting authorization.  [[BR]]
     177 h)  Operations plan for XML Messaging Service.  [[BR]]
    193178
    1941792)  Who: Rudra Dutta (NCSU);  LEAD Anirban Mandal (RENCI);  Christoph Dwertmann (NICTA);  Ahmed El-Hassany (IU);  Harry Mussman (GPO) [[BR]]
     
    198183Lookup Service  [[BR]]
    199184
    200 
    201185[wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
    202186
    203 
    204 1)  Definition of topic:  [[BR]]
    205 
    206 a)  Home and global Lookup Service, as defined by perfSONAR  [[BR]]
    207 
    208 b)  Also Topology Service? 
    209 
    210 c)  Global UNIS?  Also Local UNIS in slice? [[BR]]
    211 
    212 d)  Map MDOD into metadata that is registered  [[BR]]
    213 
    214 e)  Can Lookup Service be used for finding portals?  [[BR]]
    215 
    216 f)  Operations plan for Global UNIS. 
     1871)  Definition of topic:  [[BR]]
     188
     189 a)  Home and global Lookup Service, as defined by perfSONAR  [[BR]]
     190 b)  Also Topology Service? 
     191 c)  Global UNIS?  Also Local UNIS in slice? [[BR]]
     192 d)  Map MDOD into metadata that is registered  [[BR]]
     193 e)  Can Lookup Service be used for finding web interfaces, and other types of portals?  [[BR]]
     194 f)  Operations plan for Global UNIS. 
    217195
    2181962)  Who:  ? (GEMINI);  Giridhar Manepalli (CNRI);  Harry Mussman (GPO)  [[BR]]
     
    2262041)  Definition of topic:  [[BR]]
    227205
    228 a)  Towards Max Ott's vision that provides a unified environment for experiment support  [[BR]]
    229 
    230 b) GENI User Workspace Service is a container for a wide range tools including:  experiment control tools;  portal tools;  measurement analysis and presentation tools
    231 
    232 c) Is a Linux OS environment with files system, certificate and credential stores
    233 
    234 d)  Linux environment can be hosted on server dedicated to user;  shared among multiple users in an organization;  shared among multiple GENI users.
    235 
    236 e)  Many tools interact with GENI aggregates using GENI APIs
    237 
    238 f)  Many tools have a user interface, i.e.,a web interface
    239 
    240 g)  Many tools call other tools through published APIs.
    241 
    242 h)  Having all tools in the same container with a certificate store minimizes effort to gain authorizations.
    243 
    244 i)  Would prefer a service useful with both GIMI and GEMINI tools [[BR]]
    245 
    246 j)  Should compare with CNRI prototype User Workspace service
    247 
    248 k)  Operations plan for GENI User Worksapce service
     206 a)  Towards Max Ott's vision that provides a unified environment for experiment support  [[BR]]
     207 b)  GENI User Workspace Service is a container for a wide range tools including:  experiment control tools;  portal tools;  measurement analysis and presentation tools [[BR]]
     208 c)  Is a Linux OS environment with files system, certificate and credential stores [[BR]]
     209 d)  Linux environment can be hosted on server dedicated to user;  shared among multiple users in an organization;  shared among multiple GENI users. [[BR]]
     210 e)  Many tools interact with GENI aggregates using GENI APIs [[BR]]
     211 f)  Many tools have a user interface, i.e.,a web interface;  these are foten called portal tools [[BR]]
     212 g)  Many tools call other tools through published APIs. [[BR]]
     213 h)  Having all tools in the same container with a certificate store minimizes effort to gain authorizations. [[BR]]
     214 i)  Would prefer a service useful with both GIMI and GEMINI tools [[BR]]
     215 j)  Should compare with CNRI prototype User Workspace service [[BR]]
     216 k)  Operations plan for GENI User Worksapce service [[BR]]
    249217
    2502182)  Who: Jim Griffioen and/or Charles Carpenter (U Kentucky);  Max Ott (NICTA);  Christoph Dwertmann (NICTA);  Chris Small, for NetKarma (Internet2);  Ahmed El-Hassany (IU);  Jeanne Ohren (GPO) [[BR]]
     
    2582261)  Definition of topic:  [[BR]]
    259227
    260 a)  Consider CNRI prototype user workspace and archive service [[BR]]
    261 
    262 b)  Consider U Kentucky archive service [[BR]]
    263 
    264 c)  Use iRODS service? [[BR]]
    265 
    266 d)  How to move data to service:  move file;  move SQL DB;  or? [[BR]]
    267 
    268 e)  How are partitions for different users managed? [[BR]]
    269 
    270 f)  How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
    271 
    272 g)  Operations plan for Archive Service.
     228 a)  Consider CNRI prototype user workspace and archive service [[BR]]
     229 b)  Consider U Kentucky archive service [[BR]]
     230 c)  Use iRODS service? [[BR]]
     231 d)  How to move data to service:  move file;  move SQL DB;  or? [[BR]]
     232 e)  How are partitions for different users managed? [[BR]]
     233 f)  How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
     234 g)  Operations plan for Archive Service. [[BR]]
    273235
    2742362)  Who: Giridhar Manepalli (CNRI);  LEAD  Shu Huang (RENCI) ;  Larry Lannom (CNRI);  Wesley Wu (U Kentucky);  Hussam Nasir (U Kentucky);  Chris Small  (NetKarma, IU) [[BR]]