authority and delegation of authority in NS (Actor?)
Attached is a two page ppt. The first modifies Tomohiro's a little - and uses names from Joan. The main modification other than names is that it removes the capability advertisement module. The idea is that a single module provides "services" which may be called from outside or integrated in the actor itself. We need to describe what these services do for the Actor, but not how they do it. In my mind these are services that Chin has started to enumerate (except the resource coordination module). The Aggregation/ coordination module in the pic is Chin's coordination and Tomohiro' aggregation module -- I think they are the same. -- any thoughts? The second shows resource delegation of authority (for a particular resource. Note that the local RMM agent is the ultimate authority for resources controlled by the RMM. Given that the RMM agent is part of the Actor, the Actor is the ultimate authority for all resources controlled by the RMM. Resources requested by the NSI are delegated from the remote NSA and may be redelegated (along with the local resources) to a requesting agent. This, btw, is very similar if not identical to what in my understanding the ORCA and GENI frameworks do. -- thoughts or questions?
Hi all, I revised the NSA functional component document and essentially made it very generic. After talking with Inder, I realized that this document should give us a VERY brief overview of the NSA, and as such, all it has is a block diagram and descriptions of each component. The focus of this document is to support the NSI architecture document and not take away from it. I've removed all the MAY/MUST statements because those should really be in a separate NSA architecture document, if we plan to create one. I noticed that the diagrams from Joan and Tomohiro had the notion of a aggregator/coordinator. In the NSA functional component block diagram, that function is supported by "Resource Management". I'm open to ideas on where this should go. Please review it and feel free to comment (there are some inline). Thanks. - Chin --On November 10, 2009 11:45:32 AM -0500 John Vollbrecht <jrv@internet2.edu> wrote:
Attached is a two page ppt. The first modifies Tomohiro's a little - and uses names from Joan. The main modification other than names is that it removes the capability advertisement module. The idea is that a single module provides "services" which may be called from outside or integrated in the actor itself. We need to describe what these services do for the Actor, but not how they do it. In my mind these are services that Chin has started to enumerate (except the resource coordination module). The Aggregation/ coordination module in the pic is Chin's coordination and Tomohiro' aggregation module -- I think they are the same. -- any thoughts?
The second shows resource delegation of authority (for a particular resource. Note that the local RMM agent is the ultimate authority for resources controlled by the RMM. Given that the RMM agent is part of the Actor, the Actor is the ultimate authority for all resources controlled by the RMM. Resources requested by the NSI are delegated from the remote NSA and may be redelegated (along with the local resources) to a requesting agent. This, btw, is very similar if not identical to what in my understanding the ORCA and GENI frameworks do. -- thoughts or questions?
We will have a call tomorrow at 9 ET (for 1.5 hours). Call info Call infoCall: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 Proposed Agenda 1) Naming of elements - Joan's and Tomohiro and Chin's 2) delegation of authority over NSI interface 3) Chin's functional component descriptions We can revise at the start of the call. I suggest we assign times to each topic and try to talk some about all, and continue using online chat. John
John, all, find attached a new version of the slide, reflecting the naming we've just discussed (only affects slide 1). Comments are more than welcome. Regards, -- Joan A. Garcia-Espin CTX, i2CAT Foundation El 10/11/2009, a las 17:45, John Vollbrecht escribió:
Attached is a two page ppt. The first modifies Tomohiro's a little - and uses names from Joan. The main modification other than names is that it removes the capability advertisement module. The idea is that a single module provides "services" which may be called from outside or integrated in the actor itself. We need to describe what these services do for the Actor, but not how they do it. In my mind these are services that Chin has started to enumerate (except the resource coordination module). The Aggregation/ coordination module in the pic is Chin's coordination and Tomohiro' aggregation module -- I think they are the same. -- any thoughts?
The second shows resource delegation of authority (for a particular resource. Note that the local RMM agent is the ultimate authority for resources controlled by the RMM. Given that the RMM agent is part of the Actor, the Actor is the ultimate authority for all resources controlled by the RMM. Resources requested by the NSI are delegated from the remote NSA and may be redelegated (along with the local resources) to a requesting agent. This, btw, is very similar if not identical to what in my understanding the ORCA and GENI frameworks do. -- thoughts or questions?
<Authority.NSActor.10.10.09.ppt> _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org http://www.ogf.org/mailman/listinfo/nsi-wg
participants (3)
-
Chin Guok -
Joan A. Garcia-Espin -
John Vollbrecht