Re: [tosca] network feature discussion today..

I assume the the requirements on the specification (being declarative etc) does not only apply to networking features but to other types of features too: correct? I.e. the goal is to also have storage, compute,… features be handled declaratively, abstracted from the implementation etc.

What is the difference between being „declarative“ and „intend based“? Furthermore, being „policy based“ is some sort of mechanism to specify the „intend“, i.e. assuming a policy mechanism is predetermining a way to achieve „intend based“.

Gruss/Regards,
Frank

Am 24.04.2014 um 02:25 schrieb Hemal Surti (hsurti) <hsurti@cisco.com>:

Hi Dale/Derek,

Based our Network feature discussion today, here are some thoughts around describing connectivity.

Specification needs to be

Declarative
Intent based
Implementation abstraction
Policy Based

From application perspective, here is the partial list of dimensions we may want to capture.

Type of connection
Network Classification of connection
Source End point requirements
Destination end point capabilities
attributes of connection
Quality of connection
Security policies adherence

In order to achieve the right balance in abstraction, we may have to work from both ends.

1> upwards from network component requirements (firewall, tunnel, LB, NAT, Domain, routing…) on one end.

2> application modeling requirements (protocol, quality, security, availability, resiliency…) from other end.

I can provide more details during our next session.

Thanks,

Hemal

tosca message