========================== #opendaylight-meeting: tcc ========================== Meeting started by colindixon at 16:59:14 UTC. The full logs are available at http://meetings.opendaylight.org/opendaylight-meeting/2015/tcc/opendaylight-meeting-tcc.2015-06-04-16.59.log.html . Meeting summary --------------- * agenda bashing and roll call (colindixon, 16:59:20) * colindixon (colindixon, 16:59:23) * edwarnicke (edwarnicke, 16:59:50) * LINK: https://wiki.opendaylight.org/index.php?title=TSC:Main&oldid=30884#Agenda the agenda, fixed in history (colindixon, 17:00:01) * Chris Wright (cdub, 17:00:25) * chris price partially (ChrisPriceAB, 17:00:27) * dlenrow (dlenrow, 17:00:42) * Casey Cain (odlcasey, 17:01:45) * LINK: https://meetings.opendaylight.org/opendaylight-meeting/2015/tsc/opendaylight-meeting-tsc.2015-05-28-16.59.html Minutes from last week’s meeting (tbachman, 17:02:10) * jmedved (jmedved, 17:05:06) * we’re unfortunately short a chair — Topic is now Events (tbachman, 17:07:45) * phrobb1 says the ONS is on the 14th (tbachman, 17:08:09) * phrobb1 asks folks to register for the develoment summit at the end of the week of the ODL summit (tbachman, 17:08:34) * mohnish anumala (mohnish, 17:08:40) * Lithium updates (dfarrell07, 17:09:51) * zxiiro et al encurage everyone to test RC0 (dfarrell07, 17:10:44) * LuisGomez points out that testing takes time — just got RC0 (tbachman, 17:11:15) * colindixon says that for previous releases in between the RC offsets, builds were made so that projects could tell to see if their bugs had been fixed (tbachman, 17:11:50) * edwarnicke says that for Helium, we were building a daily RC release, which people could use to verify fixes (tbachman, 17:12:53) * gzhao says that in Helium, there was a daily helium build which triggered integration tests, but didn’t publish the results of the tests (tbachman, 17:13:18) * Youcef Laribi (Youcef, 17:13:33) * zxiiro says autorelease has two jobs: daily and release (tbachman, 17:13:40) * zxirro says the daily doesn’t create a staging repo (tbachman, 17:14:01) * LINK: https://jenkins.opendaylight.org/releng/view/autorelease/ Link to the autorelease jenkins page (tbachman, 17:14:37) * colindixon asks if there are any new blocking bugs to be addressed, or new items on the weather page (tbachman, 17:15:09) * LINK: https://wiki.opendaylight.org/view/Weather Current weather page for ODL Lithium (tbachman, 17:15:19) * LuisGomez asks when do we cut RC1? Answer - we will cut RC1 in one week and acknowledge we are a week behind in RC testing (phrobb1, 17:16:00) * LuisGomez asks if we should update the release plan to reflect the right dates (tbachman, 17:16:06) * colindixon says that probably makes sense (tbachman, 17:16:22) * colindixon (colindixon, 17:16:38) * gzhao says he’d like the TSC to schedule some time for the release plan review — notes that we have over 40 projects (tbachman, 17:17:46) * gzhao says that given that ONS is June 14-18, which is RC3 timeframe, it might be challenging to do the reviews and meet the 25th release (tbachman, 17:18:17) * ACTION: gzhao and phrobb1 to find suitable times for Lithium release reviews (tbachman, 17:18:30) * edwarnicke says he’d like to walk through the weather report (tbachman, 17:19:15) * edwarnicke says that an email was sent out on the pattern matching bug (tbachman, 17:20:10) * LINK: https://lists.opendaylight.org/pipermail/release/2015-June/002578.html email from rovarga_ on the patch (tbachman, 17:20:15) * edwarnicke says there are some items that they’re chasing on Neutron, which may be issues on the openstack side (tbachman, 17:20:35) * edwarnicke would like folks to have a look at the “to verify” blockers, to see if they’re truly resolved and can be removed from the weather page (tbachman, 17:21:05) * tykeal says that on Monday there was an issue with the host that ran the VM for our gerrit system. (tbachman, 17:21:21) * tykeal says they have a new VM in place, and are working to move the current gerrit system onto this VM (tbachman, 17:21:36) * it is recommended always have current handler filled for blocking bugs, so /me can chase current handler (gzhao, 17:21:45) * tykeal says that this morning the jenkins system could no longer talk to the API system. This has been fixed ,but the build queue is rather large (tbachman, 17:22:11) * tykeal is talking to rackspace to see if we can get the API limits increased (tbachman, 17:22:24) * colindixon asks if we’ve done any cursory examinations to see how many projects have merged their patches across to stable/lithium? (tbachman, 17:22:55) * colindixon asks if it makes sense to walk through to see if there are any obvious places that haven’t been fixed in stable/lithium before we merge the fix in yangtools to stable/lithium (tbachman, 17:24:12) * edwarnicke says that projects must have fixed in master in order to do their version bumps; these could be easily cherry-picked (tbachman, 17:24:51) * colindixon asks if we can run the CSIT tests to uncover any such bugs? (tbachman, 17:25:05) * ttkacik1 says we’d also have to run the autorelease tests (tbachman, 17:25:12) * ACTION: colindixon to follow-up offline to see if we can prevent breakage before the patch gets merged (tbachman, 17:26:03) * Integration and Test (tbachman, 17:26:39) * colindixon asks how many projects haven’t yet bumped (tbachman, 17:27:09) * ACTION: colindixon to bump and branch docs (zxiiro, 17:28:40) * Creation Review for NETCONF/MD-SAL Spinout Projects (tbachman, 17:28:59) * DIDM, Persistence, Reservation, SNMP4SDN, SNBI need to complete branching and version bump (gzhao, 17:29:09) * gzhao to follow up D4A for stable branch and version bump (gzhao, 17:30:05) * abhijitkumbhare will stand for me today, have Arno activities consuming my time. (ChrisPriceAB, 17:30:32) * Creation Review for Netconf (phrobb1, 17:31:11) * ttkacik1 says the reason for splitting out netconf/restconf is that they’re not core to the controller functionality (tbachman, 17:31:19) * LINK: https://wiki.opendaylight.org/view/Project_Proposals:Netconf he proposal (colindixon, 17:31:22) * LINK: https://lists.opendaylight.org/pipermail/project-proposals/2015-February/000253.html propsed on 2/17/2015 (colindixon, 17:31:43) * LINK: https://lists.opendaylight.org/pipermail/tsc/2015-May/003141.html a mail with links to lots of discussion here (colindixon, 17:32:21) * LuisGomez asks if this will be an offset 0 or 1 project (tbachman, 17:33:31) * ttkacik1 says they’re aiming for an offset 0 project (tbachman, 17:33:43) * colindixon says there are only two committers on the project, and are in the same time zone (tbachman, 17:34:28) * ttkacik1 says there will be a third committer as well, but they currenlty will be in the same time zones (tbachman, 17:35:01) * colindixon asks if they’re looking to be a core feature to the controller (tbachman, 17:35:55) * colindixon asks if they will be moving to mature with stable feautes, ttkacik1 says yes they aim to (colindixon, 17:36:02) * colindixon asks what the ramifications are of the spinout on downstream projects (tbachman, 17:36:41) * colindixon says this will change the group ID, and maybe the package names (tbachman, 17:37:09) * cdub points out that with the current committer list they will have difficulty to be mature if diversity is a requirement (colindixon, 17:38:50) * gzhao asks if we have the email for the committers? We only have the user IDs, which makes it hard to contact them (tbachman, 17:39:01) * ttkacik1 says they’ll provide the emails (tbachman, 17:39:09) * mohnish asks if the user would be able to issue netconf/restconf commands from the Karaf CLI (colindixon, 17:39:48) * ttkacik1 says that it’s not currently planned, but he’d be happy to help out and there is some code that would help (colindixon, 17:40:06) * rovarga_ says to ask during project release planning beryllium (colindixon, 17:40:23) * jmedved says that there are opportunities in beryllium for the community to provide patches and become committers (tbachman, 17:42:00) * VOTE: Voted on "Shall the TSC approve the Netconf project to the Incubation Lifecycle State?" Results are, +1: 9 (phrobb1, 17:44:12) * AGREED: the TSC approve the Netconf project to the Incubation Lifecycle State (tbachman, 17:44:52) * LINK: https://wiki.opendaylight.org/view/Project_Proposals:MD-SAL md-sal spinout project proposal (colindixon, 17:45:06) * LINK: https://lists.opendaylight.org/pipermail/project-proposals/2015-February/000268.html proposed on 2/19/2015 (colindixon, 17:45:29) * ttkacik1 says there are 4 implementations of the MD-SAL; the spinout is of the DOM APIs, and also the Java binding APIs and adapters, which can be put on top of any other MDSAL implementation (tbachman, 17:46:50) * abhijitkumbhare asks what is left in the "controller" project if MD-SAL is moved? (tbachman, 17:47:15) * colindixon says the config subsystem, the MD-SAL data implementation, clustering, and karaf; (tbachman, 17:47:36) * ttkacik1 also says apps on top of the MD-SAL: toaster, xsql, protocol frameworks, message bus (colindixon, 17:48:18) * abhijitkumbhare asks if the name should be mdsal-api, not mdsal (colindixon, 17:49:00) * abhijitkumbhare asks if most of the MD-SAL is still in the controller project (tbachman, 17:49:27) * ttkacik1 says it’s not just the API since it contains the SPIs, implementations of the MD-SAL binding impls, and a few things (colindixon, 17:49:31) * rovarga_ says it’s an implementation of the MD-SAL that’s left (tbachman, 17:49:47) * there are core pieces and SPIs that are reusable across multiple implementations, which is what they’re proposing be split out (tbachman, 17:50:43) * the general guidelines are to put things that would be needed for *all* mdsal implementations in the mdsal project and then leave the details of the current implementat(s) in controller (and yangtools) (colindixon, 17:52:54) * rovarga_ says that historically yangtools has taken on a lot of code that argualby should have been in the controller, this helps with some of that (colindixon, 17:54:21) * mohnish asks if these projects will interact with each other differently from other projects, e.g., other projects interact via YANG and the MD-SAL, but these will have to interact in lower-level OSGi ways (colindixon, 17:55:15) * LINK: what are the dependencies goign to be between mdsal, yangtools and controller after this? (colindixon, 17:58:08) * rovarga_ says mdsal will depend on yangtools, but not controller (colindixon, 17:58:21) * rovarga_ controller will depend on both yangtools and mdsal (colindixon, 17:58:35) * restconf/netconf will likely be dependent on all three others (yangtools, controller, mdsal) and aaa (colindixon, 17:59:19) * VOTE: Voted on "Shall the TSC approve the MD-SAL project to the incubation lifecycle state?" Results are, +1: 9 (phrobb1, 18:00:37) * AGREED: the MD-SAL project is approved to the incubation lifecycle state (phrobb1, 18:01:00) * cookies! (phrobb1, 18:01:20) Meeting ended at 18:01:26 UTC. Action items, by person ----------------------- * colindixon * colindixon to follow-up offline to see if we can prevent breakage before the patch gets merged * colindixon to bump and branch docs * gzhao * gzhao and phrobb1 to find suitable times for Lithium release reviews * phrobb1 * gzhao and phrobb1 to find suitable times for Lithium release reviews People present (lines said) --------------------------- * tbachman (122) * colindixon (54) * odl_meetbot (20) * phrobb1 (15) * cdub (12) * dfarrell07 (10) * edwarnicke (9) * tykeal (9) * odlcasey (6) * mohnish (6) * abhijitkumbhare (6) * gzhao (6) * ebrjohn (6) * dlenrow (3) * ChrisPriceAB (3) * Youcef (3) * zxiiro (3) * jmedved (3) * LuisGomez (2) * alagalah (2) * rovarga_ (1) * phrobb (0) Generated by `MeetBot`_ 0.1.4