I must admit that I haven't been able to join the NFV ad-hoc group calls
due to timing conflicts, so I might miss some background. But I agree to
what you said in that using artifacts to describe NFGs would introduce
another layer that would need to be standardized (unless the language for
the artifact is already standardized e.g. by ETSI).
I agree that it would make much more sense for TOSCA to stick to TOSCA's
fundamental modeling concepts of using Nodes and Relationships. In contrast
to your proposal, however, I thought more about letting a TOSCA topology
*be* the NFG instead of having something like a NetworkForwardingGraph node
type. Basically, one could imaging node types for VNFs (e.g. VNF1, VNF2,
etc) and relationship types like "ForwardsTo" or "Chains", and then we
could have a topology of node templates for the different VNFs with chains
relations between them.
... but again the disclaimer that my inability to join WG calls might mean
some miss of background.
Cloud Architect - IT Service Management, IBM Systems
IBM Deutschland Research & Development GmbH, D229, Schoenaicher Str. 220,
D-71032 Boeblingen, Germany
email@example.com | +49-7031-16-1219
IBM Deutschland Research & Development GmbH / Vorsitzende des
Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
From: Chris Lauwers <firstname.lastname@example.org>
To: shitao li <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Date: 20/04/2015 23:22
Subject: [tosca] NFV: modeling forwarding graphs
Sent by: <firstname.lastname@example.org>
You have proposed in the past to use the concept of artifacts to model the
forwarding graph(s) in NFV deployments (
). However, this would effectively introduce a requirement for another file
format that needs to be documented, standardized, and maintained. We would
also miss the opportunity to leverage the power of Tosca, since graphs are
at the core of what Tosca models are all about.
I’d like to make an alternative proposal where the forwarding graph is
modeled explicitly using Tosca Node Types. Specifically, I propose to
introduce two new node types: ForwardingGraphNode and ForwardingGraphEdge.
The main responsibility of these node types would be to model the
end-to-end graph by connecting ConnectionPoint nodes together:
- The ForwardingGraphNode connects an “in” connection point to an
“out” connection point on the same VNF (note that “in” and “out” could
point to the same connection point)
- The ForwardingGraphEdge connects a connection point on one VNF
to a connection point on a different VNF.
Tying the ForwardingGraphNode and ForwardingGraphEdge nodes to the
appropriate connection points requires the introduction of a new capability
type for Connection Points (e.g. tosca.capabilities.nfv.Forwarder) and a
new relationship type (e.g. tosca.relationships.nfv.ForwardsThrough) to
associate the Graph Nodes and Graph Edges with the appropriate connection
Using this approach, we can use Tosca to model both the network topology of
VNFs and Virtual Links as well as the forwarding graphs that is overlaid on
top of this topology.
From: email@example.com [mailto:firstname.lastname@example.org
Behalf Of shitao li
Sent: Wednesday, April 15, 2015 1:59 AM
Subject: [tosca] Groups - draft-tosca-nfv-v1.0-wd01-rev02 uploaded
Document Name: draft-tosca-nfv-v1.0-wd01-rev02
No description provided.
Download Latest Revision
Public Download Link
Submitter: Mr. shitao li
Group: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA)
Folder: Working Documents
Date submitted: 2015-04-15 01:58:21