================================
#opnfv-meeting: Infra WG Meeting
================================


Meeting started by fdegir at 16:02:53 UTC.  The full logs are available
at
http://ircbot.wl.linuxfoundation.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-12-18-16.02.log.html
.



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

* Joe Kidder  (joekidder, 16:04:15)
* Aric Gardner  (aricg, 16:04:16)
* David McBride  (dmcbride, 16:04:30)
* Fatih Degirmenci  (fdegir, 16:04:31)
* Tianwei Wu  (hw_wutianwei, 16:04:45)
* LINK: Agenda - https://wiki.opnfv.org/display/INF/Infra+Working+Group
  (jmorgan1, 16:04:56)
* David spoke with OpenStack Release project about topic - they use CI
  to judge if something needs to be release or not  (jmorgan1, 16:09:13)
* In order for basic promotion to work, we must ensure when we test
  scenarios, we only change the scenario  (fdegir, 16:10:54)
* Meaning that everything else should be frozen; test fw/cases, infra,
  etc  (fdegir, 16:11:10)
* Apart from this, we need a way to find out which scenario is impacted
  by certain change in order to run test that scenario  (fdegir,
  16:11:31)
* CI Evolution was proposed/approved long before XCI was even created
  (fdegir, 16:11:48)
* And due to us failing to make CI Evolution real, we started XCI to
  show that that's the way  (fdegir, 16:12:15)
* A basic schemet could be  (fdegir, 16:13:17)
* - patchset verification: healthcheck  (fdegir, 16:13:30)
* - post merge: smoke (?)  (fdegir, 16:13:41)
* - daily: functest + yardstick  (fdegir, 16:13:49)
* - weekly: performance/stress/etc.  (fdegir, 16:14:02)
* Each of these stages promoting scenarios to the next one or demoting
  (fdegir, 16:14:23)
* Test WG should come up with the scope for the test loops; what tests
  should be used where  (fdegir, 16:15:11)
* Promotion is not only for scenarios; test projects should also have
  promotion to enable certain test cases that are used for testing
  scenarios  (fdegir, 16:16:11)
* LINK: Pharos Spec etherpad -
  https://etherpad.opnfv.org/p/Pharos_Specification2.0  (jmorgan1,
  16:19:10)
* Compass: https://build.opnfv.org/ci/label/compass-baremetal/  (fdegir,
  16:23:37)
* Fuel: https://build.opnfv.org/ci/label/fuel-baremetal/  (fdegir,
  16:23:47)
* Joid: https://build.opnfv.org/ci/label/joid-baremetal/  (fdegir,
  16:23:56)
* Daisy: https://build.opnfv.org/ci/label/daisy-baremetal/  (fdegir,
  16:24:05)
* Apex: https://build.opnfv.org/ci/label/apex-baremetal-master/ and
  https://build.opnfv.org/ci/label/apex-baremetal-euphrates/  (fdegir,
  16:24:27)
* MCP/Fuel  (fdegir, 16:25:00)
* Armband: https://build.opnfv.org/ci/label/armband-baremetal/
  (bramwelt, 16:25:23)
* huawei-pod12 will connect jenkins this week  (hw_wutianwei, 16:26:42)
* each installer has two CI POD except Compass which has three and Fuel
  which has two POD per arch  (jmorgan1, 16:30:45)
* discussion on patch - https://gerrit.opnfv.org/gerrit/#/c/48755
  (jmorgan1, 16:31:54)
* who owns making sure a CI POD is listed in the test DB?  (jmorgan1,
  16:34:09)
* once a resource is approved as CI project, adding the permission to
  push results to test DB should be done by Test WG  (jmorgan1,
  16:35:54)
* ACTION: bramwelt will work on documenting the process for future
  releases  (jmorgan1, 16:36:47)
* INFRA-195 request for StorPerf POD - looking for baremetal POD
  (jmorgan1, 16:40:56)
* will look at this after the holidays to help StorPerf project find
  hardware resources  (jmorgan1, 16:42:00)
* LINK: https://gerrit.opnfv.org/gerrit/#/c/48413/  (bramwelt, 16:43:27)
* ACTION: bramwelt to work with LF Releng to resolve this discussion
  (jmorgan1, 16:46:29)
* bramwelt suggests use Jenkins as the default  (jmorgan1, 16:59:09)
* jmorgan1 thinks that if Jenkins is used then Jenkins needs to be
  better monitored for accuracy  (jmorgan1, 17:00:31)
* Reminder that we won't be meeting next two weeks and next meeting is
  January 9th  (jmorgan1, 17:02:03)
* Reminder that we won't be meeting next two weeks and next meeting is
  January 8th  (jmorgan1, 17:02:35)



Meeting ended at 17:03:26 UTC.



Action items, by person
-----------------------

* bramwelt
  * bramwelt will work on documenting the process for future releases
  * bramwelt to work with LF Releng to resolve this discussion



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

* fdegir (37)
* jmorgan1 (26)
* collabot (3)
* dmcbride (3)
* aricg (2)
* bramwelt (2)
* hw_wutianwei (2)
* joekidder (1)



Generated by `MeetBot`_ 0.1.4