<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:tax="http://schemas.microsoft.com/sharepoint/taxonomy/soap/" xmlns:tns="http://schemas.microsoft.com/sharepoint/soap/recordsrepository/" xmlns:spsup="http://microsoft.com/webservices/SharePointPortalServer/UserProfileService" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style></style></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1>Hello guys!<o:p></o:p>Long time ago I wrote from my another email (this is company email) the idea which I want to contribute to skydive<o:p></o:p>Finally, we made a release of skydive integration into our product and I got a time to get an opensource contribution approval.<o:p></o:p>So, here is a list of things which we may contribute to skydive:<o:p></o:p><![if !supportLists]>1. <![endif]>Separated typescript solution to build a network topology in browser. Pluggable, changeable, adaptable to huge infrastructures.<o:p></o:p>Around may we discussed the javascript solution to improve and provide ability to see different layouts for network topology.<o:p></o:p>At the end of the page you may see how it looks like in our implementation.<o:p></o:p>Sylvian reply:<o:p></o:p><o:p> </o:p><div style='mso-element:para-border-div;border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.25in;margin-right:0in'>Hi Sergey,<o:p></o:p><o:p> </o:p>Thanks for you email. There is a lot of interesting topics, I'll try to answer to all of them :)<o:p></o:p><o:p> </o:p>For the view complexity of the topology, you're right, that's why we started to rewrite the D3 view to bring something more stable in term of node placement but also being able to leverage the filtering mechanism we have to reduce the number of elements present in the view and sent by the server. Currently we don't have anything ready yet, just a POC.<o:p></o:p><o:p> </o:p>For the "different view thing", there is a way to achieve this which is for sure not perfect. We do have this "graph" object listening the websocket connection and dispatching message to layouts. Currently two layouts are listening the graph events, the "standard" topology view and the Openflow rules view. The last one displays only the flow rules. That is for sure something we need to rework in order to make it more flexible and more clear.<o:p></o:p><o:p> </o:p>It seems to me that we already have some of what you suggested but not clearly identified and decoupled. That's where we want to push efforts. The typescript migration will help on this.<o:p></o:p><o:p> </o:p>Do you think you can share the work you did around the typescript migration ? We think that this conversion we will be the first step toward a better architecture.<o:p></o:p><o:p> </o:p>Another question a bit out of topic, do you think you can share in which context you used Skydive ?<o:p></o:p><o:p> </o:p>Thanks,<o:p></o:p>Sylvain<o:p></o:p></div><o:p> </o:p><o:p> </o:p>My email: <o:p></o:p><o:p> </o:p><div style='mso-element:para-border-div;border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.25in;margin-right:0in'>On Thu, May 10, 2018 at 5:26 PM, Sergey Glazyrin <<a href="mailto:s.glazyrin@partner.samsung.com" target="_blank">s.glazyrin@partner.samsung.com</a>> wrote:<o:p></o:p>Hello guys!<o:p></o:p> <o:p></o:p>This is a follow up of discussion we started with Sylvian month ago.<o:p></o:p>Sorry Sylvian, was busy.<o:p></o:p> <o:p></o:p>How do we extend skydive frontend if customers want to customize it ?<o:p></o:p>Problems/Use cases:<o:p></o:p>• Network topology sometimes very complicated, what if want to show only nodes between two network elements ? A and B ? Customers/People want to have a simplified interface.<o:p></o:p>• We may need to show only part of Metainformation for network elements. How can we do that ?<o:p></o:p>• Will the browser behave good if we show network topology for 2000 hosts? Will it have a problem with memory ?<o:p></o:p> <o:p></o:p>Solve performance problem<o:p></o:p>• Introduce different levels of detalization: host detalization, concrete host detalization. Then we may need only small datasets, if we have 2000 hosts, we may need only a hosts and network elements which connect hosts to each other.<o:p></o:p> <o:p></o:p>Solve problem of different layouts/views.<o:p></o:p>Here we may introduce another abstraction: workload which will be responsible for transformation data sets/simplification/another custom user needs.<o:p></o:p> <o:p></o:p>Skydive frontend new architecture<o:p></o:p><o:p> </o:p><img border=0 width=627 height=182 id="_x0000_i1028" src="cid:image002.png@01D44F58.3301A850"><o:p></o:p><o:p> </o:p><o:p> </o:p>Conclusion<o:p></o:p> <o:p></o:p>I believe such approach would help us to have a lot of different views/workloads and easiest usage of frontend<o:p></o:p> <o:p></o:p>PS: Around 20-30% we migrated to typescript but then we stopped migration because of tight deadline.<o:p></o:p></div> <o:p></o:p>Sylvian reply:<o:p></o:p><div style='mso-element:para-border-div;border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.25in;margin-right:0in'>Hi Sergey,<o:p></o:p> <o:p></o:p>Great ! As we wanted to provide other views for the topology, the D3 things implemented as a library is really something interesting, especially using typescript. Do you have any code available or something ? Tests would be really useful too.<o:p></o:p>About the "more user-friendly" frontend, do you have anything that you can share, it will help us to improve it :)<o:p></o:p> <o:p></o:p>Regards,<o:p></o:p>Sylvain<o:p></o:p></div> <o:p></o:p>Previous email:<o:p></o:p> <o:p></o:p><div style='mso-element:para-border-div;border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 4.0pt;margin-left:.25in;margin-right:0in'>Hello guys!<o:p></o:p>I do like your skydive stuff but I need to customize frontend of skydive to make it more userfriendly for customers + my own stuff, a bit differnet data, etc....<o:p></o:p>I started rewriting javascript frontend on TypeScript.<o:p></o:p>But then I realized I've no time to finalize it because we have a tight deadline.<o:p></o:p>It's not a problem.<o:p></o:p>In general I love skydive, love frontend, especially D3 related stuff. But I'd like to work on moving this D3 related stuff, getting information from websockets in this npm package, without any Vue things, etc. <o:p></o:p>Would be that interesting for you ? If I implement it with tests, etc, would you consider to to migrate to this npm package ?<o:p></o:p></div><o:p> </o:p>Here is an example of how it is used.<o:p></o:p>Here’s a list of hosts<o:p></o:p><img border=0 width=1667 height=889 id="Picture_x0020_2" src="cid:image004.png@01D44F58.3301A850"><o:p></o:p><o:p> </o:p>When user chooses a topology we show by default application topology with virtual machines on this host. (I’ll send an explanation of how we added virtual machines in next letters.)<o:p></o:p>As you can see it is simplified version of topology. We removed all nodes which are outside of connection between host and app (it is useful for debugging specific applications)<o:p></o:p><o:p> </o:p><img border=0 width=1674 height=820 id="Picture_x0020_3" src="cid:image005.png@01D44F58.3301A850"><o:p></o:p>And here is a full default skydive topology<o:p></o:p><o:p> </o:p><img border=0 width=1686 height=877 id="Picture_x0020_4" src="cid:image006.png@01D44F58.3301A850"><o:p></o:p><o:p> </o:p>So, the idea of solution is to provide an interface to switch between different layouts.<o:p></o:p>I’ll be able to show you the code in two weeks. Need to cleanup and write some tests.<o:p></o:p><o:p> </o:p>Best, Sergey<o:p></o:p>Samsung R&D Institute Poland<o:p></o:p>Samsung Electronics<o:p></o:p>Cell: +48731810674<o:p></o:p><o:p> </o:p></div><table id=bannersignimg data-cui-lock="true" namo_lock><tr><td> </td></tr></table><table id=confidentialsignimg data-cui-lock="true" namo_lock><tr><td> <img style="border: 0px solid currentColor; border-image: none; width: 520px; height: 144px; display: inline-block;" unselectable="on" data-cui-image="true" src="cid:cafe_image_0@s-core.co.kr"> </td></tr></table></body></html><img src='http://ext.w1.samsung.net/mail/ext/v1/external/status/update?userid=s.glazyrin&do=bWFpbElEPTIwMTgwOTE4MTIwMjE0ZXVjYXMxcDJlYjllMmIxMGYzZGJmN2NiYjQ5MzgyOTUyNTYwMmE4NyZyZWNpcGllbnRBZGRyZXNzPXNreWRpdmUtZGV2QHJlZGhhdC5jb20_' border=0 width=0 height=0 style='display:none'>