On Feb 25, 2008, at 2:13 PM, Williams, James G wrote:
>
>
> 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.
Certainly classifying is useful. I don't think we have critical mass
to make sub-groups yet, but I agree with you that it will probably
happen in the future as we delve into each area. Right now I am most
interested in getting OMIS members to contribute their opinions on
what they think are the most important areas to pursue in a way that
allows us to pursue the most important issues right away, which is
important as you emphasis in your next point. Do you (or others) have
a suggestion for how to collect this input quickly (aside from the
"top 10 list?" I think we'll have to have most of our discussion on
the mailing list, since there is actually very little time for the
joint working group meetings during GEC2. We need to use that time to
highlight the cross-group issues that are most important.
>
>
> 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.
Along these lines, Mike Patton has been talking to working group
members in other groups and will be sending some notes to the list
very soon related to possible GENI use cases that might help clarify
some ground-up OMIS needs if we can get some discussion going on the
list.
>
>
>
> Just ideas...designed to stimulate discussion both on the list and
> at the March meeting.
Thanks very much! I really want to use people's time wisely at the
March meeting and on the list. I'm keenly aware that everyone is
volunteering at this point, and there are many demands for your time.
It is very important, especially for OMIS, to actively contribute in
the early stages of the GENI architecture and design, to make sure
operations requirements are included in development and prototyping.
>
>
>
>
> _______________________________________________
> omis-wg mailing list
>
omis-wg@...
>
http://lists.geni.net/mailman/listinfo/omis-wg_______________________________________________
omis-wg mailing list
omis-wg@...
http://lists.geni.net/mailman/listinfo/omis-wg