<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to implement SHARED route policy in NSO? in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205222#M8697</link>
    <description>&lt;P&gt;The issue here is you are probaly using the IOS-XR CLI NED that models a route policy as a name and a single leaf with the policy definition. If the policy definition has a structure and different services for example can add a 'match' in the policy, then the way to do this is to have a service dedicated to managing the route policy. You model that service as you need, for exampl with a leaf-list of matches. The create callback of your services goes through the list of matches and build the required policy string.&lt;/P&gt;
&lt;P&gt;Then the services that require a match to be added, specify that match in the template by adding a match under the service that manages the route policy. That's an example of the stacked services pattern, where the template of a service is specifying what it's intent is, in terms of a lower level service.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Oct 2024 14:31:41 GMT</pubDate>
    <dc:creator>snovello</dc:creator>
    <dc:date>2024-10-08T14:31:41Z</dc:date>
    <item>
      <title>How to implement SHARED route policy in NSO?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205196#M8696</link>
      <description>&lt;P&gt;Hi, I want to create one shared route policy&amp;nbsp; that multiple services can use. With my current implementation, this shared policy gets rewritten every time, which is not what I want. I want it to be extended with each request instead. Even if I can manage shared RPL to be extended ,&amp;nbsp;I think the other connected services will get out of sync. Do you have any ideas or suggestions on how to do this?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 13:29:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205196#M8696</guid>
      <dc:creator>Elvin J</dc:creator>
      <dc:date>2024-10-08T13:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement SHARED route policy in NSO?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205222#M8697</link>
      <description>&lt;P&gt;The issue here is you are probaly using the IOS-XR CLI NED that models a route policy as a name and a single leaf with the policy definition. If the policy definition has a structure and different services for example can add a 'match' in the policy, then the way to do this is to have a service dedicated to managing the route policy. You model that service as you need, for exampl with a leaf-list of matches. The create callback of your services goes through the list of matches and build the required policy string.&lt;/P&gt;
&lt;P&gt;Then the services that require a match to be added, specify that match in the template by adding a match under the service that manages the route policy. That's an example of the stacked services pattern, where the template of a service is specifying what it's intent is, in terms of a lower level service.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 14:31:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205222#M8697</guid>
      <dc:creator>snovello</dc:creator>
      <dc:date>2024-10-08T14:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement SHARED route policy in NSO?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205577#M8698</link>
      <description>&lt;P&gt;Thanks for the answer, could you please show example code?&lt;/P&gt;</description>
      <pubDate>Wed, 09 Oct 2024 07:04:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5205577#M8698</guid>
      <dc:creator>Elvin J</dc:creator>
      <dc:date>2024-10-09T07:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to implement SHARED route policy in NSO?</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5206996#M8705</link>
      <description>&lt;P&gt;After some conversation with Elvin, we now have this small NSO example package.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://github.com/StefanoNovello/shared-route-policy/" target="_blank"&gt;https://github.com/StefanoNovello/shared-route-policy/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2024 07:18:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/how-to-implement-shared-route-policy-in-nso/m-p/5206996#M8705</guid>
      <dc:creator>snovello</dc:creator>
      <dc:date>2024-10-11T07:18:51Z</dc:date>
    </item>
  </channel>
</rss>

