17:03:11 <Madhu> #startmeeting TWS
17:03:11 <odl_meetbot> Meeting started Mon Jun  9 17:03:11 2014 UTC.  The chair is Madhu. Information about MeetBot at http://ci.openstack.org/meetbot.html.
17:03:11 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:03:11 <odl_meetbot> The meeting name has been set to 'tws'
17:03:17 <tbachman> regXboi: no networkstatic here ;)
17:03:32 <regXboi> let's not start that again
17:03:36 <Madhu> anyone volunteering for being chair ?
17:03:36 <tbachman> lol
17:03:43 <Madhu> #chair phrobb tbachman
17:03:43 <odl_meetbot> Current chairs: Madhu phrobb tbachman
17:03:45 <Madhu> regXboi: ?
17:03:57 <regXboi> not today thanks
17:04:02 <regXboi> I'm only half listening
17:04:28 <tbachman> #topic ODL Autorelease tool and process presentation
17:04:42 <Madhu> #info Giovanni is taking the lead.
17:04:54 <Madhu> regXboi: thanks sir
17:04:56 <tbachman> #info autorelease is a process that tries to streamline the release process
17:06:19 <Madhu> #info autorelease process is required for a better release process due to all the issues that we faced during Hydrogen release.
17:07:23 <Madhu> #info slides : https://wiki.opendaylight.org/images/8/84/OpenDaylight_AutoRelease_TWS_Presentation.ppt
17:07:23 <tbachman> #info one such issue is inter-project dependencies
17:08:56 <tbachman> #info edwarnicke asks who was there for the “Monday of Doom” for the Hydrogen release.
17:09:07 <tbachman> #info rovarga notes it was Monday and Tuesday
17:09:18 <tbachman> lol
17:09:44 <tbachman> #info The current release process has too much manual processing
17:09:45 <Madhu> #info is it really 2 days of doom.. it went on forever and we are still feeling the repercussions ;)
17:10:59 <edwarnicke> #info "As God as my witness, Monday will never happen again!" ;)
17:11:47 <tbachman> #info there were two categories of issues: versions-maven-plugin didn’t reliably do what was needed, and the Maven “out-of-the-box’ release process is complex and requires access to external git repos
17:13:49 <Madhu> #info the Giovanni's slide (https://wiki.opendaylight.org/images/8/84/OpenDaylight_AutoRelease_TWS_Presentation.ppt) is verbose enough in explaining the release-plugin issues :)
17:14:00 <tbachman> lol
17:14:08 <tbachman> fair enough :)
17:14:24 <Madhu> tbachman: pls don't stop your awesome work
17:14:28 <Madhu> am just being lazy :)
17:14:28 <tbachman> lol
17:14:38 <tbachman> no need to repeat a #linkfor the slides
17:14:59 <tbachman> #link ttps://wiki.opendaylight.org/images/8/84/OpenDaylight_AutoRelease_TWS_Presentation.ppt) <== slides for presentation
17:18:33 <tbachman> #info edwarnicke asks why “git short SHA” is used in the versioning?
17:19:59 <tbachman> #info GiovanniMeo says that this makes it easy to identify a particular artifact
17:21:05 <tbachman> #info all the projects that get put in the same run will have the same day, month, year, etc., but will have a unique SHA
17:22:50 <tbachman> #info We could have used literal forms of identification, but they run the risk of ambiguity
17:23:21 <tbachman> #info rovarga asks if the git short SHA can be captured within the artifcats
17:23:37 <tbachman> #info GiovanniMeo says that’s already available in the pom.xml
17:24:00 <tbachman> #info rovarga asks if this can be captured into the actual jar.
17:24:18 <tbachman> #info GiovanniMeo says this is possible, and we can look to Eclipse as a reference
17:24:49 <tbachman> #info In the manifest of the .jar, the eclipse project includes a SHA for each single file of source used to create this artificat.
17:24:59 <tbachman> #info they also sign with GPG each of these signatures
17:27:50 * edwarnicke is going to be quite for a while... curious to hear others thoughts :)
17:30:06 * edwarnicke is laughing at the optimism of the uranium release ;)
17:30:43 * tbachman can’t help but think of an old Benny Hill skit
17:30:58 <edwarnicke> tbachman: Which one?
17:31:18 <tbachman> #info regXboi notes that we’re already doing a
17:31:22 <tbachman> ugh
17:31:39 <tbachman> #info regXboi notes that we’re already using a “-n” for stable branches
17:34:45 <tbachman> #info discussion on human-readable vs. SHA defined identifiers
17:35:11 <tbachman> #info humans find it easier to have the -n conventions, but SHAs are the most specific for what an artificat is
17:37:17 <edwarnicke> So... random half baked idea to consider... x.y.z-Hydrogen.n-v{timestamp} ?
17:37:48 <edwarnicke> (and then we could also do x.y.z-Helium.0-v{timestamp} )
17:38:20 <tbachman> #info Madhu points out that weekly releases aren’t necesarrily stable
17:40:31 <regXboi> is it time for a time-check?
17:40:42 <Madhu> regXboi: thanks :)
17:41:16 <cdub> it's a released snapshot ;)
17:41:39 <edwarnicke> cdub: In some sense, yes... God save us from the semantic pot holes ;)
17:41:46 <Madhu> ya. its a released snapshot ;)
17:41:46 <regXboi> I say, let's deploy this as it is... we can change the artifact names later :)
17:41:55 <regXboi> on the stable branch
17:44:32 <Madhu> #info This brings in the weekly release process in place & does not guarantee Stability of the artificats.
17:45:07 <Madhu> #info regXboi requests for making it obvious by adding WEEKLY in the artifact name
17:45:23 <regXboi> Madhu: -WEEKLY- was what I was thinking
17:45:47 <Madhu> #info correction "-WEEKLY-" :)
17:48:12 <tbachman> #info GiovanniMeo will complete the rest of his presentation in Tomorrow’s MD-SAL call
17:50:14 <Madhu> #info Raghu clarifies the point that the Surekha's parent pom work and Giovanni's automated release process are complementary. Both these work are important & the version cleanup is needed.
17:50:27 <Madhu> #topic Automated Robot Integration test to verify FlowMod installation
17:51:10 <Madhu> Thanks GiovanniMeo sorry about spilling over to tomorrow's call
17:51:35 <tbachman> #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group starting link for Integration team
17:52:38 <regXboi> #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Download_and_Run_System_Test
17:52:54 <tbachman> #info first is to clone the git repo
17:53:19 <tbachman> #info There are now two levels in their test suties folder
17:53:35 <tbachman> #info first level is main suite for a given distro (base, VTN, etc.)
17:53:46 <tbachman> #info second level is for the sub-suties that run within the main suite
17:53:58 <cdub> someone is backing up
17:54:35 <tbachman> lol
17:56:03 <tbachman> #info Madhu asks whether the first level should be something like “virtualization”, and the second level should be something lk “VTN”
17:57:25 <tbachman> #info Testing at the first level means that a controller instance is launced with a given configuration
17:57:39 <tbachman> #info Tesitng at the second level can be done with an already-launched controller
17:58:03 <tbachman> #info Luis notes that they haven’t yet decided what this will look like for the Helium release.
18:02:20 <tbachman> #info the “ha” top level test dir isn’t yet ready (requires some LF infra support)
18:05:31 <tbachman> #info test group is working to get all of the test cases documented in testopia
18:09:39 <tbachman> #info every time a robot test is run, 3 reports are generated. Reports are easily viewed from a web browser
18:10:03 <tbachman> #info system tests using robot framework all run outside the controller, using REST
18:11:03 <tbachman> #info the test framework is currently in use in Jenkins
18:11:43 <CASP3R> #link https://wiki.opendaylight.org/view/CrossProject:Integration_Group:FlowMod_Test
18:13:36 <maberg> Integration hackfest https://lists.opendaylight.org/pipermail/integration-dev/2014-May/001148.html
18:15:44 <maberg> #link https://lists.opendaylight.org/pipermail/integration-dev/2014-May/001148.html Integration hackfest
18:19:15 <tbachman> #info team is currently testing with OVS, but is working with LF infra folks to add CPqD
18:20:41 <tbachman> #endmeeting