<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:42:19 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[TRNSPRTPCE-123] Automatic spanloss measurement</title>
                <link>https://jira.opendaylight.org/browse/TRNSPRTPCE-123</link>
                <project id="10178" key="TRNSPRTPCE">transportpce</project>
                    <description>&lt;p&gt;This is related to&#160;&lt;a href=&quot;https://jira.opendaylight.org/browse/TRNSPRTPCE-95&quot; title=&quot;Create File for OMS population&quot; class=&quot;issue-link&quot; data-issue-key=&quot;TRNSPRTPCE-95&quot;&gt;&lt;del&gt;TRNSPRTPCE-95&lt;/del&gt;&lt;/a&gt;,&#160;where it is only mentioned that spanloss is needed in the OMS attribute in the network topology for OSNR calculation. But spanloss is also read from the ROADM device when calculating and setting the power in PowerMgmt.java. Currently, it seems that a spanloss measurement has to be triggered manually through RESTCONF API in order to write the spanloss to the device. Otherwise&#160;power setup&#160;will fail. So I think automatic spanloss measurement when a ROADM-to-ROADM link is discovered is needed even without OSNR calculation.&lt;/p&gt;</description>
                <environment></environment>
        <key id="31691">TRNSPRTPCE-123</key>
            <summary>Automatic spanloss measurement</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="1" iconUrl="https://jira.opendaylight.org/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="ojnas">Jonas M&#229;rtensson</reporter>
                        <labels>
                    </labels>
                <created>Fri, 17 May 2019 09:02:44 +0000</created>
                <updated>Tue, 7 Sep 2021 15:40:17 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="66807" author="orenais" created="Tue, 21 May 2019 08:44:22 +0000"  >&lt;p&gt;We still in process for checking and changing part of the algorithm. Standard behavior shall be : attenuation  associated with a span is provided through RESTCONF interface. This is the attenuation stored in a specific database. It is then stored in topology as span loss-base (span-attribute). Then during discovery of the link, the controller calculates the span-loss from PMs (inputPowerNode(N)-outputPowerNode(N-1). Then it populates topology with this calculated value (spanloss-current) and refreshes the value on the ots-interfaces of the device. &lt;/p&gt;</comment>
                            <comment id="66809" author="ojnas" created="Tue, 21 May 2019 12:01:32 +0000"  >&lt;p&gt;I don&apos;t fully understand the proposed behavior. When you say &quot;attenuation associated with a span is provided through RESTCONF interface&quot; it sounds like something coming from an external system like the operator&apos;s fiber database. I think the&#160;engineered-spanloss attribute in the network topology model is meant for such pre-deployment data. In my understanding from the network model whitepaper and descriptions in the YANG files, the spanloss-base attribute should be based on measurement (or calculation based on PMs) during degree turn-up (or link discovery). The spanloss-current attribute should be updated periodically if auto-spanloss is set to true.&lt;/p&gt;</comment>
                            <comment id="66810" author="orenais" created="Tue, 21 May 2019 12:58:24 +0000"  >&lt;p&gt;You are right. Sorry, we participated to that modeling but it is a bit far away.I made a confusion. The value coming from data base is used to populate engineered-spanloss. Spanloss base is the value that is measured first time the link is discovered. Span-loss current is associated with last measured value.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>TRNSPRTPCE-500</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03nv3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>