<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:43:45 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-674] Support parameterization of hard-coded SIMS attributes</title>
                <link>https://jira.opendaylight.org/browse/TRNSPRTPCE-674</link>
                <project id="10178" key="TRNSPRTPCE">transportpce</project>
                    <description>&lt;p&gt;Certain node attributes are hard-coded into test_utils.py and test_utils_rfc8040.py, including username (openroadm), password (openroadm), and host (127.0.0.1). To facilitate using the existing tox testing framework for physical devices, we propose to add support for username, password, and host as additional optional key-value pairs in the simulators.py file.&lt;/p&gt;

&lt;p&gt;If the new key-value pairs are not present in simulators.py, the normal defaults will apply. In order to take advantage of this new feature, the person doing the testing of physical devices would need to edit the simulators.py file by hand.&lt;/p&gt;

&lt;p&gt;E.g.:&lt;/p&gt;

&lt;p&gt;&lt;tt&gt;SIMS = {&lt;/tt&gt;&lt;tt&gt;&#160; &#160; (&apos;xpdra&apos;, &apos;1.2.1&apos;): {&apos;port&apos;: &apos;17830&apos;, &apos;configfile&apos;: &apos;oper-XPDRA.xml&apos;, &apos;logfile&apos;: &apos;xpdra-121.log&apos;, &apos;username&apos;: &apos;person123&apos;, &apos;password&apos;: &apos;MyPassword&apos;, &apos;host&apos;: &apos;192.168.5.55&apos;},&lt;/tt&gt;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Additionally, if the start_sims function sees that a particular node has a host override specified in the SIM dictionary, it will skip starting a Honeynode instance for it. This would potentially allow for mixed physical/honeynode test environments.&lt;/p&gt;</description>
                <environment></environment>
        <key id="35905">TRNSPRTPCE-674</key>
            <summary>Support parameterization of hard-coded SIMS attributes</summary>
                <type id="10103" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10311&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="10001" iconUrl="https://jira.opendaylight.org/" description="">In Review</status>
                    <statusCategory id="4" key="indeterminate" colorName="yellow"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="nathan.ellsworth">Nathan Ellsworth</assignee>
                                    <reporter username="nathan.ellsworth">Nathan Ellsworth</reporter>
                        <labels>
                    </labels>
                <created>Thu, 16 Jun 2022 08:11:15 +0000</created>
                <updated>Tue, 16 Jan 2024 13:59:11 +0000</updated>
                                                            <fixVersion>unspecified</fixVersion>
                                        <due>Thu, 30 Jun 2022 00:00:00 +0000</due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                    <workratio workratioPercent="0"/>
                                    <progress percentage="0">
                                    <originalProgress>
                                                    <row percentage="100" backgroundColor="#89afd7"/>
                                            </originalProgress>
                                                    <currentProgress>
                                                    <row percentage="0" backgroundColor="#51a825"/>
                                                    <row percentage="100" backgroundColor="#ec8e00"/>
                                            </currentProgress>
                            </progress>
                                    <aggregateprogress percentage="0">
                                    <originalProgress>
                                                    <row percentage="100" backgroundColor="#89afd7"/>
                                            </originalProgress>
                                                    <currentProgress>
                                                    <row percentage="0" backgroundColor="#51a825"/>
                                                    <row percentage="100" backgroundColor="#ec8e00"/>
                                            </currentProgress>
                            </aggregateprogress>
                                    <timeoriginalestimate seconds="288000">2 weeks</timeoriginalestimate>
                            <timeestimate seconds="288000">2 weeks</timeestimate>
                                        <comments>
                            <comment id="71204" author="gthouenon" created="Thu, 16 Jun 2022 12:47:22 +0000"  >&lt;p&gt;The idea is good.&lt;br/&gt;
To prevent from having to modify simulators.py file each time you have to use specific real equipment, it would be worth configuring once the simulators.py file with a python function (os.getenv) that will read environment variables as for example XPDRA_USER, XPDRA_PASSWORD, XPDRA_HOST..., and test_utils.mount_device with the reading of the simulators dictionary.&lt;br/&gt;
If the env variable is not set, the corresponding key will not exist in the dictionary and the test_utils.start_sims() will start the sims.&lt;br/&gt;
On the other hand, if the env variable is set, the key will exist, the corresponding sims will not start, and the mount_device function could use the dict.get(key, default) to either use the value setted in the env variable, or the default value to be used for the sims.&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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i042xy:zzzzei</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10001" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="42">Sprint 28</customfieldvalue>
    <customfieldvalue id="43">Sprint 29</customfieldvalue>
    <customfieldvalue id="44">Sprint 30</customfieldvalue>
    <customfieldvalue id="45">Sprint 31</customfieldvalue>
    <customfieldvalue id="46">Sprint 32</customfieldvalue>
    <customfieldvalue id="47">Sprint 33</customfieldvalue>
    <customfieldvalue id="48">Sprint 34</customfieldvalue>

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