<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:11 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>[CONTROLLER-1300] Allow user upgrade from Helium to Lithium with user config</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1300</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;This is broader issue than just controller&apos;s config subsystem, but in general there is no documented upgrade procedure for a user to take a running Helium controller and upgrade it to a running Lithium controller (possibly shutting it down in the process).&lt;/p&gt;

&lt;p&gt;Some discussion has happened on the mailing lists:&lt;br/&gt;
&lt;a href=&quot;https://lists.opendaylight.org/pipermail/tsc/2015-May/003021.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/tsc/2015-May/003021.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;On the MD-SAL interest call:&lt;br/&gt;
&lt;a href=&quot;https://meetings.opendaylight.org/opendaylight-meeting/2015/md_sal_interest_call/opendaylight-meeting-md_sal_interest_call.2015-05-05-16.02.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://meetings.opendaylight.org/opendaylight-meeting/2015/md_sal_interest_call/opendaylight-meeting-md_sal_interest_call.2015-05-05-16.02.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And during the TSC meeting:&lt;br/&gt;
&lt;a href=&quot;https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-07-17.01.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-07-17.01.html&lt;/a&gt;&lt;/p&gt;


&lt;p&gt;The highest order bits to start discussion were:&lt;br/&gt;
There were differences of opinion in how exactly to handle it ranging from:&lt;/p&gt;

&lt;p&gt;1.) It should be something automatic that happens in the actual ODL project&lt;br/&gt;
code so that you can just, shut down the controller, expand the new zip&lt;br/&gt;
file into the same place, run it again, and it will work and have all your&lt;br/&gt;
old config persisted.&lt;br/&gt;
2.) It should be done out-of-band with an upgrade script.&lt;br/&gt;
3.) We should just document the process people have to go through.&lt;br/&gt;
4.) We shouldn&apos;t do anything.&lt;/p&gt;

&lt;p&gt;It was noted that a lot of this will have to be done on a per-project basis&lt;br/&gt;
since each project has different config and different data.&lt;/p&gt;

&lt;p&gt;My personal take is that #3 is the bare minimum and we&apos;ve asked for&lt;br/&gt;
information about that since the Hydrogen release notes &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; and I think at&lt;br/&gt;
least documenting what users should expect (and ideally providing them a&lt;br/&gt;
way to move without losing all of their configuration) is probably a really&lt;br/&gt;
good idea.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25854">CONTROLLER-1300</key>
            <summary>Allow user upgrade from Helium to Lithium with user config</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="colindixon">Colin Dixon</reporter>
                        <labels>
                    </labels>
                <created>Fri, 8 May 2015 18:41:49 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:41 +0000</updated>
                            <resolved>Tue, 24 Nov 2015 17:55:56 +0000</resolved>
                                    <version>Post-Helium</version>
                                                    <component>config</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="50576" author="colin@colindixon.com" created="Fri, 8 May 2015 18:46:41 +0000"  >&lt;p&gt;As Tony pointed out during the TSC meeting, the first thing to do would be to see if we can just upgrade the container with no config persistence. That is, can we install Helium, boot it, do something, shut it down, install Lithium over it, delete config data, re-launch and see if it still works.&lt;/p&gt;</comment>
                            <comment id="50577" author="tpantelis" created="Mon, 11 May 2015 14:30:38 +0000"  >&lt;p&gt;Another config file that needs to be upgraded is the configuration/initial/akka.conf for clustering. There shouldn&apos;t be anything that&apos;s incompatible but a couple knobs have been changed to improve things. Also a new message serializer has been added where a certain uncommon code path will bork w/o it.&lt;/p&gt;

&lt;p&gt;The seed-nodes and role sections are what users would change so these would need to be reapplied on top of the new akka.conf, either manually or with a script.&lt;/p&gt;

&lt;p&gt;In order to get the new akka.conf though, a user would have to move off the current one and start the controller to get the feature to lay down the new one.&lt;/p&gt;</comment>
                            <comment id="50578" author="colin@colindixon.com" created="Tue, 26 May 2015 16:38:46 +0000"  >&lt;p&gt;@Tony points out that if we just copy the zip over the existing installed distribution, we&apos;ll roughly double the size of the installation since we&apos;ll have two copies of most bundles. I will open a second bug to track that, but it should be low priority since we don&apos;t have an installation process anyway.&lt;/p&gt;</comment>
                            <comment id="50579" author="colin@colindixon.com" created="Fri, 29 May 2015 01:09:22 +0000"  >&lt;p&gt;The solution to BUG3377 should help in at least understanding what data models will/won&apos;t be compatible between Helium and Lithium.&lt;/p&gt;</comment>
                            <comment id="50580" author="colin@colindixon.com" created="Tue, 18 Aug 2015 16:44:37 +0000"  >&lt;p&gt;Tony also points out that renaming features may also cause issues.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="25893">CONTROLLER-1339</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3160</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=3160]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10305"><![CDATA[Improvement]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10325"><![CDATA[Lithium-2]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02ppz:</customfieldvalue>

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