https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-308 mdsal <p>Given  the model</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> leaf role-set { type leafref { path <span class="code-quote">"/rpol:routing-policy/rpol:defined-sets/role-sets/role-set/role-set-name"</span>; } description <span class="code-quote">"References a defined neighbor roles set"</span>; }</pre> </div></div> <p>when reading from DS and calling getRoleSet()</p> <p>where</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> /** * References a defined neighbor roles set * * * * @<span class="code-keyword">return</span> &lt;code&gt;java.lang.<span class="code-object">String</span>&lt;/code&gt; &lt;code&gt;roleSet&lt;/code&gt;, or &lt;code&gt;<span class="code-keyword">null</span>&lt;/code&gt; <span class="code-keyword">if</span> not present */ java.lang.<span class="code-object">String</span> getRoleSet();</pre> </div></div> <p> </p> <p>I was not able to find a tool or way to do a direct conversion from this string </p> <p>to an InstanceIdentifier.</p> MDSAL-308

leaf-ref to InstanceIdentifier

Improvement Medium Resolved Won't Do Unassigned Claudio David Gasparini Mon, 5 Feb 2018 12:41:40 +0000 Thu, 28 Oct 2021 20:14:42 +0000 Thu, 28 Oct 2021 20:14:42 +0000 Binding runtime 0 3 <p>This feature could be properly provided by mdsal runtime of binding v2 after <a href="https://jira.opendaylight.org/browse/MDSAL-17" title="Simplify InstanceIdentifer creation" class="issue-link" data-issue-key="MDSAL-17"><del>MDSAL-17</del></a>.<br/> but the Instance Identifier only identifies a specific TreeNode in the data tree, not a leaf node.</p> <p>This boils down to resolving leafref types, which really is an XPath query on the data store.</p> <p>Codegen API contract should change, so that it returns an XPath query (which can be limited in terms of InstanceIdentifier wildcards?). That query then needs to be run against the datastore.</p> <p>In this particular instance we want the reference to come from:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> grouping role-set { description "Data definition for a list of Odl Bgp roles which are matched as part of a policy"; list role-set { key role-set-name; description "List of the defined role sets"; leaf role-set-name { type string; description "name / label of the role set -- this is used to reference the set in match conditions"; } leaf-list role { type rib:peer-role; description "List of role expressions that are part of the set"; } } } </pre> </div></div> <p>From this follows, that if you want a (Yang)InstanceIdentifier, you want additional proof as to what the role set entry is. Why do we need this?</p> <p>If the need is to find the role-set, the returned string is what you need to construct RoleSetKey with to point to what the correlation you are making with a particular instantiation.</p> <p>If there is a gap that needs to be addressed, please reopen.</p> Relates MDSAL-17 Development Rank 0|i03a0n: