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/GBP-51 groupbasedpolicy <p>This is a check of the yang. not an implementation of this functionality.</p> <p>Operating System: All<br/> Platform: All</p> GBP-51

Ensure SFC Yang models are complete such that SF can leverage them to modify metadata

Bug Resolved Won't Do Thomas Bachman Keith Burns Wed, 20 May 2015 15:53:44 +0000 Mon, 15 Jun 2015 04:35:05 +0000 Mon, 15 Jun 2015 04:35:05 +0000 unspecified General Wed, 27 May 2015 00:00:00 +0000 0 1 <p>Thanks to Andrej Kincel who pointed me to the right place in the code. The service-function.yang model has a separate container/list for Service Function state:</p> <p> container service-functions-state {<br/> description<br/> "This container hold operational state for all service<br/> functions";<br/> config false;<br/> list service-function-state {<br/> description<br/> "This list holds operational data for all service functions<br/> in the domain";<br/> key "name";<br/> leaf name </p> { type string; description "the name of the service function"; } <p> uses sfc-ss:service-statistics-group </p> { description "Global Service Function statistics"; } <p> list sf-service-path {<br/> key "name";<br/> leaf name </p> { type string; description "The name of the Service Path"; } <p>etc.</p> <p>The code updates the sf-service-path in the operational data store using the RSP name. The RSP contains:</p> <p> list rendered-service-path {<br/> description<br/> "A list that holds operational data for all RSPs in the<br/> domain";<br/> key "name";<br/> leaf name </p> { type string; description "The name of this rendered function path. This is the same name as the associated SFP"; } <p>....<br/> leaf context-metadata </p> { type sfc-md:context-metadata-ref; description "The name of the associated context metadata"; } <p> leaf variable-metadata </p> { type sfc-md:variable-metadata-ref; description "The name of the associated variable metadata"; } <p>It's not ideal, as the state is kept in a separate list, rather than contained within the SF itself. In short, it means that the SF has to look it's own name up in the service-function-state list, get the service-path name, and then look up the rendered-service-path by name to get the metadata fields.</p> Development External issue ID 3307 External issue URL ODL SR Target Milestone Priority Rank 0|i03567: