15:01:41 <colindixon> #startmeeting carbon release sync
15:01:41 <odl_meetbot> Meeting started Thu May  4 15:01:41 2017 UTC.  The chair is colindixon. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:01:41 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:41 <odl_meetbot> The meeting name has been set to 'carbon_release_sync'
15:01:49 <colindixon> #topic overview of status
15:02:04 <colindixon> #link https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit#gid=921315511 blocking bugs
15:09:20 <colindixon> #info colindixon thinks most of our current issues are likely tied to the fact that no bundles/features in OpenDaylight are built to be reloaded, but Karaf 4 lifecycle management by default reloads them quite a bit because we have dependency=false by default
15:15:14 <colindixon> #info the issue with that is that the plugin is hosted in karaf not in ODL, so changing the karaf plugin is a longer-term strategy than we would otherwise have to go after
15:16:08 <colindixon> #info we could (in theory) patch features.xml files in autorelease, but it would require two build passes, one to generate the feature.xml files, and other to modify them and rebuild
15:16:30 <colindixon> #info skitt says in theory, we could probably hook in just after the karaf maven plugin and do it in a single pass, but we haven't done that yet
15:17:20 <colindixon> #info skitt also says we could in theory do it in the karaf 4 distribution in integration/distribution, which would work, but would ship something different that we would test (basically just manually tweak all the features.xml files in the distribution feature repo)
15:20:22 <colindixon> #info that would have the somewhat bad property that the integration/distribution artifacts would not match nexus, that makes it a good short-term candidate for testing if this fixes most of the issues and let us know if we need to work harder on things to get it working
15:23:14 <colindixon> #info colindixon asks about prerequisite=true as well, skitt says that will likely need to be added in some places, but adding it everywhere will result in deadlocks
15:26:21 <colindixon> #info the other key question is how are we doing with Karaf 3 in Carbon, the answer is CSIT running against it probably means it's in pretty good shape
15:31:13 <colindixon> #info skitt says that Karaf 3 still has security support from apache, but that doesn't totally save us as it could be that karaf 3 stops us from pulling in a dependency that would be critical for us, but doesn't matter to Karaf
15:34:11 <colindixon> #info lori says that he's seeing issues that look like "Unable to start… aaa …" when testing lispflowmapping
15:37:28 <colindixon> #link colindixon notes that we have a bug tracking something like this https://bugs.opendaylight.org/show_bug.cgi?id=8373
15:38:19 <colindixon> #info lori points out that he ran into stack overflow errors early in the Karaf 4 testing and he thought it was because of dependency=true, but it might be because of prerequisite=true
15:40:24 <colindixon> #info skitt says his hope is that won't be the case for dependency=true, it was more for prerequisite=true, but we'll see
15:40:48 <colindixon> #info katie asks if this will eventually require changes in all projects, skitt  and colindixon say they really hope not and shouldn't
15:44:40 <colindixon> #endmeeting