BRINGING OPENWRT TO MARKET

Size: px

Start display at page:

Download "BRINGING OPENWRT TO MARKET"

Margery Gardner
6 years ago
Views:

1 BRINGING OPENWRT TO MARKET OPENWRT SUMMIT 2017 technicolor.com

2 Introducing Technicolor We are known for Entertainment (film processing, special effects ) We also design and manufacture equipment for the Connected Home (routers, set-top-boxes ) And we work with OpenWrt/LEDE 2

3 Market Dynamics Component Vendors Technicolor Internet Service Providers Subscribers (You!) Technicolor is not in the retail business Our direct customers are ISPs Large scale operations: hundreds of products, tens of millions of homes Extensive and diverse set of requirements: triple play (Data, IPTV, VoIP), remote management Access to component vendor s proprietary code: physical layer (DSL, Wi-Fi, LTE), hardware accel High quality expectations: uptime, Quality of Service Robust software processes: traceability, release management, continuous integration These market dynamics influence the way we work with OpenWrt/LEDE 3

4 Our customers using OpenWrt One unified SW strategy lets customers share the benefits of interoperability and feature evolutions Homeware deployed in 50+ customers from Australia to Gibraltar 4

5 Solid platform Provides the right functionality for a standard home router Modular and platform agnostic Easy to build upon to create your own router products Why OpenWrt/LEDE? Accessible Well known throughout the community and the industry Anyone can get started, no red tape Common reference platform for third parties Diverse ecosystem Platform of choice for new router software initiatives ranging from commercial to nonprofit Innovation across boundaries 5

6 Our proposition with Homeware Unleash creativity for your own applications or 3 rd parties. User Applications Voice TR-069 GUI Analytics TR-143 Network OpenWrt is the dominant platform for gateway market Broadcom Semicon Vendor SDK Intel Quantenna Annapurna Qualcomm Vendor agnostic platform approach 6

7 Homeware quarterly releases, based on OpenWrt One highly customizable release branch for all customers, chipsets and platforms releasing 4 times per year Homeware Build complexity solved Consistent quality Configurable and flexible Maximize reuse Bug fix coverage Fast security updates

8 Enabling quality software During development Homeware is constantly verified with Continuous Integration fully integrated with bug tracking system. Each deliverable is fully validated on the target platform in the lab and the customer network. Development On generic SW Technology-facing testing Functional testing SW dev support testing Typically in generic CI setup Typically automated Validation On customized SW Customer facing testing Scenario testing From User perspective Typically in customer network Typically manual Field Diagnostics in the field Fast resolution 8

9 Focus on security Security assessment on every quarterly release of Homeware Vulnerabilities are being scored and assessed Common Vulnerability Scoring System v3.0 NOT ALLOWED Known critical vulnerabilities (CVSS > 7) Field deployment Field trials TOLERATED Known critical vulnerabilities Lab trials Enforced by the Technicolor Security Office 9

Offering an SDK Homeware gives operators and their partners the tools that

Compiler toolchain, APIs, documentation, sample apps, support services

groups + namespace isolation Control groups CPU Memory Managing sparse

10 Offering an SDK Homeware gives operators and their partners the tools that they need to develop, to integrate and to deploy their applications Compiler toolchain, APIs, documentation, sample apps, support services Package management Remote management Linux Containers (LXC) = control groups + namespace isolation Control groups CPU Memory Managing sparse resources I/O Namespace isolation Processes Users Improving security File systems Network stacks 10

11 Enabling life cycle management TR-69 / TR157 Amendment II App Store App 1 App 2 App 3 App 4 Enables the gateway as an application platform

12 Combining Proprietary and Open Source SW (Simplified package distribution of a Technicolor OpenWrt based router) Specific kernel extensions, drivers, utilities Component vendor 10% Other 5% Base Linux system: kernel, drivers OpenWrt framework: UCI, ubus, procd Managed services: IPTV, VoIP, WAN sensing Remote management: TR-069, SNMP Local management: Web UI, TR-064 Technicolor 35% Open source 50% + patches Standard networking: Ethernet, IPv4, IPv6, firewall, NAT, DHCP, DNS, QoS Various applications: VPN, Samba, MQTT Value-added applications and services 12

13 OpenWrt Contribution Strategy Component vendor 10% Technicolor 35% Other 5% Open source 50% + patches Goal: achieving the right balance between software available in OpenWrt as open source, and software maintained in house Reasons for Technicolor to contribute: Strengthen the community, increase adoption Stimulate new contributions, increase quality Reduce maintenance cost, avoid forking Reasons for Technicolor not to contribute: Loss of competitive advantage Open source licensing constraints Effort to contribute and to maintain, low chance of adoption 13

14 Adding new features GRE tunneling PPP Unnumbered IPinIP netifd link state propagation NTP server config via DHCP Procd firewall support Making existing packages ready for field deployment 464xlat/map-t odhcp6c and odhcpd Past and Present Examples Package upsteps, additional config options dnsmasq, nginx and ngx_lua, strongswan, curl, openssl, openssh, dropbear Bug fixes ubus, procd, libubox, firewall3, Ldoc, luacheck Unsuccessful contributions (*it happens!) MWAN TR-069 datamodel mapping framework Potential future contributions WAN sensing Life Cycle Management 14

15 Thank you

mbed OS Update Sam Grove Technical Lead, mbed OS June 2017 ARM 2017

mbed OS Update Sam Grove Technical Lead, mbed OS June 2017 ARM mbed: Connecting chip to cloud Device software Device services Third-party cloud services IoT device application mbed Cloud Update IoT cloud