=============================
#opnfv-release: OPNFV Release
=============================


Meeting started by dmcbride at 16:02:53 UTC.  The full logs are
available at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-01-17-16.02.log.html
.



Meeting summary
---------------

* roll call  (dmcbride, 16:03:08)
  * David McBride  (dmcbride, 16:03:12)
  * Jose Lausuch  (jose_lausuch, 16:03:18)
  * Sofia Wallin  (sofiawallin, 16:03:25)
  * Jack Morgan  (jmorgan1, 16:03:51)
  * Trevor Cooper  (trevor_intel, 16:04:19)
  * Uli  (uli-k, 16:04:25)
  * Tapio Tallgren  (tallgren, 16:04:38)
  * Bryan Sullivan  (bryan_att, 16:08:28)

* Daisy integration with functest  (dmcbride, 16:08:49)
  * jose_lausuch continues to provide information to the Daisy team
    (dmcbride, 16:09:08)
  * progress is unclear  (dmcbride, 16:09:15)

* Danube schedule  (dmcbride, 16:09:51)

* Movie status  (dmcbride, 16:12:01)
  * Prakash reports that Movie team is making progress in adding test
    cases to the TC database  (dmcbride, 16:15:17)
  * Prakash says that there are no longer any access issues  (dmcbride,
    16:15:36)

* Danube schedule  (dmcbride, 16:16:03)
  * Intel labs still needing to be brought online are kvm4nfv, ovsnfv,
    vsperf, Barometer  (jmorgan1, 16:17:59)
  * Intel lab will be back online by Wednesday this week  (jmorgan1,
    16:18:28)
  * bryan_att reports that the Barometer project has been delayed due to
    resource unavailability  (dmcbride, 16:20:13)
  * bryan_att also notes that the unavailability of scenarios for Danube
    has also been a problem  (dmcbride, 16:21:30)
  * - to clarify there are several underlying delay issues beyond the
    lab infra issues we experienced this time. I don't want to conflate
    these, but they are: (1) the timeline in which current upstream code
    is integrated in installers; (2) the complexity and resource
    requirements of OPNFV deploys  (bryan_att, 16:26:02)
  * trevor_intel also reports being delayed due to resource migration
    (dmcbride, 16:26:36)
  * as a result this year I am shifting toward more independence from
    OPNFV scenarios as a basis for test/dev, with functest integration
    at the right time (when installers are ready) and using OPNFV CI/CD
    infra for all that testing, rather than my dev lab resources
    (bryan_att, 16:28:38)
  * trevor_intel asks about documentation requirements  (dmcbride,
    16:28:44)
  * sofiawallin reports that documentation setup will be similar to
    prior releases, even though we are switching to read-the-docs
    (dmcbride, 16:29:40)
  * doc WG continues to define requirements  (dmcbride, 16:29:55)
  * this approach should enable more early/continual progress on current
    upstream release support and features - in essence this is like
    OPNFV on Devstack, and no/few tests will be OPNFV-specific (all will
    run on upstream dev environments alone)  (bryan_att, 16:31:07)
  * sofiawallin reports that the doc WG is having an additional meeting
    on Weds (tomorrow)  (dmcbride, 16:32:50)

* AoB  (dmcbride, 16:33:03)
  * jose_lausuch expresses concern about status of Joid  (dmcbride,
    16:33:27)
  * narinder reports that Joid has been impacted by the Intel lab
    migration  (dmcbride, 16:33:53)
  * Intel POD5 Node5 needs to be reset due to IMPI being stuck
    (jmorgan1, 16:34:50)
  * ACTION: narinder to update team on status of Joid at the next
    release meeting (Jan 24)  (dmcbride, 16:37:34)



Meeting ended at 16:37:45 UTC.



People present (lines said)
---------------------------

* dmcbride (23)
* fdegir (11)
* bryan_att (8)
* jmorgan1 (4)
* collabot (3)
* jose_lausuch (3)
* trozet (2)
* trevor_intel (1)
* tallgren (1)
* sofiawallin (1)
* uli-k (1)



Generated by `MeetBot`_ 0.1.4