Two OMIS ideas....
Both of these ideas focus around the question..."What 'ways of thinking' will be most useful in the short-intermediate term, as OMIS tries to move forward within the overall GENI Project?"
1. Is it useful to begin to classify problems into different OMIS sub-areas such as measurement, security, experimenter interface? I think we realize that integration is necessary...eventually...but, in the interests of making the most progress as quickly as possible, perhaps segmenting the OMIS activity into chunks is useful. Then security issues can be discussed in detail within a security sub-group and more generally (at a higher-level and more briefly) in the WG meetings.
2. Timing of the OMIS efforts, within the overall GENI development timeline, seems important. There are complicated questions that can be stated now..."How will OMIS and Experimenter Support work together?" This is a very important question. But, until we know more about OMIS tools and the basic functioning of OMIS, we can't answer this kind of question. OMIS will have to be built from the ground up. At this point in OMIS development it seems like raw tool development, development of OMIS operational prototypes and integration of OMIS tools in other GENI prototype and integration projects are valuable areas of exploration.
Just ideas...designed to stimulate discussion both on the list and at the March meeting.
_______________________________________________
omis-wg mailing list
omis-wg@...
http://lists.geni.net/mailman/listinfo/omis-wg
