10 min | Call plan | All |
|
Guidelines | All | No updates this call (22 Nov) Kam reported the status of the guidelines documents: IISOMI Deliverables
| |
40 min | Use of "Current" in xPath | Deferred to next call on November 29
| |
leafref on non-config data | Thorsten Heinze | Thorsten presented an issue that they encounted: In UML: We define a read-only Class (e.g. TransmissionMode) that hold several attributes (e.g. center frequency, channel bandwidth, modulation) We reference this datatype in read-only classes (Capability) for vendors to list the combinations of values, which are supported by the hardware We reference this datatype in read-write classes (Configuration) for operators to select one of the supported combinations of values It looks like this in the class diagram (unfortunately the referencing _attributes in the Capability and Configuration classes are not shown in Papyrus): The “shared” associations from the Configuration class to the TransmissionMode are very well translated into leafref statements in the YANG. But unfortunately, we get the following error messages during compiling the resulting YANG: … error: the node is config, but refers to a non-config leaf 'transmission-mode-name' in module … We would have thought that this is a very reasonable appliance of leafref, and are surprised about the error message. Do you have an idea about what we have to correct in the YANG, respectively the UML? Note that the error message doesn’t show up, when the leafref is complemented with a require-instance==false statement, but we are not sure about the side effect of this amendment. Bernd Zeuner gave the following link on "require-instance false" when pulling leafref definitions from grouping. Discussion resumed on the Nov. 22 IISOMI call: Thorsten Heinzeconfirms that the issue can be solved thanks to this "require-instance false": leaf transmission-mode-min { The above Yang definitions should be the result of UML to Yang translation of "shared association to read-only list", but currently the tool is not generating the "must" statement.
| |
update UML to Yang Mapping Guidelines with respect to leafref on non-config data | UML starting point: A shared association in UML, to a read-only list of object-classes. From a functional point of view, the user should be able to select an entry from y read-only list. An example would be to select a certain behavior defined by hardware capabilities. Yang solution: In order to avoid yang validations for such case, the yang instance validation can be suppressed by adding the "require-instance: false;" statement to the "leafref" statement and in addition to verify the existence of the instance by adding a "must" statement to the "leaf" statement. ``` ``` To be discussed: Where to add such section in TR531? | ||
5 min | Agenda of next call | All |
|