========================== #opendaylight-meeting: TWS ========================== Meeting started by Madhu at 17:03:11 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2014/tws/opendaylight-meeting-tws.2014-06-09-17.03.log.html . Meeting summary --------------- * ODL Autorelease tool and process presentation (tbachman, 17:04:28) * Giovanni is taking the lead. (Madhu, 17:04:42) * autorelease is a process that tries to streamline the release process (tbachman, 17:04:56) * autorelease process is required for a better release process due to all the issues that we faced during Hydrogen release. (Madhu, 17:06:19) * slides : https://wiki.opendaylight.org/images/8/84/OpenDaylight_AutoRelease_TWS_Presentation.ppt (Madhu, 17:07:23) * one such issue is inter-project dependencies (tbachman, 17:07:23) * edwarnicke asks who was there for the “Monday of Doom” for the Hydrogen release. (tbachman, 17:08:56) * rovarga notes it was Monday and Tuesday (tbachman, 17:09:07) * The current release process has too much manual processing (tbachman, 17:09:44) * is it really 2 days of doom.. it went on forever and we are still feeling the repercussions ;) (Madhu, 17:09:45) * "As God as my witness, Monday will never happen again!" ;) (edwarnicke, 17:10:59) * 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 (tbachman, 17:11:47) * 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 :) (Madhu, 17:13:49) * LINK: ttps://wiki.opendaylight.org/images/8/84/OpenDaylight_AutoRelease_TWS_Presentation.ppt) <== slides for presentation (tbachman, 17:14:59) * edwarnicke asks why “git short SHA” is used in the versioning? (tbachman, 17:18:33) * GiovanniMeo says that this makes it easy to identify a particular artifact (tbachman, 17:19:59) * all the projects that get put in the same run will have the same day, month, year, etc., but will have a unique SHA (tbachman, 17:21:05) * We could have used literal forms of identification, but they run the risk of ambiguity (tbachman, 17:22:50) * rovarga asks if the git short SHA can be captured within the artifcats (tbachman, 17:23:21) * GiovanniMeo says that’s already available in the pom.xml (tbachman, 17:23:37) * rovarga asks if this can be captured into the actual jar. (tbachman, 17:24:00) * GiovanniMeo says this is possible, and we can look to Eclipse as a reference (tbachman, 17:24:18) * In the manifest of the .jar, the eclipse project includes a SHA for each single file of source used to create this artificat. (tbachman, 17:24:49) * they also sign with GPG each of these signatures (tbachman, 17:24:59) * regXboi notes that we’re already doing a (tbachman, 17:31:18) * regXboi notes that we’re already using a “-n” for stable branches (tbachman, 17:31:39) * discussion on human-readable vs. SHA defined identifiers (tbachman, 17:34:45) * humans find it easier to have the -n conventions, but SHAs are the most specific for what an artificat is (tbachman, 17:35:11) * Madhu points out that weekly releases aren’t necesarrily stable (tbachman, 17:38:20) * This brings in the weekly release process in place & does not guarantee Stability of the artificats. (Madhu, 17:44:32) * regXboi requests for making it obvious by adding WEEKLY in the artifact name (Madhu, 17:45:07) * correction "-WEEKLY-" :) (Madhu, 17:45:47) * GiovanniMeo will complete the rest of his presentation in Tomorrow’s MD-SAL call (tbachman, 17:48:12) * 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. (Madhu, 17:50:14) * Automated Robot Integration test to verify FlowMod installation (Madhu, 17:50:27) * LINK: https://wiki.opendaylight.org/view/CrossProject:Integration_Group starting link for Integration team (tbachman, 17:51:35) * LINK: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Download_and_Run_System_Test (regXboi, 17:52:38) * first is to clone the git repo (tbachman, 17:52:54) * There are now two levels in their test suties folder (tbachman, 17:53:19) * first level is main suite for a given distro (base, VTN, etc.) (tbachman, 17:53:35) * second level is for the sub-suties that run within the main suite (tbachman, 17:53:46) * Madhu asks whether the first level should be something like “virtualization”, and the second level should be something lk “VTN” (tbachman, 17:56:03) * Testing at the first level means that a controller instance is launced with a given configuration (tbachman, 17:57:25) * Tesitng at the second level can be done with an already-launched controller (tbachman, 17:57:39) * Luis notes that they haven’t yet decided what this will look like for the Helium release. (tbachman, 17:58:03) * the “ha” top level test dir isn’t yet ready (requires some LF infra support) (tbachman, 18:02:20) * test group is working to get all of the test cases documented in testopia (tbachman, 18:05:31) * every time a robot test is run, 3 reports are generated. Reports are easily viewed from a web browser (tbachman, 18:09:39) * system tests using robot framework all run outside the controller, using REST (tbachman, 18:10:03) * the test framework is currently in use in Jenkins (tbachman, 18:11:03) * LINK: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:FlowMod_Test (CASP3R, 18:11:43) * LINK: https://lists.opendaylight.org/pipermail/integration-dev/2014-May/001148.html Integration hackfest (maberg, 18:15:44) * team is currently testing with OVS, but is working with LF infra folks to add CPqD (tbachman, 18:19:15) Meeting ended at 18:20:41 UTC. People present (lines said) --------------------------- * tbachman (50) * Madhu (20) * regXboi (8) * edwarnicke (7) * odl_meetbot (4) * maberg (2) * cdub (2) * CASP3R (1) * phrobb (0) Generated by `MeetBot`_ 0.1.4