Subject | RE: Network Control Architecture |
From | "Inder Monga" <imonga@xxxxxxxxxx> |
Date | Tue, 17 Apr 2007 23:08:39 -0400 |
Dear Gigi and All, I was not present at the last GLIF meeting and plan to remedy that going forward. I apologize for maybe bringing up the same issues again, but these are my initial reactions in looking at the slides: A) I am surprised to see such a deep Grid flavor to the interfaces. I do understand Grids are an important application of the GLIF network, but can't GLIF define generic interfaces that can be used by non-grid applications, management platforms, automated scripts? To choose this path because OGF as a likely standardization body is not the right reason. The defined generic interfaces need to fit into the "grid" resource management model. B) In examining the multi-domain proposal, it looks like the RB from one domain can request access to resources directly from the specific RM of the next domain without notifying the RB of the other domain? This model does not appeal to me. I am concerned about the case when resources are required across "n" domains (say), RBi (where i belongs to N) needs to access and request resouces from xRMj where x = Network, Compute, Storage, Instrument and j = 1 .. n, {n <=N} ? In this case, the RB needs to have knowledge of and have access to (through firewalls) to all those RMs. In the multi-domain model we have demonstrated (detailed document attached) that having each domain manager manage the resources within its own domain makes the best architecture. With that model you have the advantage of having only ONE multi-domain resource request entry point (and corresponding AAA policies). I look forward to discussions on the mailing list. Thanks, Inder -----Original Message----- From: owner-tech@xxxxxxx [mailto:owner-tech@xxxxxxx] On Behalf Of Gigi Karmous-Edwards Sent: Tuesday, April 17, 2007 4:18 PM To: controlplane@xxxxxxx; GLIF-tech Subject: [GLIF tech] Network Control Architecture Dear All, At the last GLIF control plane meeting in Minneapolis (meeting minutes will be sent tomorrow to the list) we had several discussions on interoperability between the different networks. We drew a diagram on the white board with input from the participants. The outcome was an action item on me to send out a high level functional diagram on the framework for interoperability (sorry for the delay). We expanded the notion of network resource in the control plane working group to include other resources as well, such as compute, storage, instruments, etc. Enclosed are three very high level slides discussing the framework and the high level functional components included in a "Resource Broker " and a "Network Resource Manager". Several of you in the meeting had comments on the interfaces we need to standardize. I propose we start with the "Grid Network Interface" GNI, first. We also agreed to work with both the GLIF community and standard bodies like OGF to develop these interfaces. I look forward to your comments. Kind regards, Gigi -- -------------------------------------------- Gigi Karmous-Edwards Principal Scientist Advanced Technology Group http://www.mcnc.org MCNC RTP, NC, USA +1 919-248 -4121 gigi@xxxxxxxx --------------------------------------------
Attachment:
GHPN Grid Network Services in SC04.pdf
Description: GHPN Grid Network Services in SC04.pdf
- Follow-Ups:
- Re: [GLIF controlplane] RE: Network Control Architecture
- From: Gigi Karmous-Edwards
- Re: [GLIF controlplane] RE: Network Control Architecture
- References:
- Network Control Architecture
- From: Gigi Karmous-Edwards
- Network Control Architecture
- Prev by Date: Re: Network Control Architecture
- Next by Date: Re: Network Control Architecture
- Previous by thread: Re: Network Control Architecture
- Next by thread: Re: [GLIF controlplane] RE: Network Control Architecture
- Index(es):