#opendaylight-integration: integration

Meeting started by jamoluhrsen at 16:01:31 UTC (full logs).

Meeting summary

  1. packaging (jamoluhrsen, 16:04:56)
    1. packaging intern started now and going well. working on .deb packaging project (jamoluhrsen, 16:06:03)
    2. BeSR2 release artifacts to be complete this week. (jamoluhrsen, 16:06:44)
    3. good progress with different installers in OPNFV. up to now it's mostly only been APEX (jamoluhrsen, 16:07:03)
    4. ACTION: dfarrell07 to update int/pack's trello (dfarrell07, 16:08:03)
    5. cluster test and perf call still at 9am on Fridays. (jamoluhrsen, 16:09:09)
    6. ACTION: jamoluhrsen to setup a bluejeans meeting for 8:30am going forward starting in two weeks (jamoluhrsen, 16:09:26)

  2. distribution (jamoluhrsen, 16:10:12)
    1. karaf upgrade complete and we ended up with some broken distribution related jobs (jamoluhrsen, 16:10:36)
    2. one problem is that sshpass stopped working which affects bin/client (jamoluhrsen, 16:11:04)
    3. sshpass problem not happening in every environment, but does happen in releng (jamoluhrsen, 16:11:51)
    4. there are people working on this, and probably some workaround with some config or removal of a file (jamoluhrsen, 16:12:19)
    5. other issue was that after karaf upgrade, jetty started failing to start. iotdm needed to be removed from -all- features to fix this (jamoluhrsen, 16:13:29)
    6. autorelease was failing because sfc was still depending on ovsdb version of netvirt, so needed to move to netvirt features as ovsdb and netvirt split (jamoluhrsen, 16:15:37)
    7. autorelease currently failing because vxlan adapter issue. faas project. vratko sent email about this one. (jamoluhrsen, 16:16:25)
    8. autorelease didm project still not part of autorelease after being removed several weeks ago. (jamoluhrsen, 16:17:06)
    9. autorelease successful build for all projects is part of M4 requirement, but ideally projects should try to always be there and building successfully. (jamoluhrsen, 16:17:59)

  3. builder (jamoluhrsen, 16:19:36)
    1. private cloud is under test, and going well. (jamoluhrsen, 16:20:01)
    2. private cloud sandbox will be migrated to soon (maybe this weekend) (jamoluhrsen, 16:20:20)
    3. everyone using sandbox will need to pull in some patches in order to use new sandbox (jamoluhrsen, 16:20:42)
    4. https://git.opendaylight.org/gerrit/#/q/status:open+topic:rpc-migration rpc-migration patches (zxiiro, 16:20:51)
    5. we need to reduce the resources each VM uses in the jobs we are using. zxiiro plans to investigate this. (jamoluhrsen, 16:23:22)
    6. biggest impact is if we can reduce system requirements on builder vms, mininet, etc. (jamoluhrsen, 16:24:06)
    7. we could reduce mininet vms right now, but we'll still need larger mininet systems for things like scale tests (jamoluhrsen, 16:24:59)
    8. do *NOT* abort jobs more than once. just click the little red x one time. more than once will leave VMs hung and wasting resources. (jamoluhrsen, 16:26:59)
    9. tykeal thinks the sandbox migration could start happening friday night (5/20) (jamoluhrsen, 16:27:40)
    10. if anyone notices anything in new sandbox that is not the same as old sandbox, make it known. (jamoluhrsen, 16:29:00)
    11. releng private cloud will migrate a few weeks after sandbox migration assuming all is well in new sandbox (jamoluhrsen, 16:29:36)
    12. new private cloud will not let us view robot logs in browser remotely. we have to save the logs locally and open locally. (jamoluhrsen, 16:31:16)
    13. might have workaround for viewing logs, or they might get posted to nexus eventually. (jamoluhrsen, 16:31:35)

  4. release (jamoluhrsen, 16:31:52)
    1. M3 offset 2 coming up. seems like the toughest milestone. maybe we can do a TWS working group to answer questions (jamoluhrsen, 16:33:09)

  5. misc (jamoluhrsen, 16:33:49)
    1. what do we want to do with the old Integration repo? (jamoluhrsen, 16:34:16)
    2. archived projects have locked repos, meaning read-only. we can unlock to do one off changes. we can move it, but non-trivial to do. (jamoluhrsen, 16:35:14)
    3. the problem is that people can clone and use this old archived repo, and can cause confusion, especially to new people. (jamoluhrsen, 16:35:50)
    4. LuisGomez likes idea to remove all repo files and add one readme that points users to the new repos. (jamoluhrsen, 16:36:19)
    5. tykeal asks that a committer do this. (jamoluhrsen, 16:36:54)
    6. anipbu agrees with this idea, but we should do this with all archived projects. (jamoluhrsen, 16:37:39)
    7. Integration is a special case, because the project is archived but there is still the same work ongoing in a new repo (jamoluhrsen, 16:38:34)
    8. vratko points out that we need to do this to all branches. (jamoluhrsen, 16:39:48)
    9. ACTION: jamoluhrsen to double check with TSC that this is ok. (jamoluhrsen, 16:40:00)
    10. https://wiki.opendaylight.org/view/Archive_Proposals/Integration#Archive_Location (anipbu, 16:42:12)
    11. https://wiki.opendaylight.org/view/Archive_Proposals/Integration#Archive_Location needs to be updated if we do this repo cleaning (jamoluhrsen, 16:42:58)
    12. jamoluhrsen asks how can we start getting our wiki pages indexed so they can be publically searched. (jamoluhrsen, 16:44:58)
    13. zxiiro notes that phrobb had a good reason to not have this. (jamoluhrsen, 16:45:11)
    14. ACTION: jamoluhrsen to email phrobb and CaseyODL to get this enabled if possible (jamoluhrsen, 16:45:29)
    15. ACTION: anipbu to survey all projects to see if they want to be indexed and present that info to LF folks (jamoluhrsen, 16:46:48)

  6. system test waivers (jamoluhrsen, 16:47:57)
    1. DLUX has the basics of what they need to do system tests. jamoluhrsen recommends we do not give a waiver (jamoluhrsen, 16:49:31)
    2. ODLPARENT granted system test waiver (jamoluhrsen, 16:52:44)
    3. MDSAL granted system test waiver (jamoluhrsen, 16:53:34)
    4. https://lists.opendaylight.org/pipermail/integration-dev/2016-May/006768.html reasons why we may want to rethink what is valid for system tests. maybe something yang could be. (jamoluhrsen, 16:54:37)
    5. YANG granted system test waiver (jamoluhrsen, 16:54:46)
    6. OPENFLOWJAVA granted system test waiver (jamoluhrsen, 16:55:14)
    7. https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Waiver/System_Test <--- List of current system test waivers (anipbu, 16:55:56)
    8. YANGIDE granted system waiver because there is no infra to run their system tests (jamoluhrsen, 16:56:18)
    9. anipbu would like a way that projects report external system test results. (jamoluhrsen, 16:58:15)
    10. https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template (anipbu, 16:58:26)
    11. Be projects still not requesting waiver, but maybe wont need one (OpFlex, SNMP4SDN, TTP, TCPMD5) (jamoluhrsen, 17:00:25)


