15:59:32 <jmorgan1> #startmeeting Infra WG Weekly meeting
15:59:32 <collabot> Meeting started Wed Jan 18 15:59:32 2017 UTC.  The chair is jmorgan1. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:59:32 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:59:32 <collabot> The meeting name has been set to 'infra_wg_weekly_meeting'
15:59:37 <jmorgan1> #topic Rol Call
15:59:42 <jmorgan1> #info Jack Morgan
16:01:32 <uli-k> #info Uli
16:01:35 <jose_lausuch> #info Jose Lausuch
16:02:40 <thaj> #info thaj
16:02:46 <dfarrell07> is there a call-in number?
16:03:40 <dfarrell07> I'm seeing a strange GtM bug (2nd meeting now) - joining starts to work, then redirected to sales page.
16:03:42 <basic`> do i have the wrong link?
16:03:44 <jmorgan1> https://global.gotomeeting.com/join/819733085
16:03:54 <jmorgan1> https://wiki.opnfv.org/display/INF/Infra+Working+Group
16:03:57 <jmorgan1> details ^^
16:04:23 <dfarrell07> jmorgan1: thanks, was looking at https://wiki.opnfv.org/display/meetings/Infra+Working+Group+Meeting
16:04:54 <jmorgan1> dfarrell07: good to know, I'll those details there as well
16:04:58 <thaj> #info thaj
16:05:01 <jmorgan1> i'll add
16:07:08 <jmorgan1> #topic MS4 for Danube
16:09:44 <jmorgan1> #info Bryan points that projects should report out there status for MS4, which is a little different then installers
16:11:03 <bryan_att> #info Bryan Sullivan
16:12:02 * dfarrell07 never got access code 773-318-405 to work with +1 (224) 501-3312 FYI
16:12:42 <bryan_att> #info perhaps we should allow feature projects to report MS4 as "ready to start current release development", i.e. "the project has what it needs to get started". This may not be *all* that it needs, but is a sign that the project is not blocked from getting started in *some* sense, e.g. even just with Devstack.
16:14:50 <bryan_att> #info That way the installers can report when they have the deploy ready for testing, and a little pressure perhaps taken off (even though we need the installer integration earlier - that won't change) if they know that specific feature projects are not blocked by them.
16:15:33 <dfarrell07> jmorgan1: also the linked meeting ID is 773318405 but the text of the link is 819733085, so I guess maybe phone numbers are also from old meeting
16:15:36 <dfarrell07> np
16:15:51 <jmorgan1> dfarrell07: ok, i'll fix it later. sorry
16:16:24 <bryan_att> #info the goal should be that projects make progress on their own, using the minimum requirements needed to do that; an OPNFV deploy is not always (and maybe often not) the minimum requirement to make progress, and projects should not feel they have to wait unless they are truly blocked for some aspect.
16:31:05 <jmorgan1> https://jira.opnfv.org/issues/?filter=11156
16:36:48 <jmorgan1> #topic Infra JIRA tasks
16:36:59 <jmorgan1> #info went through open issues
16:38:24 <jmorgan1> #info Dynamic POD allocation needs a new owner
16:39:09 <jmorgan1> #info Jack mentions that Pharos should be able to take over Dynamic POD allocation
16:39:52 <jmorgan1> #info Scenario consolidation - Uli has updated his slides based on feedback he got
16:40:13 <jmorgan1> #info He continues to collect feedback from scenario owners
16:51:09 <jmorgan1> #info ChrisPriceAB asks about swagger API status, he is to sync up wth Jose on details and Prakesh to send a link
16:51:38 <jmorgan1> #info Bryan asks about a recommended BOM for hardware purchase in a Pharos lab
16:52:03 <jmorgan1> #info Jack to work on some details to add to the wiki and Bryan to look through the community lab wiki pages in the meantime
16:52:15 <jmorgan1> #endmeeting