Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

LCU14 404 - LAVA & VLANS - Complex Networks On Demand

2,788 views

Published on

LCU14 404 - LAVA & VLANS - Complex Networks On Demand
---------------------------------------------------
Speaker: D. Pigott, M. Hart, S. McIntyre & N. Williams
Date: September 18, 2014
---------------------------------------------------
★ Resources ★
Zerista: http://lcu14.zerista.com/event/member/137772
Google Event: https://plus.google.com/u/0/events/c7h3j8426l3uu883ulbg7ohhdsk
Video: https://www.youtube.com/watch?v=Qb_NwuDFAyA&list=UUIVqQKxCyQLJS6xvSmfndLA
Etherpad: http://pad.linaro.org/p/lcu14-404
---------------------------------------------------
★ Event Details ★
Linaro Connect USA - #LCU14
September 15-19th, 2014
Hyatt Regency San Francisco Airport
---------------------------------------------------
http://www.linaro.org
http://connect.linaro.org

Published in: Software
  • Be the first to comment

  • Be the first to like this

LCU14 404 - LAVA & VLANS - Complex Networks On Demand

  1. 1. LCU14-404: LAVA & VLANS - complex networks on demand D. Pigott, M. Hart, S. McIntyre & N. Williams, LCU14 LCU14 BURLINGAME
  2. 2. Agenda • History and Background • Real World Problems in the Lab • VLANs and the VLAN daemon • LAVA integration • Wrap up and Questions
  3. 3. A brief history of LAVA and the LAVA Lab • Linaro Automated Validation Architecture • LAVA Lab started out with a handful of boards o One rack, one server, a handful of boards and one switch Slide
  4. 4. The Lab starts growing • Today o 10 racks, 12 dispatchers o 150+ ARM devices o 3 Fast Model servers o QEMU, KVM... • Multi-node comes along o Multiple devices in one test o Increasing need to talk over LAN with each other
  5. 5. Problem 1: Network Reconfiguration • LNG Rack turns up o On LAVA Network, but also their own private network o Cabling needs to be re-done almost on a test by test basis
  6. 6. This doesn’t scale any more!
  7. 7. Problem 2: “Broken” devices • Some boards have USB ethernet, sharing MAC addresses on all interfaces • Some boards share the same MAC address • We have to keep these separated, or bad stuff happens Private switch Lab network
  8. 8. The solution: VLAN daemon • What is a VLAN? • VLAN daemon o Some single-vendor proprietary options? o If it was easy, we’d be doing “apt-get install vland” o Eventually we will be! o Our automated cable monkey!
  9. 9. Port-based VLANs • Each physical port is connected to one VLAN • Ingress switch adds extra tags to each packet on input • Packets routed using VLAN tags • Egress switch removes the tags from packets on output Dispatcher server
  10. 10. “Broken” devices Private switch Lab network
  11. 11. “Broken” devices - after vland base vlan base vlan Lab network
  12. 12. JSON API • CreateVLAN (VLAN_name, switch/port, [switch/port, …]) • DestroyVLAN (VLAN_name) • ShowBaseVLAN (switch/port) • SetBaseVLAN (VLAN_name, switch/port) • ListVLANbyName (string) • ListVLANbyConnection (switch [,port])
  13. 13. Admin • Admin interface to define network setup • Tell the database where the trunks, PDUs and servers are • “Protected” ports • Sanity checks by the daemon • Does the switch setup match what we asked for? • Has anybody “unplugged” a switch? • Has a switch or PDU failed? • Simple command line for admin
  14. 14. LAVA Integration - VLAN multi-node syntax { "role": "filter_one", "device_type": "keystone2", "interfaces": [ { "vlan": "input", "tags": [ "10G" ] }, { "vlan": "output", "tags": [ "1G" ] } ] }
  15. 15. Targeted VLANd capabilities • Set up and tear down ad-hoc port-based VLANs • Support “broken” devices • JSON API for LAVA (and other services) • Admin interface to define network setup • Protect “special” ports • Command line for admin • Sanity checks by the daemon • Support the Cisco switches we use in the lab
  16. 16. Current status / TODO • Drivers written for 2 models of switch • sX300 series • Catalyst 3750 • Simple test harness • Database next • Higher-level logic • Configuration & API
  17. 17. Futures • KVM VLANs • Access control • Reset API • Transactional interface • Cross-site VLANs • Support for more switches - CLI/SNMP/Web UI?
  18. 18. Get Involved! code git://git.linaro.org/lava/vland.git Code is GPL v2+
  19. 19. Questions?
  20. 20. More about Linaro Connect: connect.linaro.org Linaro members: www.linaro.org/members More about Linaro: www.linaro.org/about/

×