Network Reliability Engineering (NRE) and DevNetOps
If big changes begin inside-out and not have-do-be but be-do-have, then goals of automation require us to focus on our core being and behaviors instead of products, tools and programmability/APIs. To …
| Talk Title | Network Reliability Engineering (NRE) and DevNetOps |
| Speakers | James Kelly (Automation and multicloud lead, Juniper Networks), Matt Oswalt (Marketing Engineer, Juniper Networks) |
| Conference | Open Networking Summit North America |
| Conf Tag | |
| Location | Los Angeles, CA, USA |
| Date | Mar 26-30, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
If big changes begin inside-out and not have-do-be but be-do-have, then goals of automation require us to focus on our core being and behaviors instead of products, tools and programmability/APIs. To engineer of network simplicity, it’s time to lose the title of network admin, operator or architect and embrace a new identity as a Network Reliability Engineer. Like sysadmins graduated from technicians to technologists as SREs, the NRE title stakes a new culture and zenith for engineering network invincibility. Like SREs describe their practices as DevOps, network reliability engineering embraces DevNetOps behaviors. Through real-life examples, we examine the shift to an NRE culture and DevNetOps behaviors that embody the role: networks as code, timelines as pipelines, microservice and immutable infrastructure, pipeline CD, chaos engineering, and continuous measurement and response.
