Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Skydive 31 janv. 2016

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Wird geladen in …3
×

Hier ansehen

1 von 21 Anzeige
Anzeige

Weitere Verwandte Inhalte

Diashows für Sie (20)

Ähnlich wie Skydive 31 janv. 2016 (20)

Anzeige

Aktuellste (20)

Skydive 31 janv. 2016

  1. 1. Skydive Real-time network topology and protocols analyzer Sylvain Afchain
  2. 2. Sylvain Afchain Principal software engineer Redhat Openstack Neutron contributor Opencontrail contributor
  3. 3. WHY ?
  4. 4. SDN IS COMPLEX Troubleshooting/monitoring is even more complex
  5. 5. Implementations Management Control plane ● OpenFlow ● XMPP ● BGP ● AMQP ● Etc... Data plane ● VLAN ● VXLAN ● GRE ● MPLS ● OVS, Linuxbridge, other
  6. 6. Real network issues… just an extract ! Offloading issue leading in packet drop Offloading issue leading in bad performances, tcp retransmission Offloading issue leading in bad checksum Configuration issues like MTU Remaining filtering rules or routing Forwarding database corrupted with vxlan Offloading checksum issue with gre tunnel, leading in bad performances for TCP connections. Bonding, LACP issues multicast packets dropped in vxlan tunnels SDN Control plane issues, config not reflected to the dataplane, ex: Remaining or missing openflow rules. While trying to record a demo of Skydive…. and this not a joke ! http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [('Connection aborted.', OSError(101, 'Network is unreachable'))]
  7. 7. Troubleshooting Where... are the packets dropped ? are the packets fragmented ? is the congestion point ? What… is the path of packets ? kind of traffic for this virtual network ? is the number of flows on this link ? is the number of TCP Sessions ? is the bandwidth for this tenant ?
  8. 8. Current toolbox ● Iproute2 ● ovs-vsctl, ovs-ofctl, ovs-dpctl... ● ethtool ● brctl ● tcpdump ● SDN CLI/API ● etc.
  9. 9. The needs 1. SDN Agnostic solution 2. Non-intrusive 3. Lightweight 4. Flow centric 5. Easy to deploy 6. Open, API 7. Connectors to SDN
  10. 10. The needs 1. Topology probes a. interfaces, bond, mtu, vlan b. bridges c. Network namespaces d. etc.. 2. Flow probes a. on-demand traffic capture b. on-demand counter capture c. filtering d. underlay/overlay informations 3. Topology/flow aggregation a. mapping topology/flow b. analysis
  11. 11. Skydive design Agents ● On the nodes to monitor ● Topology probes ● Flow probes ● Southbound API, topology queries, Flow Probes Analyzers ● collect agents data, time-series database ● Flow centric ● Northbound API, topology queries, flow capture, alarming
  12. 12. Skydive Use-cases Operator : ● Detection of common configuration errors. ● Detection of live network issues at any point of the infrastructure meaning in the underlay and in the overlay. ○ bad performances, helping to find the root cause. ○ DDOS and any unattended traffic. ● Possibility to capture traffic at any point for further analysis. ○ Historic of all the metrics captured, keeping all the flow events for further analysis. User : ● Detection of misconfigured filtering mechanism like security groups. ● Detection of bad application performance, bad RTT.
  13. 13. Skydive today ● Topology capture ○ Netlink, NetNS, ETHTool, OVSDB ○ Connectors: ■ Neutron, Docker ○ Backend: ■ In-Memory, Gremlin based (Titangraph, Tinkerpop, neo4j) ● Live distributed capture ○ sFlow with OVS, PCAP ● Analysis ○ Flow table, flow event, session expiration, etc. ○ Backend: ■ ElasticSearch ● API/WebUI ○ On-demand capture, Topology (events, alerting)
  14. 14. Skydive Roadmap ● Topology capture ○ Adding more connectors ● Live distributed capture ○ PCAP, Filtering ● Analysis ○ Adding more protocols ○ Alerting ● Improvement of the security ○ RBAC ○ SSL
  15. 15. Key points Non-intrusive, SDN-agnostic. Helps to troubleshoot/monitor giving informations on the root cause and its impact. Gives feedback providing informations needed for capacity planning, billing. Open source Apache License Written in Go
  16. 16. Questions What would the best place for the project ? OpenStack - single point where multiple SDN controllers meet, but is it really a network focussed project ? Events to engage/propose content ?
  17. 17. Questions ? https://github.com/redhat-cip/skydive safchain@redhat.com

×