NSM Kubecon Demo Update

[Christopher Metz]

Hey Folks-

Tied up tomorrow so can't make mtg. Items:

a) updated demo deck on my thoughts re: objectives, architecture, logistics etc.

b) need rough consensus on objectives, functions to show, etc.

c) key component is UI :-) ... we need a front-end package that can dynamically render topology/data, overlay paths, etc. from the NSM network, along with buttons or something to initiate NSM setup. 

d) need to select UI package and start hacking. I gotta guy who is working on contiv vpp with code hacks he has used before and can see if cycles are available. Upsides are: done before, can get it done quickly; downside is single purpose,throw-away, kcon-demo code only. Ed suggested another package (Skynet). Is open source and possesses k8s hooks. Upside is open source, already hooks into k8s, community supported, iterations could live on after kcon; downside is effort to hack up NSM probes (hooks), I do not know what is involved. I am 100%  fine w either and prefer the latter if we have the time. Other options welcome

e) need a platform we can bolt the UI on top of so we can dev/test UI to make it work and look pretty.

Items b) thru e) need attention and commitment by end of week? Interested in assisting parties, ping me and I can setup call later in the week to discuss.

Of course open to any and all suggestions on making a quality NSM demo for kcon.

tx

-cm 

[Mathieu Rohon]

hi,

Concerning the dynamic rendering UI, I talk about skydive (http://skydive.network/index.html) to ed and kyle, as I use to use it for demos. It renders topologies very well with d3js.
Unfortunately, for now, it doesn't support vpp, and I'm not sure I'll have time to work on it before the kubecon, even if adding new probes for vpp in skydive, or alternatively adding external components (vpp/memif/vxlan interfaces) to the skydive topo with the skydive API doesn't seem too hard. I'll try to work on it on my spare time.

Skydive has k8s probes, marked as unstable for now. I've never played with it, but we we should be able to show and select k8s elements (deployments, replicaset, services) in the topo.

I'm CCing the skydive-dev team, they'll probably be interested in your demo.

Regards

Mathieu

--
You received this message because you are subscribed to the Google Groups "networkservicemesh" group.
To unsubscribe from this group and stop receiving emails from it, send an email to networkservicem...@googlegroups.com.
To post to this group, send email to networkse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/networkservicemesh/e73ae3d0-dcf4-4d6c-84b4-366186c947d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ed Warnicke]

Mathieu,

I think what we'd probably be looking to contribute for NSM would be a Probe for Network Service Managers (since they manage the links).  

Skydive team,

Delighted to meet you, we are targeting a demo for Network Service Mesh for Kubecon, and as part of that were looking for ways to visualize topology.  It looks like you guys have done a bunch of good work there, how would we plug in? :)

Ed

To view this discussion on the web visit https://groups.google.com/d/msgid/networkservicemesh/CAAfiWQrOvNjKe1Hd%3DvjRXHTskO81t%2BpsH5gCpObkxoEBQMcgOw%40mail.gmail.com.

[Christopher Metz]

Could we use VPP REST APIs to pull out VPP data and feed it into skydive?

https://github.com/ligato/vpp-agent/tree/master/plugins/rest

Attached is doc I hacked up for APIs available when using another k8s network solution: contiv vpp. I don't know effort to reuse/re-engineer for NSM

-cm

PS - I am completely all-in on skydive

[Ed Warnicke]

The interesting question is what is semantically interesting to skydive.  I would maintain the semantically interesting bits (graphnodes and graphlinks) are going to be at NetworkServiceManager level, not vpp level.

Ed

[Mathieu Rohon]

AFAIK, skydive use to gather datas from switches (OVS, netlink...). Those probes are adding nodes and links, while "controller probes" such as Neutron or K8s probes are adding additional infos to the metadata of those skydive elements.

I let the skydive team correct me if I'm wrong.

The same kind of design could be used with a VPP probe that would add interfaces, while a NSM probe would add metadatas (NetworkServices, Endpoints?)

A single NSM probe probably fit too, moreover it seems easier to develop for the kubecon.

[Sylvain Afchain]

Hi,

Nice to meet you guys !

What Mathieu described is correct, probes are either gathering information to create graph elements (nodes/links) in Skydive or enhancing. For the demo there are multiple options to inject information into Skydive :

- write a real probe[1]

- use the python API[2]

- use the topology api[3]

We were about to start to work on the VPP integration. I think working on this together may help.

You can reach out us on IRC (freenode #skydive-project)

Thank,

Sylvain

[1] blog post pending, https://github.com/skydive-project/skydive.network/pull/29

[2] http://skydive.network/documentation/api-python

[3] http://skydive.network/documentation/api#topology-rules

_______________________________________________
Skydive-dev mailing list
Skydi...@redhat.com
https://www.redhat.com/mailman/listinfo/skydive-dev