Meeting ended at 17:00:46 UTC (full logs).

Action items

  1. dfarrell07 to update int/pack's trello
  2. jamoluhrsen to setup a bluejeans meeting for 8:30am going forward starting in two weeks
  3. jamoluhrsen to double check with TSC that this is ok.
  4. jamoluhrsen to email phrobb and CaseyODL to get this enabled if possible
  5. anipbu to survey all projects to see if they want to be indexed and present that info to LF folks


Action items, by person

  1. anipbu
    1. anipbu to survey all projects to see if they want to be indexed and present that info to LF folks
  2. CaseyODL
    1. jamoluhrsen to email phrobb and CaseyODL to get this enabled if possible
  3. dfarrell07
    1. dfarrell07 to update int/pack's trello
  4. jamoluhrsen
    1. jamoluhrsen to setup a bluejeans meeting for 8:30am going forward starting in two weeks
    2. jamoluhrsen to double check with TSC that this is ok.
    3. jamoluhrsen to email phrobb and CaseyODL to get this enabled if possible


People present (lines said)

  1. jamoluhrsen (61)
  2. CaseyODL (5)
  3. anipbu (4)
  4. zxiiro (3)
  5. odl_meetbot (3)
  6. dfarrell07 (2)


Generated by MeetBot 0.1.4.