#opnfv-release: OPNFV Release

Meeting summary

1. roll call (dmcbride, 16:01:44)
   1. David McBride (dmcbride, 16:01:51)
   2. Trevor Bramwell (bramwelt, 16:02:18)
   3. Maryam Tahhan (mtahhan_, 16:02:52)
   4. Justin (chigang, 16:03:24)
   5. Uli (uli-k, 16:03:39)
   6. Jack Morgan (IRC only - have a conflict) (jmorgan1, 16:04:57)
   7. Fatih Degirmenci (fdegir, 16:05:23)
   8. Gerald Kunzmann (GeraldK, 16:05:31)
   9. Frank Brockners (frankbrockners, 16:05:31)
   10. Tapio Tallgren (tallgren, 16:06:01)
   11. Mark Beierl (mbeierl, 16:06:06)
   12. Stuart Mackie (StuartMackie, 16:06:16)
   13. https://www.gotomeeting.com/join/775124285 (dmcbride, 16:06:23)
   14. Dave Neary (dneary, 16:06:59)
   15. Trevor Cooper (trevor_intel, 16:08:21)
   16. http://testresults.opnfv.org/test/swagger/spec.html#!/spec (jose_lausuch, 16:10:15)
   
   
2. Movie status (dmcbride, 16:10:53)
   1. jose_lausuch believes that link to swagger is working (dmcbride, 16:11:32)
   2. jose_lausuch provides credentials on IRC (dmcbride, 16:13:59)
   3. ACTION: jose_lausuch provide credentials for swagger to prakash via email (dmcbride, 16:14:29)
   
   
3. followup on MS3 - Installer integration with OpenStack (dmcbride, 16:17:36)
   1. rprakash (rprakash, 16:19:00)
   2. uli-k believes that using a common keystone API is necessary for scenario consolidation (dmcbride, 16:23:10)
   3. dneary concerned that using a common API will lead to using the oldest version, which is contrary to OPNFV goals (dmcbride, 16:27:18)
   4. sergmelikyan says: "we never know which software people running on our openstack and which API this software requires, we should not only consider our project or official openstack projects" (dmcbride, 16:29:51)
   5. jose_lausuch says: "functest tries to support v2 and v3" (dmcbride, 16:31:47)
   6. https://releases.openstack.org/teams/keystone.html (rprakash, 16:33:43)
   7. chigang: "I just have a suggestion that we can list the OpenStack configurations differences automatically." (dmcbride, 16:35:56)
   8. uli-k agrees with chigang (dmcbride, 16:36:13)
   9. trozet says: " it looks like in keystone, if users are assigned to default domain they use v2, other domains would use v3. I think for Apex our admin user is in default domain." (dmcbride, 16:37:20)
   10. https://gerrit.opnfv.org/gerrit/#/c/26769/1/functest/ci/config_functest.yaml (rprakash, 16:39:38)
   11. frankbrockners says: "trying to harmonize all the components for a release does *not* make sense, because it would be a race to the lowest common denominator and hence stop progress" (dmcbride, 16:43:23)
   12. http://docs.openstack.org/releasenotes/keystone/newton.html (bramwelt, 16:43:40)
   13. tallgren agrees with frankbrockners (dmcbride, 16:44:06)
   14. Greg_E_ says: "API compatibility is a difficult topic. API differences between installers will limit the compatibility of applications running on top. Just like Java, write once, test and debug every where. But installers are simply packaging commercial efforts and delivering them to the community, it is not possible to deviate in a major way. So we will have to live with a degree of uncertainty" (dmcbride, 16:45:13)
   15. we should support upgrade to minimum usable version of API supported by OpenStack version say if its Newton supports use 2.0 and move up o 2.1 or 3 as will be supported by Ocata (rprakash, 16:48:53)
   
   
4. Danube schedule (dmcbride, 16:51:32)
   1. MS5 moved to January 27 (dmcbride, 16:53:13)
   2. MS6 moved to February 17 (dmcbride, 16:53:35)
   3. fdegir suggests for future releases we have a map of projects to resources so that we can see which projects are impacted by resource disruptions (dmcbride, 16:55:28)
   4. fdegir and uli-k say that we should allocate critical processes to resources in a way that provides redundancy, so that we don't lose all capability during a resource disruption (dmcbride, 16:58:44)
   5. ACTION: fdegir propose how to improve lab redundancy and identify gaps and a plan to accomplish (dmcbride, 17:01:09)
   6. jmorgan1 expects to have all Intel resources back online by the end of the week (dmcbride, 17:02:11)

Action items

1. jose_lausuch provide credentials for swagger to prakash via email
2. fdegir propose how to improve lab redundancy and identify gaps and a plan to accomplish

Action items, by person

1. fdegir
   1. fdegir propose how to improve lab redundancy and identify gaps and a plan to accomplish
2. jose_lausuch
   1. jose_lausuch provide credentials for swagger to prakash via email

People present (lines said)

1. dmcbride (28)
2. uli-k (6)
3. jose_lausuch (6)
4. rprakash (5)
5. dneary (4)
6. frankbrockners (4)
7. chigang (4)
8. trozet (3)
9. tallgren (3)
10. Greg_E_ (3)
11. collabot (3)
12. fdegir (2)
13. bramwelt (2)
14. mtahhan_ (2)
15. trevor_intel (1)
16. GeraldK (1)
17. StuartMackie (1)
18. sergmelikyan (1)
19. mbeierl (1)
20. jmorgan1 (1)