<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>YANG on rob.sh</title>
    <link>https://rob.sh/tags/yang/</link>
    <description>Recent content in YANG on rob.sh</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 12 Feb 2024 22:12:00 -0500</lastBuildDate>
    <atom:link href="https://rob.sh/tags/yang/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NANOG 90: Pondering Abstractions</title>
      <link>https://rob.sh/post/nanog90/</link>
      <pubDate>Mon, 12 Feb 2024 22:12:00 -0500</pubDate>
      <guid>https://rob.sh/post/nanog90/</guid>
      <description>&lt;div style=&#34;text-align:center&#34;&gt;&#xA;&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/uOWxogW5Ubg?si=kPsqahnAxZGnfRUr&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen&gt;&lt;/iframe&gt;&#xA;&lt;/div&gt;&#xA;&lt;div style=&#34;height: 30px&#34;&gt;&lt;/div&gt;&#xA;&lt;p&gt;I had the pleasure of giving the keynote presentation at &lt;a href=&#34;https://www.nanog.org/events/nanog-90/agenda&#34;&gt;NANOG90&lt;/a&gt; - sharing some thoughts and lessons that we have learnt in the 10 years since we started the OpenConfig project.&lt;/p&gt;&#xA;&lt;p&gt;This was a really enjoyable presentation to put together and give. It balanced being able to look back at what we&amp;rsquo;ve learnt, and also think about some important lessons that I wanted to share with the networking community.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reimagining Network Devices</title>
      <link>https://rob.sh/post/reimagining-network-devices/</link>
      <pubDate>Wed, 12 Apr 2023 11:28:50 +0000</pubDate>
      <guid>https://rob.sh/post/reimagining-network-devices/</guid>
      <description>&lt;div style=&#34;text-align:center; margin: 10px 10px 30px 10px;&#34;&gt;&lt;em&gt;Some reflections on the development of&#xA;Software-Defined Networking, and how it has impacted the ongoing re-imagining&#xA;of network devices that OpenConfig, and associated projects has driven.&lt;/em&gt;&lt;/div&gt;&#xA;&lt;p&gt;Almost 10 years ago, there was a shift in the IP networking industry. The move&#xA;towards SDN, and its adoption by hyperscalers as a means to break apart&#xA;traditional network architectures had set the scene for disruption. The&#xA;question of “how are we using SDN?” was on the lips of vendor and telco&#xA;executives — and lead to many initiatives in the industry - both those that can&#xA;be thought of “SDN” and those that were more incremental.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NANOG 86: Emulating Network Topologies in k8s</title>
      <link>https://rob.sh/post/nanog86/</link>
      <pubDate>Tue, 11 Oct 2022 16:00:00 -0800</pubDate>
      <guid>https://rob.sh/post/nanog86/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/marcushines&#34;&gt;Marcus Hines&lt;/a&gt; and I spoke at &lt;a href=&#34;https://www.nanog.org/events/nanog-86/agenda/&#34;&gt;NANOG86&lt;/a&gt;&#xA;on some of the work that we&amp;rsquo;ve been doing related to emulating network topologies in Kubernetes, and how this relates&#xA;to improving network testability.&lt;/p&gt;&#xA;&lt;p&gt;The slides can be found &lt;a href=&#34;https://storage.googleapis.com/site-media-prod/meetings/NANOG86/4573/20221017_Shakir_Emulating_Network_Topologies_v1.pdf&#34;&gt;here&lt;/a&gt;&#xA;and there is a video on &lt;a href=&#34;https://www.youtube.com/watch?v=mAThruRU7hA&#34;&gt;YouTube&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;center&gt;&#xA;&#x9;&lt;a href=&#34;https://www.youtube.com/watch?v=mAThruRU7hA&#34;&gt;&lt;img style=&#34;width: 80%&#34; src=&#34;https://cdn.rob.sh/img/k8s-titleslide.png&#34;&gt;&lt;/a&gt;&#xA;&lt;/center&gt;</description>
    </item>
    <item>
      <title>OpenConfig Public Projects</title>
      <link>https://rob.sh/post/public-projects/</link>
      <pubDate>Sun, 17 May 2020 22:15:00 -0800</pubDate>
      <guid>https://rob.sh/post/public-projects/</guid>
      <description>&lt;p&gt;There are a number of public projects that we&amp;rsquo;ve been working on over the last few years in OpenConfig, and published from Google. It seemed like it might be worth giving a brief &amp;ldquo;hitchhikers guide” that glues together some of the different projects that we’ve published on GitHub.&lt;/p&gt;&#xA;&lt;p&gt;Of course, the initial output of OpenConfig, which has motivated much of this ecosystem is the data models — which are &lt;a href=&#34;https://github.com/openconfig/public&#34;&gt;publicly available on GitHub&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IETF98: OpenConfig Observations</title>
      <link>https://rob.sh/post/ietf98/</link>
      <pubDate>Wed, 29 Mar 2017 09:00:00 +0100</pubDate>
      <guid>https://rob.sh/post/ietf98/</guid>
      <description>&lt;p&gt;Anees Shaikh and I put together some thoughts that we shared with &lt;code&gt;rtgwg&lt;/code&gt; at&#xA;IETF 98 in Chicago. The slides are linked below.&lt;/p&gt;&#xA;&lt;div width=&#34;100%&#34;&gt;&#xA;&#x9;&lt;center&gt;&#xA;&#x9;&#x9;&lt;a href=&#34;https://cdn.rob.sh/files/slides-98-rtgwg-openconfig-modeling-and-observations-00.pdf&#34;&gt;&#xA;&#x9;&#x9;&#x9;&lt;img style=&#39;width: 60%&#39; src=&#34;https://cdn.rob.sh/img/ietf98.png&#34;&gt;&#xA;&#x9;&#x9;&lt;/a&gt;&#xA;&#x9;&lt;/center&gt;&#xA;&lt;/div&gt;</description>
    </item>
    <item>
      <title>FutureNet: Model-Driven Automation</title>
      <link>https://rob.sh/post/futurenet/</link>
      <pubDate>Thu, 01 Sep 2016 10:40:00 -0700</pubDate>
      <guid>https://rob.sh/post/futurenet/</guid>
      <description>&lt;div style=&#34;text-align:center&#34;&gt;&#xA;&lt;iframe width=&#34;560&#34; height=&#34;315&#34; src=&#34;https://www.youtube.com/embed/Irjy8AZHOEM?si=bVHWs7UWhQjENlwl&amp;amp;start=2420&#34; title=&#34;YouTube video player&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share&#34; allowfullscreen&gt;&lt;/iframe&gt;&#xA;&lt;/div&gt;&#xA;&lt;div style=&#34;height: 30px&#34;&gt;&lt;/div&gt;&#xA;&lt;p&gt;Anees Shaikh and I presented at &lt;code&gt;future:net&lt;/code&gt; talking about automation work that&#xA;we&amp;rsquo;ve been doing in OpenConfig, and I shared some of the NMS implementation&#xA;I&amp;rsquo;ve been working on recently. Slides are linked below.&lt;/p&gt;&#xA;&lt;center&gt;&#xA;&#x9;&lt;a href=&#34;https://cdn.rob.sh/files/model_driven_automation_aas_rjs.pdf&#34;&gt;&#xA;&#x9;&#x9;&lt;img style=&#39;width: 80%&#39; src=&#34;https://cdn.rob.sh/img/futurenet2016.png&#34;&gt;&#xA;&#x9;&lt;/a&gt;&#xA;&lt;/center&gt;</description>
    </item>
    <item>
      <title>OpenConfig and IETF YANG Models: Can they converge?</title>
      <link>https://rob.sh/post/215/</link>
      <pubDate>Tue, 02 Aug 2016 11:30:00 +0000</pubDate>
      <guid>https://rob.sh/post/215/</guid>
      <description>&lt;p&gt;At IETF96 in Berlin, the chairs of the NETMOD working group, and Operations Area Director (Benoit Claise) &lt;a href=&#34;https://www.ietf.org/proceedings/96/slides/slides-96-netmod-1.pdf&#34;&gt;published a statement&lt;/a&gt; to say &amp;ldquo;Models need not, and SHOULD NOT, be structured to include nodes/leaves to indicate applied configuration&amp;rdquo;. Now, this might seem a pretty innocuous statement, but it actually has a number of implications for the data models for network configuration and state that are being produced in the industry.&lt;/p&gt;&#xA;&lt;h3 id=&#34;what-is-applied-configuration&#34;&gt;What is applied configuration?&lt;/h3&gt;&#xA;&lt;p&gt;The first question to an uninitiated reader might be, what is &amp;ldquo;applied configuration&amp;rdquo;? It&amp;rsquo;s not a term that has been in the common network nomenclature - and hence does need some further explanation.  To define it, we need to look at the way that configuration is changed on a network element.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lecture at Ecole Polytechnique: Taking Network Management into the 21st Century</title>
      <link>https://rob.sh/post/214/</link>
      <pubDate>Thu, 28 Jan 2016 12:00:00 +0000</pubDate>
      <guid>https://rob.sh/post/214/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.linkedin.com/in/wmtownsley&#34;&gt;Mark Townsley&lt;/a&gt; and &lt;a href=&#34;http://perso.telecom-paristech.fr/~rougierj/My_Web_Page/Welcome.html&#34;&gt;Jean-Louis Rougier&lt;/a&gt; again invited me to come and lecture at École Polytechnique this year. Their course there focuses on analysing the success of network protocols - using the (fantastic) framework laid out in RFC5218. Given that I&amp;rsquo;d spoken about SR for the last couple of years in my lecture there, and was giving a (slightly) updated version of the SR lecture at Telecom ParisTech for JLR&amp;rsquo;s &amp;lsquo;Future Internet&amp;rsquo; course earlier in the week, I decided to shift the focus of my lecture at X this year to the management plane. Particularly, looking at some of the issues with SNMP, and how these have pushed adoption of alternative management approaches, and what this has fundamentally meant for the way that we build network management today. I then shifted to explaining what we are doing in &lt;a href=&#34;http://www.openconfig.net/&#34;&gt;OpenConfig&lt;/a&gt;, and how we might address some of those issues - again, using the framework in 5218.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenConfig Interfaces - Some Examples</title>
      <link>https://rob.sh/post/213/</link>
      <pubDate>Tue, 08 Sep 2015 23:23:00 +0000</pubDate>
      <guid>https://rob.sh/post/213/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve talked a little on this site before about what we&amp;rsquo;re trying to achieve with &lt;a href=&#34;http://www.openconfig.net&#34;&gt;OpenConfig&lt;/a&gt;. However, one of the observations that it&amp;rsquo;s easy to make is that YANG models alone don&amp;rsquo;t really achieve anything in terms of making the network more programmable. To make the network more programmable, we need to have tooling that helps us create instances of those modules, manipulate them, and then serialise the into a format that can be used to transmit data that conforms to the model to a device.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
