[Isod-rg] OGF ISOD-RG use case document

[Joan A. Garcia-Espin]

Hi Alex,

> I think we can agree the e.g. Google App Engine is a typical PaaS  
> example. Here, on this layer, we should incorporate the network. So  
> we don't want to setup a network topology or configure interfaces.

Agree.

> As you wrote: "you need some generic functions". What if I can  
> deploy a "network-aware" distributed application to the Google  
> cloud? I.e. I can specify that I want the network e.g. behave like  
> GPRS mobile network. Is this what we talk about?


This is the bottom-down approach, and it must also be considered. This  
is not so close to my area of expertise, but finding a good use case  
could help driving the discussion.

> What about this:
>
> a) I can setup a virtual NSI/Harmony/Argon/Argia/... instance  
> somewhere in the cloud that can control the physical/virtual network  
> I'm managing or
> b) a can rent a pre-configured appliance that runs an NSI instance  
> for my network...

Yes, these are valid examples. Please mind that in either case you  
need privileged access to either the infrastructure management systems  
or some abstraction/virtualisation layer as the LICL in Geysers [1,2].

Thoughts?

[1] www.geysers.eu
[2] http://www.youtube.com/v/7kinKsJ1Hg8&autoplay=1&hd=1
--
Joan A. García-Espín
DANA, Fundació i2CAT







El 16/09/2011, a las 17:34, Alexander Willner escribió:

> Hi there,
>
> Thanks for the answer.
>
>>>> to PaaS
>>> What about "nPaaS" (Network PaaS): here you can specify network  
>>> properties of your Application PaaS.
>> My idea is: ok, a network domain has some properties (if managed)  
>> that allows you to provide net services on top. Hence, one can see  
>> the net domain as a "platform" for net services. This has  
>> implications in the management and control functions of the domain:  
>> you need some generic functions, and some tech-specific ones. Does  
>> this reasoning fit your mind?
>
> I think we can agree the e.g. Google App Engine is a typical PaaS  
> example. Here, on this layer, we should incorporate the network. So  
> we don't want to setup a network topology or configure interfaces.  
> As you wrote: "you need some generic functions". What if I can  
> deploy a "network-aware" distributed application to the Google  
> cloud? I.e. I can specify that I want the network e.g. behave like  
> GPRS mobile network. Is this what we talk about?
>
>>>> and, why not, to SaaS.
>>> Mh, Network as a Software?
>> Not this way, I am referring to "network software". Simple example:  
>> the control plane and its behaviour. Complex example: programmable  
>> networks. It is again related to control and management, but now in  
>> thinking in the operation phase. Even more, using the Google App  
>> Engine (one platform) one can run different apps simultaneously  
>> (several sw pieces). Is this applicable to networking? How do we re- 
>> define SaaS if so?
>
> What about this:
>
> a) I can setup a virtual NSI/Harmony/Argon/Argia/... instance  
> somewhere in the cloud that can control the physical/virtual network  
> I'm managing or
> b) a can rent a pre-configured appliance that runs an NSI instance  
> for my network...
>
> Best regards, Alex
>
> --
> net.cs.bonn.edu/willner
>
> _______________________________________________
> Isod-rg mailing list
> Isod-rg at ogf.org
> http://www.ogf.org/mailman/listinfo/isod-rg
>