Subject: [yang-doctors] Cloud portal telemetry alignment with - does YANG have model the hierarchy to support cloud portal telemetry?

From: "Bugenhagen, Michael K" <[email-masked]>
Date: Thu, 16 Feb 2017 15:50:10 +0000

Hello,

     I’m working some provider business projects with other carriers and we’ll be crafting a standard network telemetry API framework that will support telemetry for Cloud portals.

Cloud portals use a very specific model driven hierarchy using the “cloud transparency” principle of exposing resource telemetry.
Specifically, if we can’t map that telemetry to the matching resource levels then that telemetry is unfit for cloud portal display (it’s broken).

Cloud portals represent resources in this hierarchy

                Atomic, Composite, Cluster, Cloud     -

This model is the cross over point between “Menu oriented ordering Model” portals, and Cloud that enabled them to have customer cloud portals.
All ordering (even McDonalds) uses the pickles, hamburger, happy meal, …,
Cloud uses “CPU, Memory, composite = VM, Cluster = storage cluster, group of servers,  ..   and of course, a Virtual Data Center = Cloud
Each level being a composite of the lower models so that once can “click down” into the lower level resources to display the telemetry.

However, right now Yang is without any such “model driven construct” that I can find – it’s build for SDN, and Orchestration – but not the portal.

** My question(s)

a)       Have the YANG / NETCONF groups considered this hierarchy …
To be suitable for cloud portal telemetry we would need a “model driven” framework that provided this set of YANG models, with a known hierarchy.

ie.  -- each entity level would have a set of standard resource CIM’s to support the portal. (Atomic, Composite, …)

Currently, I’m thinking about having 4 standard yang models that could be established for any one resource for display in a cloud portal.

a)       Resource / Service attribute

b)       PM

c)       FM

d)       Allowable states

This way anyone could make a “model” of that resource for display into a cloud portal -

** This work’s going to move forward to create a standard Network API for cloud telemetry (I’m only showing one piece of the problem here – the rest will be addressed in other areas).  However, I think we’ll be coming around to discuss this with the IETF so I wanted to ping your team.

Thanks,
Michael Bugenhagen
CenturyLink
NFV Chief Architect, Eco-System Strategy & Dev.

This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.